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: Tue, 12 Oct 2021 10:40:10 +0100	[thread overview]
Message-ID: <26E16FA2-AA87-45AA-8B7F-66C6293CC971@ipfire.org> (raw)
In-Reply-To: <ee9a840f-c75d-20bc-f029-499b176c7383@ipfire.org>

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

Hello,

visudo launching nano would really surprise me :)

-Michael

> On 11 Oct 2021, at 21:57, Adolf Belka <adolf.belka(a)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(a)ipfire.org> wrote:
>>> 
>>> Hello,
>>> 
>>>> On 10 Oct 2021, at 20:42, Jon Murphy <jcmurphy26(a)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(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-12  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11C8156B-0713-41A0-B3F8-74927F47D03A@gmail.com>
2021-10-11 20:57 ` Adolf Belka
2021-10-12  9:40   ` Michael Tremer [this message]
     [not found] <668607DA-B692-46E1-A6CE-6027D21A30FB@gmail.com>
2021-10-11 13:07 ` Michael Tremer
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

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=26E16FA2-AA87-45AA-8B7F-66C6293CC971@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