From: pauline-galea@gmx.com
To: monnier@iro.umontreal.ca
Cc: help-gnu-emacs@gnu.org
Subject: Getting Emacs (was: No such file or directory, popup)
Date: Tue, 25 May 2021 20:08:53 +0200 [thread overview]
Message-ID: <trinity-ccc9f9c4-d3f8-4b8b-abd5-1323f718a31b-1621966133804@3c-app-mailcom-bs01> (raw)
In-Reply-To: <jwvzgwisprw.fsf-monnier+emacs@gnu.org>
> Sent: Wednesday, May 26, 2021 at 5:12 AM
> From: "Stefan Monnier via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Getting Emacs (was: No such file or directory, popup)
>
> > Emacs 25 was installed from my package manager (synaptic). Installed Emacs
> > 27.1 using "sudo add-apt-repository". Emacs 28 from source.
>
> Hmm... so based on this progression, I'd guess that for Emacs-29, you'll
> hacking into Emacs maintainers's machines to get the code before it hits
> the Git repository, and for Emacs-30 you'll be listening to their brain
> waves to get the code before they type it into their computers?
>
> Stefan
>
Be very afraid ! :)
next prev parent reply other threads:[~2021-05-25 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 12:27 No such file or directory, popup pauline-galea
2021-05-25 12:33 ` Jean Louis
2021-05-25 13:08 ` pauline-galea
2021-05-25 14:45 ` Philip Kaludercic
2021-05-25 14:54 ` pauline-galea
2021-05-25 15:10 ` Philip Kaludercic
2021-05-25 15:50 ` pauline-galea
2021-05-25 16:13 ` Philip Kaludercic
2021-05-25 16:17 ` pauline-galea
2021-05-25 17:05 ` Philip Kaludercic
2021-05-25 17:12 ` Getting Emacs (was: No such file or directory, popup) Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-25 18:08 ` pauline-galea [this message]
2021-05-25 16:03 ` No such file or directory, popup pauline-galea
2021-05-25 16:15 ` Philip Kaludercic
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=trinity-ccc9f9c4-d3f8-4b8b-abd5-1323f718a31b-1621966133804@3c-app-mailcom-bs01 \
--to=pauline-galea@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).