Sujet : Re: Running an editor from ANSI C
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.lang.cDate : 09. Jun 2024, 08:24:14
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v43lau$39uge$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : Pan/0.158 (Avdiivka; )
On Sat, 8 Jun 2024 22:13:49 +0300, Michael S wrote:
On Fri, 7 Jun 2024 23:57:58 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Fri, 7 Jun 2024 14:24:29 +0300, Michael S wrote:
On Fri, 7 Jun 2024 10:47:57 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Fri, 07 Jun 2024 02:37:42 -0700, Keith Thompson wrote:
As for portability, I'm not aware of the $EDITOR convention being
used on non-POSIX systems.
Can non-POSIX systems offer anything better? Any worthwhile
alternative?
No.
Yes. The one below is better.
ShellExecute(NULL, "edit", filename, NULL, NULL, SW_NORMAL);
On Windows, that combines the command-line arguments into a single
string. Which then has to be teased apart by the receiving program.
Assuming the two ends can agree on consistent rules for doing so.
You asked for something that is better *for user* than $EDITOR.
The one above is very clearly better for user than $EDITOR.
Neglecting the various potential pitfalls in how the invocation works,
fine.
It is smarter - different editors are selected for different file types.
And it achieves that with zero effort on part of app developer.
If that’s what you want, then we have xdg-open for that
<
https://askubuntu.com/questions/1279623/what-is-xdg-open>.
VISUAL and EDITOR are about editing text files, that’s all.
Running an editor from ANSI C
Re: Running an editor from ANSI C