From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 38718@debbugs.gnu.org, dgbulk@gmail.com
Subject: bug#38718: Emacs `compile' command does not handle remote (over TRAMP) file name correctly
Date: Mon, 23 Dec 2019 15:58:27 +0200 [thread overview]
Message-ID: <83a77jxhx8.fsf@gnu.org> (raw)
In-Reply-To: <875zi7l8fq.fsf@gmx.de> (message from Michael Albinus on Mon, 23 Dec 2019 10:04:09 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 23 Dec 2019 10:04:09 +0100
> Cc: 38718@debbugs.gnu.org
>
> > Might the fix in 27.1 referenced in report #38648 need to be
> > back-ported to 26.x?
>
> There are no plans for an Emacs 26.4. Emacs 27 will start its pretest
> soon, and I don't know whether this problem will trigger a hotfix release.
>
> What we could do is to publish the patch of bug#38648 on top of Emacs
> 26.3. Since we haven't done such an announcement yet, I don't know where
> to do it.
>
> I believe there are other fixes in Emacs 27 for macOS Catalina, which
> are not included in Emacs 26.3. Maybe a special cumulative patch of
> Emacs 26.3, good for macOS Catalina, could be done?
>
> Eli? John?
I don't want to lose time by having another Emacs 26.x release. I
think even Emacs 26.3 was a mistake.
If these issues cause sever problems on Catalina, we could suggest
people to apply a few patches to their own builds, and hope that
binary distributions pick up those patches.
next prev parent reply other threads:[~2019-12-23 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 5:05 bug#38718: Emacs `compile' command does not handle remote (over TRAMP) file name correctly Duncan Greatwood
2019-12-23 9:04 ` Michael Albinus
2019-12-23 13:58 ` Eli Zaretskii [this message]
2019-12-23 14:14 ` Michael Albinus
2019-12-23 14:34 ` Eli Zaretskii
2019-12-23 15:39 ` Dmitry Gutov
2019-12-23 16:08 ` Eli Zaretskii
2019-12-23 15:47 ` Michael Albinus
2019-12-23 17:34 ` Duncan Greatwood
2019-12-23 20:20 ` Michael Albinus
2020-01-02 4:03 ` Duncan Greatwood
2020-01-02 10:54 ` Michael Albinus
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=83a77jxhx8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38718@debbugs.gnu.org \
--cc=dgbulk@gmail.com \
--cc=michael.albinus@gmx.de \
/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).