Jindrich Novy wrote:
I did two patches to fix it so that you can decide which one is better
commit candidate.
Patch1:
Allows an user to type leading spaces on the command prompt, but when
enter is pressed, it tests whether the user typed at least something
except spaces. In case it finds only
Jindrich Novy wrote:
IMHO, patch1 is better way. Else end user can decide the space key is
not working ...
Yes, the spacebar won't be working for leading spaces. However, typing
the leading spaces in the command prompt IMHO doesn't make too much
sense to me so maybe after patch2 is applied
Patch2:
Doesn't let the user to type leading spaces if he didn't write a non-
space letter already.
Not a good idea, since I think if you prepend a space to any command, the
command is not saved in bash history - a feature.
Sometimes it may be thus desirable to be able to type leading space
Hello Martin,
On Mon, 2005-03-21 at 17:42 +0100, [EMAIL PROTECTED] wrote:
Patch2:
Doesn't let the user to type leading spaces if he didn't write a non-
space letter already.
Not a good idea, since I think if you prepend a space to any command, the
command is not saved in bash history -
Hi Jindrich,
On Mon, 2005-03-21 at 18:25, Jindrich Novy wrote:
On Mon, 2005-03-21 at 17:42 +0100, [EMAIL PROTECTED] wrote:
Not a good idea, since I think if you prepend a space to any command, the
command is not saved in bash history - a feature.
Sometimes it may be thus desirable to be
Hello buc,
Monday, March 21, 2005, 7:44:46 PM, you wrote:
b Intuitively, the MC can be perceived as a screen extension to shell
b (which became possible due to ncurses/slang lib and Ctr/Fn/Alt/Meta
b keyboard features). Therefore, MC`s cmdline should be closer to a shell
b command line, rather
