From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
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 16:47:14 +0100 [thread overview]
Message-ID: <87o8vzjb7h.fsf@gmx.de> (raw)
In-Reply-To: <831rsvxg94.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Dec 2019 16:34:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I suggest to have the patches posted in the relevant bug reports, and
> have the problem description in etc/PROBLEMS which mentions the bug
> numbers and the availability of patches for Emacs versions before 27.
This would be etc/PROBLEMS of Emacs 27.0.50. Why shall it describe not
solved in Emacs 26.3, but solved in Emacs 27.0.50?
One idea I have is to provide a patch-26 package via GNU ELPA. But this
has disadvantages: It could patch only Lisp code. And it must be
guaranteed NOT to run for Emacs 27.
> Thanks.
Best regards, Michael.
next prev parent reply other threads:[~2019-12-23 15:47 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
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 [this message]
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=87o8vzjb7h.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=38718@debbugs.gnu.org \
--cc=dgbulk@gmail.com \
--cc=eliz@gnu.org \
/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).