all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org, benno@bmevers.de
Subject: Re: [PATCH] edit: Friendlier error message.
Date: Wed, 11 Nov 2015 23:01:30 +0100	[thread overview]
Message-ID: <87si4c8abp.fsf@gnu.org> (raw)
In-Reply-To: <87io5e9ev0.fsf@gnu.org> (Mathieu Lirzin's message of "Sat, 07 Nov 2015 13:24:35 +0100")

Mathieu Lirzin <mthl@gnu.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andreas Enge <andreas@enge.fr> skribis:
>>
>>> On Thu, Nov 05, 2015 at 12:08:35PM +0100, Ludovic Courtès wrote:
>>>> > +    (unless (search-path (parse-path (getenv "PATH")) (%editor))
>>>> > +      (leave (_ "Couldn't find editor '~a'. Please check $EDITOR and $PATH.")
>>>> > +             (%editor)))
>>>
>>> An additional, heterodox suggestion: Maybe also test for $VISUAL.
>>
>> AIUI, $VISUAL is for visualizing files, not for editing, no?
>
> I can't remember where I have read this, but I think this 2 variables
> exist to distinguish between line editing à la Ed, and visual editing
> à la VI.

SUS mentions ‘VISUAL’ but without saying what it’s for:

  http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08

But
<http://unix.stackexchange.com/questions/4859/visual-vs-editor-whats-the-difference>
says something that seems to make sense, like what you wrote.

I’ve committed a change that honors $VISUAL first, $EDITOR second.

Thanks,
Ludo’.

  reply	other threads:[~2015-11-11 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 22:42 [PATCH] edit: Friendlier error message benno
2015-11-05 11:08 ` Ludovic Courtès
2015-11-07  3:25   ` Andreas Enge
2015-11-07 11:06     ` Ludovic Courtès
2015-11-07 12:24       ` Mathieu Lirzin
2015-11-11 22:01         ` Ludovic Courtès [this message]
2015-11-15  4:26           ` Andreas Enge

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=87si4c8abp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=benno@bmevers.de \
    --cc=guix-devel@gnu.org \
    --cc=mthl@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.