public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] nano: Update to 5.9
Date: Mon, 11 Oct 2021 14:05:21 +0100	[thread overview]
Message-ID: <C654E5A0-1AFD-4A02-9367-074D0B33FAF5@ipfire.org> (raw)
In-Reply-To: <A9CB1A2A-EB62-4DAA-97F7-5F044EF9AD2B@rymes.net>

[-- Attachment #1: Type: text/plain, Size: 2946 bytes --]

Hello,

> On 10 Oct 2021, at 16:15, Tom Rymes <tom(a)rymes.net> wrote:
> 
> I much prefer nano, as it’s intuitive, so I don’t have to think to use it. If I forget what a command is, it’s at the bottom of the screen. With vim, I have the remember “wait, how do I get into editing mode? And if I want to save a file, how do I do that again? Crap. Better Google a tutorial.”

Funny. I feel like that about nano. Impossible to use because it has loads of weird keyboard shortcuts.

I use VIM without thinking about it :)

> Sure, if I used it more, it would become second nature, but I don’t, so as more of an admin (and less of a developer) that doesn’t spend lots of time in console editors, nano is nice.
> 
> Having said that, I don’t see the need to include it. Whenever I install a new system, I run a pakfire command to install nano, ncftp, telnet (for administering old Cisco IP phones), wlanap, and I forget what else. No big whoop, and how often does one install a new system?

Ncftp? Is FTP still alive anywhere?

-Michael

> Tom
> 
>> On Oct 10, 2021, at 8:55 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hello,
>> 
>> We have (or had) a couple of editors and I am quite against shipping them all.
>> 
>> Everyone has their favourites, and there will always be another one.
>> 
>> What is wrong with vim?
>> 
>> -Michael
>> 
>>> On 9 Oct 2021, at 22:07, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>> 
>>> All,
>>> 
>>> Is it possible to move `nano` from addon to core?  It is SOOOOO much easier to use than vim.
>>> 
>>> I understand it is an easy installed addon but it seems like it really belongs in "core".
>>> 
>>> Jon
>>> 
>>>>> On Oct 9, 2021, at 5:56 AM, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>> 
>>>> Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
>>>> 
>>>> On 08/10/2021 19:22, Matthias Fischer wrote:
>>>>> For details see:
>>>>> https://www.nano-editor.org/news.php
>>>>> 
>>>>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>>>>> ---
>>>>> lfs/nano | 6 +++---
>>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>> 
>>>>> diff --git a/lfs/nano b/lfs/nano
>>>>> index 3bb7806aa..237dfab20 100644
>>>>> --- a/lfs/nano
>>>>> +++ b/lfs/nano
>>>>> @@ -24,7 +24,7 @@
>>>>> include Config
>>>>> -VER        = 5.8
>>>>> +VER        = 5.9
>>>>> THISAPP    = nano-$(VER)
>>>>> DL_FILE    = $(THISAPP).tar.xz
>>>>> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
>>>>> DIR_APP    = $(DIR_SRC)/$(THISAPP)
>>>>> TARGET     = $(DIR_INFO)/$(THISAPP)
>>>>> PROG       = nano
>>>>> -PAK_VER    = 38
>>>>> +PAK_VER    = 39
>>>>> DEPS       = ""
>>>>> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>>> -$(DL_FILE)_MD5 = d2249e3dd108c830df00efd7c1b79d86
>>>>> +$(DL_FILE)_MD5 = 24b67a7a2e731d3a5ec6d154b4521d08
>>>>> install : $(TARGET)
>>>>> 
>>> 
>> 


  reply	other threads:[~2021-10-11 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 17:22 Matthias Fischer
2021-10-09 10:56 ` Adolf Belka
2021-10-09 21:07   ` Jon Murphy
2021-10-10 12:55     ` Michael Tremer
2021-10-10 15:15       ` Tom Rymes
2021-10-11 13:05         ` Michael Tremer [this message]
     [not found] <668607DA-B692-46E1-A6CE-6027D21A30FB@gmail.com>
2021-10-11 13:07 ` Michael Tremer
     [not found] <11C8156B-0713-41A0-B3F8-74927F47D03A@gmail.com>
2021-10-11 20:57 ` Adolf Belka
2021-10-12  9:40   ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C654E5A0-1AFD-4A02-9367-074D0B33FAF5@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox