From Fedora Project Wiki
m
m
Line 81: Line 81:
  
 
* Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.)
 
* Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.)
 
 
* Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking.
 
* Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking.
 
* Blocks product? Potentially all.
 
* Blocks product? Potentially all.

Revision as of 22:46, 12 June 2020

Make nano the default editor

Summary

vim is powerful. nano is simple. Let's use nano as the default editor across all of Fedora.

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-06-12
  • 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

nano is already installed across most Fedora Editions and Spins. This proposal will make it the default editor, while continuing to install vim-minimal.

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.

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

Lorem ipsum dolor sit amet ...

User Experience

Lorem ipsum dolor sit amet ...

Dependencies

Lorem ipsum dolor sit amet ...

Contingency Plan

  • Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.)
  • Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking.
  • Blocks product? Potentially all.

Documentation

Lorem ipsum dolor sit amet ...

Release Notes