From: Michael Albinus <michael.albinus@gmx.de>
To: Duncan Greatwood <dgbulk@gmail.com>
Cc: 38718@debbugs.gnu.org
Subject: bug#38718: Emacs `compile' command does not handle remote (over TRAMP) file name correctly
Date: Mon, 23 Dec 2019 21:20:42 +0100 [thread overview]
Message-ID: <87k16mkd45.fsf@gmx.de> (raw)
In-Reply-To: <CAN_Aq+p75z=MSAVrANp9tAfJO4hw9oxgQd5K0zDmkzsHkvTbnw@mail.gmail.com> (Duncan Greatwood's message of "Mon, 23 Dec 2019 09:34:21 -0800")
Duncan Greatwood <dgbulk@gmail.com> writes:
Hi Duncan,
>> If yes, your error is exactly the same as
>> bug#38648.
> [DG] OK, makes sense
>
> Regarding the discussion between Michael and Eli on the most efficient
> way to proceed, if you have a patch that can be applied to 26.2 I
> could certainly give it a try. Or I can try next version of emacs once
> released.
Well, you might try the patch applied to Emacs 27.0.50 for bug#38648 on
top of Emacs 26. Likely, it will apply.
<http://git.savannah.gnu.org/cgit/emacs.git/patch/lisp/progmodes/compile.el?id=0a10795d0bf4fe21997f907b7d6b1fe13517912b>
> If you want to try to prompt the relevant binary distributors to
> patch, I believe I am pretty typical for current macos emacs users in
> that emacs is installed via "brew cask install emacs" which I
> understand obtains its binary from https://emacsformacosx.com/.
I don't use macOS myself, and I don't know who is building this Emacs
version.
> Thanks.
Best regards, Michael.
next prev parent reply other threads:[~2019-12-23 20:20 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
2019-12-23 17:34 ` Duncan Greatwood
2019-12-23 20:20 ` Michael Albinus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k16mkd45.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=38718@debbugs.gnu.org \
--cc=dgbulk@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.