mirror of
git://git.code.sf.net/p/cdesktopenv/code
synced 2025-03-09 15:50:02 +00:00
Default to emacs upon invoking interactive shell
If the VISUAL or EDITOR environment variable is not set to a value matching *[Vv][Ii]* or *macs* at initialisation time, then ksh does not turn on any line editor. This is user-hostile. New users on Unix-like systems typically have a simple editor like nano preconfigured as their default, or may not have the VISUAL or EDITOR variable set at all. So if they try ksh, they find themselves without basic functionality such as arrow keys and probably go straight back to bash. The emacs line editor is by far the most widely used, especially among new users, so ksh should default to that. Most other shells already do this. src/cmd/ksh93/sh/main.c: sh_main(): - On an interactive shell, if on editor was turned on based on $VISUAL or $EDITOR, turn on emacs before reading input.
This commit is contained in:
parent
d650c73e55
commit
1375cda934
5 changed files with 62 additions and 34 deletions
6
NEWS
6
NEWS
|
@ -3,6 +3,12 @@ For full details, see the git log at: https://github.com/ksh93/ksh/tree/1.0
|
|||
|
||||
Any uppercase BUG_* names are modernish shell bug IDs.
|
||||
|
||||
2022-02-01:
|
||||
|
||||
- Upon invocation, the interactive shell no longer leaves the user without
|
||||
a line editor if the VISUAL or EDITOR variable does not indicate emacs,
|
||||
gmacs or vi; instead, it now turns on the emacs option by default.
|
||||
|
||||
2022-01-31:
|
||||
|
||||
- Improved keyboard support for the vi and emacs built-in line editors:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue