From Fedora Project Wiki
m
(work up the proposal a bit)
Line 4: Line 4:
 
== Summary ==
 
== Summary ==
  
vim is powerful. nano is simple. Let's use nano as the default editor across all of Fedora.
+
Let's make Fedora more approachable, by having a default editor that doesn't require specialist knowledge to use.
  
 
== Owner ==
 
== Owner ==
Line 33: Line 33:
 
== Detailed Description ==
 
== Detailed Description ==
  
nano is already installed across most Fedora Editions and Spins. This proposal will make it the default editor, while continuing to install vim-minimal.
+
Users are exposed to the default editor when they use commands that call it. The main example here is something like <code>git commit</code>.
  
vim requires esoteric knowledge, or Googling, for common editing tasks: entering edit mode, saving, quitting. Let's leave such power in the hands of experts.
+
Vim is the current default. 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 Vim. It also makes things hard for those who don't particularly want to learn how to use Vim.
 +
 
 +
Nano is similar to the graphical text editing that people are used to, and therefore doesn't require specialist knowledge to use it. It is already installed across most Fedora Editions and Spins.
 +
 
 +
This proposal will make Nano the default editor, while continuing to install vim-minimal. People will still be able to call <code>vi</code> if they want to edit a file.
  
 
== Feedback ==
 
== Feedback ==
Line 44: Line 48:
  
 
* Makes the default editor across all of Fedora more approachable.  
 
* Makes the default editor across all of Fedora more approachable.  
* Nano is also mostly self-documenting, by displaying common keyboard shortcuts on-screen).
+
* Nano is also mostly self-documenting, by displaying common keyboard shortcuts on-screen.
 
* More in line with the default editor of other distributions.
 
* More in line with the default editor of other distributions.
 
  
 
== Scope ==
 
== Scope ==
Line 68: Line 71:
 
== How To Test ==
 
== How To Test ==
  
Lorem ipsum dolor sit amet ...
+
Run <code>export EDITOR="/usr/bin/nano"</code>.
  
 
== User Experience ==
 
== User Experience ==
  
Lorem ipsum dolor sit amet ...
+
Users running <code>git commit</code> 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.
  
 
== Dependencies ==
 
== Dependencies ==
Line 80: Line 83:
 
== Contingency Plan ==
 
== Contingency Plan ==
  
* Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.)
+
The contingency plan is to revert to vi if there are significant issues with the change.
* Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking.
+
 
 +
* Contingency deadline: this is a simple change, so a deadline isn't necessary.
 +
* Blocks release? if the change breaks the redirection to an editor, it should block the release. However, this is unlikely.
 
* Blocks product? Potentially all.
 
* Blocks product? Potentially all.
  
 
== Documentation ==
 
== Documentation ==
  
Lorem ipsum dolor sit amet ...
+
As part of this change, it would be good to add instructions for changing the default editor to the [https://docs.fedoraproject.org/en-US/quick-docs/ quick docs].
  
 
== Release Notes ==
 
== Release Notes ==

Revision as of 11:36, 24 June 2020

Make nano the default editor

Summary

Let's make Fedora more approachable, by having a default editor that doesn't require specialist knowledge to use.

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-06-24
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Users are exposed to the default editor when they use commands that call it. The main example here is something like git commit.

Vim is the current default. 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 Vim. It also makes things hard for those who don't particularly want to learn how to use Vim.

Nano is similar to the graphical text editing that people are used to, and therefore doesn't require specialist knowledge to use it. It is already installed across most Fedora Editions and Spins.

This proposal will make Nano the default editor, while continuing to install vim-minimal. People will still be able to call vi if they want to edit a file.

Feedback

Pending ...

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.

Scope

  • Proposal owners:
    • Modify comps to include nano Fedora wide
    • Create a package that provides /usr/bin/editor ... sprinkle on some magic and voila. Also include this package in comps.

INFO: Eighth_Doctor | I think this is the thing that actually manages /usr/bin/editor on debian: https://salsa.debian.org/debian/sensible-utils

  • Other developers: N/A
  • Release engineering: #9522
  • Policies and guidelines: N/A
  • Trademark approval: N/A

Upgrade/compatibility impact

Will not apply to upgrades.

How To Test

Run export EDITOR="/usr/bin/nano".

User Experience

Users running 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.

Dependencies

Lorem ipsum dolor sit amet ...

Contingency Plan

The contingency plan is to revert to vi if there are significant issues with the change.

  • Contingency deadline: this is a simple change, so a deadline isn't necessary.
  • Blocks release? if the change breaks the redirection to an editor, it should block the release. However, this is unlikely.
  • Blocks product? Potentially all.

Documentation

As part of this change, it would be good to add instructions for changing the default editor to the quick docs.

Release Notes