Hot answers tagged user-interface
Ultimately, it was an arbitrary choice made by the creators of Unix over four decades ago now. They could have chosen to make things case-insensitive like the creators of MS-DOS did a decade later, but that has its disadvantages, too. It's too deeply embedded in *ix culture to change now. The case sensitive filesystem issue brought up by eppesuig is only ...
A normal, "modeless" editor is like Notepad on Windows: there is only one mode, where you input text. Vi, and it's successor Vim, are modal: there are two primary modes1, insert mode where you type text into the editor and it is committed to the document, and normal mode where you enter arguments via the keyboard that perform a variety of functions, ...
Ubuntu is a standard suggestion for beginners in Linux. As far as memory is concerned, go with a lighter version of Ubuntu.
This is entirely up to you but most programs do someting like this program --help Usage: program [<options>][<arguments> ...] Options: --help show this message, then exit --something after some spaces for alignment, an explenation follows. You should check out getopt which most programs (this is also available in programming ...
getopt vs getopts seems to be a religious issue. As for the arguments against getopt in the Bash FAQ: "getopt cannot handle empty arguments strings" seems to refer to a known issue with optional arguments, which it looks like getopts doesn't support at all (at least from reading help getopts for Bash 4.2.24). From man getopt: getopt(3) can parse long ...
How about :e .? This opens the current directory in Vim, i.e. it opens the file explorer. Because I have autochdir setting set, this shows the directory that the currently edited file is in.
I'm not sure but I think that you want the :rew command
Linux Mint is, for me, the most user-friendly Linux Distribution, the UI is almost the same as Windows, on the contrary of Ubuntu's Unity. Plus, for me, it's much more stable and "better", in my opinion than Ubuntu. You may also want to take a look at Mageia, a fork of Mandriva, the old Mandrake Linux.
This is not a "terminal" problem, it is a file system feature. How should the shell look for your commands on the (always case sensitive) file system?
From my experience of looking at new, untaught users: their main problems are with understanding and having a grasp on what is what on the now common Windows/KDE/Xfce/IceWM-like desktop -- they get confused by the elements of the DE and afraid. After thinking this over, I arrived at the conclusion that a Nextstep/WindowMaker/(perhaps Gnome 3)-like desktop ...
Use ^O to fallback previous opened file, which is your dir tree in this case.
Case sensitive is part of the POSIX way of handling command and argument it has nothing to do with the meaning. It's a very good thing that Status and status are not the same because the file system which kind of a base in the system is case sensitive (because of POSIX rules). It's usually a good pratice to keep the same behavior in your whole system. ...
is there any reason to be case-sensitive? It leaves a much bigger namespace available. For example, a later version of git could implement uppercase variations on command names, or allow the user to define macros/aliases, as with the shell, where you can define your own MV, CP, etc. without having to redefine mv, cp, etc.
The “kill” meaning of Ctrl+C is very old, I think even older than Unix. Wikipedia traces it back to TOPS-10, which would date it from the late 1960s. The article explains why Ctrl+C was a reasonable choice: in ASCII, which was published in 1963, the corresponding character is ETX, end-of-text. Lacking a character meaning “stop”¹, a character meaning “this ...
Press o to change the options. In the very first preference “User mode”, select “Advanced” (“Novice” has the huge help, “Intermediate” has a one-line help, and “Advanced” shows the selected URL in the modeline). Check the “Save options to disk” box then follow the “Accept” link at the top. The corresponding setting in ~/.lynxrc is user_mode=ADVANCED ...
Openbox and Window Maker are great suggestions. You may also have luck with related projects and derivatives; I had a good experience with Fluxbox on Crunchbang (Ubuntu-based). Lubuntu, with the LXDE desktop environment is very lightweight while providing a bit more out-of-the-box infrastructure than going without any desktop environment. Though, I've ...
http://www.gnome.org/getting-gnome/ Fedora Just install or try it live to use GNOME 3. openSUSE GNOME 3.2 is the default desktop environment of openSUSE 12.1. Mageia GNOME 3 will be part of Mageia 2. Install ‘task-gnome’ after installing Mageia. Arch Linux Arch Linux has GNOME 3 in the extra repository. Ubuntu ...
I am not a fan of overriding built-in commands, but in my .bashrc (part of Tilde, my "dot files") I explicitly do this: alias rm='rm -i'; This makes rm ask for permission before deleting. It has saved me a few times. You can always override with rm -f.
The technical systems that I use and respect are almost exclusively case-sensitive: be it OS or programming language or anything else. The exceptions I could think of right now is the HTML tags and some implementations of SQL, and the Ada programming language. Even in those cases, I think there are strong tendencies to actually write HTML tags in ...
There's this getopts_long written as a POSIX shell function that you may embed inside your script. Note that the Linux getopt (from util-linux) works correctly when not in traditional mode and supports long options, but is probably not an option for you if you need to be portable to other Unices. Recent versions of ksh93 (getopts) and zsh (zparseopts) ...
If it has to be portable to a range of Unices, you'd have to stick to POSIX sh. And AFAIU there you just have no choice but rolling argument handling by hand.
To disable the login manager permanently on Ubuntu you can do the following: sudo sh -c "echo 'manual' > /etc/init/lightdm.override" To start the login manager manually when needed you would do: sudo service lightdm start To stop it manually: sudo service lightdm stop
Look at it from another perspective. The computer has no knowledge of language or letters, what it sees are numbers that are then mapped to characters. While I (the letter I) and | (the pipe) may look very similar to you, they are completely different to the computer. To illustrate, have a look at the table below. You will see that there is no ...
Your primary concern will be finding a distro which runs happily in 256Mb - its not a lot of memory these days. IMHO (and personally I prefer KDE) for non-techies, I'd favour a Gnome 3 based desktop (although an icewm/xfce will fit better into the available memory). I'd also suggest having a look at the distros targeting netbooks - the program selection is ...
You can change the default font and font size under Preferences -> Interface -> Output. Check the "Font override" checkbox and then set your font and size in the bar to the right. You can change it to whatever you want: and make it as big as you want:
It's called "Visual Bell" - see this question for how to fix it in bash. set bell-style none
In ls and du, the --help output is plain and simple hardcoded into the program. In scripting languages such as Python there may be an option parsing library that does it automatically for you. As for standards, the only thing I could find was this: http://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html#g_t_002d_002dhelp or more specific to ls, ...
You will have to build X on your own. Begin by reading this X.Org wiki entry. This guide is for developers who wish to build the X Window System from source. If your area of interest is limited to a single package, like a driver or an application, check with your O/S first for development facilities. As for a package manager, you will need to choose ...
$ (read -p "Foo the bar? [y/N] " ans ; [ "$ans" = Y -o "$ans" = y ]) ; echo $? Foo the bar? [y/N] Y 0
Only top voted, non community-wiki answers of a minimum length are eligible