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: Sun, 10 Oct 2021 13:55:39 +0100	[thread overview]
Message-ID: <0E4C0FE5-E555-4B43-926D-2E1820B5C5D7@ipfire.org> (raw)
In-Reply-To: <F57769B6-EAD8-46E7-B0EF-BCCF57CE58E2@gmail.com>

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

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-10 12:55 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 [this message]
2021-10-10 15:15       ` Tom Rymes
2021-10-11 13:05         ` Michael Tremer
     [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=0E4C0FE5-E555-4B43-926D-2E1820B5C5D7@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