On Fri, Jun 26, 2020 at 12:38:40PM -0400, Ben Rosser wrote: > On Fri, Jun 26, 2020 at 12:32 PM Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > > > On Thu, Jun 25, 2020 at 01:18:59PM -0400, Ben Cotton wrote: > > > == Scope == > > > * Proposal owners: > > > ** Modify comps to include nano Fedora wide. > > > ** Create a new subpackage of <code>nano</code>, called > > > <code>nano-editor</code>. > > > ** <code>nano-editor</code> to include > > > <code>/usr/lib/environment.d/10-nano.conf</code>, which sets > > > <code>$EDITOR</code> to <code>nano</code>. > > > > There's one nitpick with using nano in 'git commit' and similar: it'll > > ask about the name to save as: > > ^X > > Save modified buffer? Y > > File Name to Write: /home/zbyszek/src/systemd/.git/worktrees/systemd-work/COMMIT_EDITMSG > > > > Would it be possible to skip this last question in those scenarios? > > It the answer is "no", that's OK, but if it would be easy, it'd make > > usage a bit nicer. 'vi' and 'emacs -nw' don't ask. > > The -t/--tempfile switch for nano (and pico) does exactly this: > https://linux.die.net/man/1/nano > Does that imply then, if we were to switch the default EDITOR variable to nano, we would have to set it as: EDITOR=nano -t or some such? That solves the problem for git, but may introduce other problems for users, either by wanting to be promted when its opened from other cli tools, or in the alternative, if we just set EDITOR=nano, are we going to encounter questions when people change the save path and wonder why their commits fail? Neil > Ben Rosser > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
