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: Mon, 14 Feb 2022 22:19:05 +0200 [thread overview]
Message-ID: <831r05p5fq.fsf@gnu.org> (raw)
In-Reply-To: <86wnhxdxmp.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de)
> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>,
> Phillip Lord <phillip.lord@russet.org.uk>
> Date: Mon, 14 Feb 2022 21:03:10 +0100
>
> 1. Gnu Nano
> 2. Vim (the ubiquitous text editor) [default]
>
> it seems the above are included in Git for Windows, for the following
> there are links provided (supposedly when they are not found)
>
> 3. Notepad++
> 4. Visual Studio Code
> 5. Visual Studio Code Insiders
> 6. Sublime Text
> 7. Atom
> 8. VSCodium
>
> And the final two programs are provided by the OS
>
> 9. Notepad (New)
> 10. Wordpad (New)
>
> 11. Select other editor as Git's editor
>
> I find this quite astonishing that there is no mention of Emacs, all the
> more because Linus is supposed to use µemacs a variant of it! It seems
> that the maintainers don't consider Emacs a "text editor"?
They should have emacsclient, not Emacs. (When I install Git, I
choose 11 and point Git to emacsclient.exe.)
next prev parent reply other threads:[~2022-02-14 20:19 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 [this message]
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
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=831r05p5fq.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).