Daaaa! meant kwrite lol
Also I think either joe or nano is default simple command line editors also there is midnight commander but you need to install that. Then there is always vi if you are daring.
-Gerry Makaro
Fraser-Bell Info Tech
Solving Tech Mysteries since the Olden Days!
~~
If I helped you, consider clicking the Star at the bottom left of my post.
Hi,
I always use the builtin command for that kind of stuff.
That code will make sure it finds screenfetch if it is in your PATH and it will run the executable screenfetch within your PATH.Code:if command -v screenfetch >/dev/null; then command screenfetch; fi
Second the builtin command is POSIX according to this site
Code:http://pubs.opengroup.org/onlinepubs/007904975/utilities/command.html
"Unfortunately time is always against us" -- [Morpheus]
.:https://github.com/Jetchisel:.
On 2014-12-08 06:06, Fraser Bell wrote:
> Only difference in path are uppercase F and lowercase f, results are
> different.
My guess is that Mr Rethil amd Mr verthrix changed the name,
intentionally or accidentally. The search is working correctly, it is
case sensitive.
> Who to notify for consolidation? Or, are there differences (I think
> not), and then which is the better choice?
Those two users, my guess.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-12-12 23:46, gogalthorp wrote:
>
> Daaaa! meant kwrite lol
>
> Also I think either joe or nano is default simple command line editors
> also there is midnight commander but you need to install that. Then
> there is always vi if you are daring.
joe should be available in all installs, even on the rescue modes of the
installation dvd. We asked for that years ago, as "vi" was difficult for
us msdos/windows émigrés. ;-)
joe is peculiar in that it can be called in several guises: joe, jstar,
jmacs, jpico... so that it behaves differently on each, similar to those
editors.
There appears not to be a jvi, though :-p
mcedit is the editor of midnight commander, and it is very simple to
use, with evident help keys and menus. Midnight commander (mc) can be a
very useful tool to have when forced to work in text mode for rescue
ops, so it is something I always add at the first chance, during install.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
Hi,
Looked at this thread again after a few weeks of holiday lunacy, and I'm still a bit confused. I may need a step-by-step walkthrough to fix this problem, because I know openSUSE less than any other distro I use, and I'm very new to Linux in general. The bottom line seems to be that while I can locate the .bashrc file in other distros, I'm having trouble figuring out how to do so in this one. Not sure why, and it's probably just due to confusion.
Are there some instructions I could use for the KDE edition that would tell me how to edit the proper file to put the Screenfetch line in so it'd automatically run upon opening a terminal? Am I better off installing a different text editor to do this with?
Sorry if I'm not entirely clear right now. I'm a bit out of it, but I don't quite get what my best option would be between all the suggestions. My attempts at locating that file for purposes of editing it are fruitless for some reason.
Hi,
the .bashrc file is in your home directory and it starts with a dot which by default is not shown by any GUI file manager.
andCode:echo ~/.bashrc
Should show you the absolute path where that file is. There should be an option for file managers to show files that starts with a dot aka "dot-files".Code:echo "$HOME/.bashrc"
orCode:kwrite ~/.bashrc
should work for KDE since kwrite is installed by default. You should be able to edit and save that file.Code:kwrite "$HOME/.bashrc"
"Unfortunately time is always against us" -- [Morpheus]
.:https://github.com/Jetchisel:.
On 2015-01-01 08:06, Hunson wrote:
>
> Hi,
>
> Looked at this thread again after a few weeks of holiday lunacy, and I'm
> still a bit confused. I may need a step-by-step walkthrough to fix this
> problem, because I know openSUSE less than any other distro I use, and
> I'm very new to Linux in general. The bottom line seems to be that while
> I can locate the .bashrc file in other distros, I'm having trouble
> figuring out how to do so in this one. Not sure why, and it's probably
> just due to confusion.
It is a hidden file.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-Gerry Makaro
Fraser-Bell Info Tech
Solving Tech Mysteries since the Olden Days!
~~
If I helped you, consider clicking the Star at the bottom left of my post.
Bookmarks