From Fedora Project Wiki
(initial writeup)
 
m
Line 60: Line 60:
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
* Release engineering: [https://pagure.io/releng/issues ]
+
* Release engineering: [https://pagure.io/releng/issues/9522 #9522]
  
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 19:26, 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

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.
  • Other developers: N/A
  • Release engineering: #9522
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes