Hide Forgot
A number of new Linux users I know find Pico to be the easiest command-line editor to learn. This is particularly the case for first year students who have access to a terminal for introductory operating system or programming subjects. Many such users are unfamiliar with (and do not wish to spend the time to learn) Vim or Emacs, and can not use a GUI text editor. With Pine and Pico slated for future removal, it will be somewhat disappointing to lose it. I am hopeful you will consider supplying the GNU Nano editor, a free clone of UW Pico in its place. Indeed, it provides some enhanced functionality such as search and replace, multiple buffers, and syntax highlighting, so you might even consider including regardless of the status of Pine. As you would expect of GNU software, it is licensed under the GNU GPL. Its home page is <http://www.nano-editor.org>.
As I commented on the mailing list, there have already been requests submitted in bugzilla to add nano, and we will consider that request from various people once pine does get officially removed from the distribution. There is no chance nano will be added while pine is still present. I am closing this bug WONTFIX for now because there is no need to track this in bugzilla as it is already present in bugzilla, and I'm 200% sure that when pine does actually get removed, there will be 10000 new RFE submissions at that juncture.
Mike Thanks for your response on the list. I only filed this bug after searching Bugzilla for any open bugs against Red Hat Linux with "nano" in the summary, and the search resulted in zero results. If you are attempting to avoid duplicates and extra work, perhaps it would be easiest to leave an RFE open so that a bug search finds it.
No. The bug status reflects the bug status. People should search for both open and closed bugs if they want to really find things. Ignoring the purpose of the bug status field and leaving a thousand bugs open because people can't properly use bugzilla doesn't let bugzilla serve it's purpose properly.
*** This bug has been marked as a duplicate of 55253 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.