From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: $EDITOR and “guix edit”
Date: Thu, 16 Nov 2023 16:25:38 +0100 [thread overview]
Message-ID: <87r0kpu3d9.fsf@gnu.org> (raw)
In-Reply-To: <416a6472edf6d2123c47ea5b555bedd005f6ac6f.camel@gmail.com> (Liliana Marie Prikler's message of "Thu, 02 Nov 2023 11:24:56 +0100")
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> Am Donnerstag, dem 02.11.2023 um 10:43 +0100 schrieb Simon Tournier:
>> Hi,
>>
>> The command “guix edit” returns “+N path/to/file” that is then passed
>> to $EDITOR. Therefore $EDITOR needs the command line:
>>
>> $ $EDITOR +N /path/to/file
>>
>> Well, that is accepted by many $EDITOR, to my knowledge. At least,
>> Emacs, Vi or less are fine with it.
> This appears to be a somewhat archaic convention.
“Archaic” is one way to describe it; I’d have said “standard”. :-)
(Implemented by Vi(m), Emacs, Nano, less, more, etc.)
>> However, some other $EDITOR does not. I have in mind “kate” or
>> “VSCode“,
>>
>> $ kate -l N path/to/file
>> $ code --goto path/to/file:N
It’d be nice to support these as well. However, how do we know we’re
dealing with kate or VSCode? By checking the basename of $EDITOR?
Kinda ugly and brittle, but probably better than nothing.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-11-16 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:43 $EDITOR and “guix edit” Simon Tournier
2023-11-02 10:24 ` Liliana Marie Prikler
2023-11-16 15:25 ` Ludovic Courtès [this message]
2023-11-16 16:04 ` Liliana Marie Prikler
2023-11-20 9:40 ` Simon Tournier
2023-11-20 19:33 ` Liliana Marie Prikler
2024-01-12 9:35 ` Simon Tournier
2024-01-12 17:39 ` Liliana Marie Prikler
2024-01-12 18:49 ` Simon Tournier
2024-01-12 19:46 ` Liliana Marie Prikler
2024-01-12 21:27 ` Simon Tournier
2023-11-22 18:21 ` Ludovic Courtès
2023-11-22 19:24 ` Liliana Marie Prikler
2023-12-09 9:24 ` Ludovic Courtès
2023-12-09 9:55 ` Liliana Marie Prikler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0kpu3d9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).