Make nano the default editor
Let's make Fedora more approachable, by having a default editor that doesn't require specialist knowledge to use.
- Name: Chris Murphy
- Email: firstname.lastname@example.org
- Targeted release: Fedora 33
- Last updated: 2020-12-04
- FESCo issue: #2426
- Tracker bug: #1854444
- Release notes tracker: #522
Users are exposed to the default editor when they use commands that call it. The main example here is something like
Fedora does not currently have a default terminal text editor, because the $EDITOR environment variable is unset by default. But a common scenario where users wind up in a terminal text editor is when using 'git commit'. By default, git picks vi. You need to spend time learning how to use it, for even basic editing tasks. This increases the barrier to entry for those who are switching to Fedora and don't know how to use vi. It also makes things hard for those who don't particularly want to learn how to use vi. (These arguments would apply just as well if git picked Vim. vi is like hard mode for Vim, with fewer features, missing syntax highlighting, and no indication of what mode you are in. Even Vim users may feel lost and bewildered when using vi.)
In contrast, Nano offers the kind of graphical text editing experience that people are used to, and therefore doesn't require specialist knowledge to use. It is already installed across most Fedora Editions and Spins. This proposal will make Nano the default editor, while continuing to install
vim-minimal (which provides vi, but not Vim). People will still be able to call
vi if they want to edit a file. It will also obviously be possible to change the default editor to vi or Vim, for those who want it.
Why make Nano default and vi optional, rather than the other way round? Because Nano is the option that everyone can use.
- I think this is a great idea - and I already set my EDITOR to vim. Having to explain how to set EDITOR in .bashrc before even starting the basics of terminal lore with a newbie is an unnecessary barrier. @sdgathman (will have to see an example of properly signing feedback)
- I like the idea, but ... this is a change in behavior for users who do a clean install in order to "upgrade" the OS. I'd expect at least a handful of bugzilla requests to be opened against this change demanding a different default or to revert and let the app pick its own default. Emacs users are a very vocal bunch for example. Personally, I don't mind; changing the default $EDITOR is not that hard, but it's a point of contention for some, and I feel it's fair to raise that for awareness now rather than wait. Also, what about the default $PAGER for man - it's currently null or /usr/bin/less right? /usr/bin/less uses similar commands to vi and this will bring about an inconsistency in the terminal that I'd like to see addressed before this is released. Speeddymon (talk) 18:25, 25 June 2020 (UTC)
Benefit to Fedora
- Makes the default editor across all of Fedora more approachable.
- Nano is also mostly self-documenting, by displaying common keyboard shortcuts on-screen.
- More in line with the default editor of other distributions.
- Proposal owners:
- Create a new subpackage of
/etc/profile.d/nano.(sh|csh), which sets
nano-default-editorwill be added to both @standard and @workstation-product in comps, so it gets installed by default everywhere.
- Create a new subpackage of
With this approach, if
nano is uninstalled, the configuration will be removed with it. At the same time, installing nano on its own won't install the conf.
- Other developers: N/A
- Release engineering: #9522
- Policies and guidelines: N/A
- Trademark approval: N/A
Users upgrading from Fedora 31/32 to Fedora 33+ who have not explicitly set their editor default will have their default editor changed to nano as well.
How To Test
git commit will be able to just type their commit message, rather than having to learn about insert mode, and they'll be able to cut and paste without having to learn special shortcuts.
No additional dependencies are required.
The contingency plan is to revert the change by removing the
- Contingency deadline: probably the beta? It's an easy change to revert.
- Blocks release? If the change breaks the redirection to an editor, it should block the release. However, this is unlikely.
- Blocks product? Potentially all.
As part of this change, it would be good to add instructions for changing the default editor to the quick docs.