| Message ID | 20211008172224.2405-1-matthias.fischer@ipfire.org |
|---|---|
| State | Accepted |
| Commit | 81acbae3f14da9cb2faa69559488ab1435925df1 |
| Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4HQw495G54z3xCR for <patchwork@web04.haj.ipfire.org>; Fri, 8 Oct 2021 17:22:33 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4HQw482m91z1qH; Fri, 8 Oct 2021 17:22:32 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4HQw481tgSz2yTr; Fri, 8 Oct 2021 17:22:32 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4HQw464HgWz2yS8 for <development@lists.ipfire.org>; Fri, 8 Oct 2021 17:22:30 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4HQw4572Wxz17r for <development@lists.ipfire.org>; Fri, 8 Oct 2021 17:22:29 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1633713750; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=ubsa7YqpTPa5BWX+T8Jc4o+jDe3WnsiWafUL8q+OiGI=; b=49luudzQjDb8lMP5sCZ29xsvNzumaiF6DLZDWhv8fCdwazQZnm91M8OpOSpE9bw/UDnc0+ s8D3ooktMR9wjzCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1633713750; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=ubsa7YqpTPa5BWX+T8Jc4o+jDe3WnsiWafUL8q+OiGI=; b=HMDYR7qU93C1wi781bbkcULGvMuHXRYj7j+67Bm8xi5fw6nzXZBUYwWvNsI6PbMvoddrm6 JYmeKC5nspjPLnyawUJuityqNUrdTvxY42T57GcS8QqB3FmVzj2R+ROWYOTEo/L0qHbH8r aQ1BSeBzN61pseZy/47QH36zBj98/E3ozI+qNz1c8yXHZNEWnoJfje/ll1PLYZ7LfUC9+M D9KkJ/V147ap1mqwScj6V6WoB7xsntEf2kTeJrh3bOBW1weXA3ERDjaAwdhsubM0ALfUXk xCjj4aTL4tXGSuJQAl5gwkcAvckPnhqoYdjWOEotbeSTzUli7Qcp7ckTgw5Czg== From: Matthias Fischer <matthias.fischer@ipfire.org> To: development@lists.ipfire.org Subject: [PATCH] nano: Update to 5.9 Date: Fri, 8 Oct 2021 19:22:24 +0200 Message-Id: <20211008172224.2405-1-matthias.fischer@ipfire.org> X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <https://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <https://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
| Series |
nano: Update to 5.9
|
|
Commit Message
Matthias Fischer
Oct. 8, 2021, 5:22 p.m. UTC
For details see:
https://www.nano-editor.org/news.php
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
---
lfs/nano | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Comments
Reviewed-by: Adolf Belka <adolf.belka@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@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) >
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@ipfire.org> wrote: > > Reviewed-by: Adolf Belka <adolf.belka@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@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) >>
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@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@ipfire.org> wrote: >> >> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>> >
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.” 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? Tom > On Oct 10, 2021, at 8:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>> >>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>> >> >
I’m not sure nano is "the" answer though I do like it. Just anything besides vim. Vim is fine for developers. It is the non-developers that struggle. This article explains it pretty well and it includes my struggles to exit! https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/ <https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/> Q: How do you generate a random string? A: Put a user in front of vi, and tell them to exit > On Oct 10, 2021, at 7:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>> >>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>> >> >
Hello, > On 10 Oct 2021, at 16:15, Tom Rymes <tom@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@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@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@ipfire.org> wrote: >>>> >>>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>>> >>> >>
Hello, > On 10 Oct 2021, at 20:42, Jon Murphy <jcmurphy26@gmail.com> wrote: > > I’m not sure nano is "the" answer though I do like it. Just anything besides vim. > > Vim is fine for developers. It is the non-developers that struggle. This article explains it pretty well and it includes my struggles to exit! > > https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/ > > Q: How do you generate a random string? > A: Put a user in front of vi, and tell them to exit LOL. Good one. I wouldn’t be against adding nano to the core distribution, although I would draw the line there and say that Joe is then out :) However, I wouldn’t want to make it the default editor if that is okay. -Michael > > >> On Oct 10, 2021, at 7:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>>> >>>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>>> >>> >> >
Vim as default is fine! The only default editor setting I know of is in fcron. # Location of the default editor for "fcrontab -e" #editor = /usr/bin/vi editor = /usr/bin/nano Is there another? > On Oct 11, 2021, at 8:07 AM, Michael Tremer <michael.tremer@ipfire.org> wrote: > > Hello, > >> On 10 Oct 2021, at 20:42, Jon Murphy <jcmurphy26@gmail.com> wrote: >> >> I’m not sure nano is "the" answer though I do like it. Just anything besides vim. >> >> Vim is fine for developers. It is the non-developers that struggle. This article explains it pretty well and it includes my struggles to exit! >> >> https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/ >> >> Q: How do you generate a random string? >> A: Put a user in front of vi, and tell them to exit > > LOL. Good one. > > I wouldn’t be against adding nano to the core distribution, although I would draw the line there and say that Joe is then out :) > > However, I wouldn’t want to make it the default editor if that is okay. > > -Michael > >> >> >>> On Oct 10, 2021, at 7:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>>>> >>>>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>>>> >>>> >>> >> >
Hi Jon, On 11/10/2021 18:14, Jon Murphy wrote: > Vim as default is fine! > > The only default editor setting I know of is in fcron. > > # Location of the default editor for "fcrontab -e" > #editor = /usr/bin/vi > editor = /usr/bin/nano > Is there another? > If you want to edit the sudoers file you have to use the visudo command which by default uses vi. You can use nano with visudo by running # EDITOR=nano visudo and to change the editor permanently add the following into the sudoers file. # Reset environment by default Defaults env_reset # Set default EDITOR to nano, and do not allow visudo to use EDITOR/VISUAL. Defaults editor=/usr/bin/nano, !env_editor Regards, Adolf. > > >> On Oct 11, 2021, at 8:07 AM, Michael Tremer <michael.tremer@ipfire.org> wrote: >> >> Hello, >> >>> On 10 Oct 2021, at 20:42, Jon Murphy <jcmurphy26@gmail.com> wrote: >>> >>> I’m not sure nano is "the" answer though I do like it. Just anything besides vim. >>> >>> Vim is fine for developers. It is the non-developers that struggle. This article explains it pretty well and it includes my struggles to exit! >>> >>> https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/ >>> >>> Q: How do you generate a random string? >>> A: Put a user in front of vi, and tell them to exit >> >> LOL. Good one. >> >> I wouldn’t be against adding nano to the core distribution, although I would draw the line there and say that Joe is then out :) >> >> However, I wouldn’t want to make it the default editor if that is okay. >> >> -Michael >> >>> >>> >>>> On Oct 10, 2021, at 7:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>>>>> >>>>>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>>>>> >>>>> >>>> >>> >> >
Hello, visudo launching nano would really surprise me :) -Michael > On 11 Oct 2021, at 21:57, Adolf Belka <adolf.belka@ipfire.org> wrote: > > Hi Jon, > > On 11/10/2021 18:14, Jon Murphy wrote: >> Vim as default is fine! >> >> The only default editor setting I know of is in fcron. >> >> # Location of the default editor for "fcrontab -e" >> #editor = /usr/bin/vi >> editor = /usr/bin/nano >> Is there another? >> > If you want to edit the sudoers file you have to use the visudo command which by default uses vi. > > You can use nano with visudo by running > > # EDITOR=nano visudo > > and to change the editor permanently add the following into the sudoers file. > > # Reset environment by default > Defaults env_reset > # Set default EDITOR to nano, and do not allow visudo to use EDITOR/VISUAL. > Defaults editor=/usr/bin/nano, !env_editor > > Regards, > > Adolf. > >> >> >>> On Oct 11, 2021, at 8:07 AM, Michael Tremer <michael.tremer@ipfire.org> wrote: >>> >>> Hello, >>> >>>> On 10 Oct 2021, at 20:42, Jon Murphy <jcmurphy26@gmail.com> wrote: >>>> >>>> I’m not sure nano is "the" answer though I do like it. Just anything besides vim. >>>> >>>> Vim is fine for developers. It is the non-developers that struggle. This article explains it pretty well and it includes my struggles to exit! >>>> >>>> https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/ >>>> >>>> Q: How do you generate a random string? >>>> A: Put a user in front of vi, and tell them to exit >>> >>> LOL. Good one. >>> >>> I wouldn’t be against adding nano to the core distribution, although I would draw the line there and say that Joe is then out :) >>> >>> However, I wouldn’t want to make it the default editor if that is okay. >>> >>> -Michael >>> >>>> >>>> >>>>> On Oct 10, 2021, at 7:55 AM, Michael Tremer <michael.tremer@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@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@ipfire.org> wrote: >>>>>>> >>>>>>> Reviewed-by: Adolf Belka <adolf.belka@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@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) >>>>>>>> >>>>>> >>>>> >>>> >>> >>
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)