From: Eli Zaretskii <eliz@gnu.org>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: corwin@bru.st, phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: Windows binaries for emacs-28 status and TODOs
Date: Wed, 16 Feb 2022 15:32:33 +0200 [thread overview]
Message-ID: <838rub2az2.fsf@gnu.org> (raw)
In-Reply-To: <86mtirt1lj.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de)
> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
> Cc: corwin@bru.st, emacs-devel@gnu.org, phillip.lord@russet.org.uk
> Date: Wed, 16 Feb 2022 13:52:56 +0100
>
> >> I believe it should also work for emacs.exe (which it is) and
> >> runemacs.exe (which is not working, please see the attached image).
> >
> > Why is that a good idea?
>
> To be prepared for all eventualities when a user might overwrite a
> suggestion of emacsclient? It took many years of Emacs usage before I
> understood what emacsclient is.
Ther option could say "emacs", but configure Git to use emacsclient
instead.
> And there's also GitGui to consider, which is not a console program
> (regarding the choice of emacsclient and emacsclientw)..
That one should use emacsclientw.
next prev parent reply other threads:[~2022-02-16 13:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 10:54 Windows binaries for emacs-28 status and TODOs Corwin Brust
2022-01-23 11:18 ` Eli Zaretskii
2022-01-23 12:00 ` Corwin Brust
2022-02-14 20:03 ` H. Dieter Wilhelm
2022-02-14 20:19 ` Eli Zaretskii
2022-02-16 9:50 ` H. Dieter Wilhelm
2022-02-16 12:30 ` Eli Zaretskii
2022-02-16 12:52 ` H. Dieter Wilhelm
2022-02-16 13:32 ` Eli Zaretskii [this message]
2022-02-16 13:40 ` Corwin Brust
2022-02-16 13:59 ` Eli Zaretskii
2022-02-16 14:43 ` H. Dieter Wilhelm
2022-02-16 16:52 ` H. Dieter Wilhelm
2022-02-16 16:37 ` H. Dieter Wilhelm
2022-01-26 19:37 ` H. Dieter Wilhelm
2022-02-06 10:40 ` H. Dieter Wilhelm
2022-02-06 18:35 ` Corwin Brust
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rub2az2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=corwin@bru.st \
--cc=dieter@duenenhof-wilhelm.de \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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/emacs.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).