From: Pascal Quesseveur <pquessev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Change in 28.1 in opening a file from grep results on Windows
Date: Tue, 12 Jul 2022 19:04:53 +0200 [thread overview]
Message-ID: <825yk28doq.fsf@gmail.com> (raw)
In-Reply-To: 83r12qwa0w.fsf@gnu.org
>"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> I know that the error comes from cmd.exe. But I wanted to see what
EZ> kind of commands trigger it.
EZ> Is the command that you have shown something you actually type from
EZ> Emacs? If so, for what purpose?
It is a build command using ant. When I launch the build from a file
whose path is the symlink it works, when I launch the build from a
file whose path is the real one it doesn't work.
EZ> So what is that "same command as before on file1.c"? And if you
EZ> invoke it, how does the error manifest itself? E.g., does Emacs
EZ> signal an error and/or enter the Lisp debugger and show Lisp
EZ> backtrace?
As I said, there is no Emacs error. It's just the compilation that
can't be run.
--
Pascal Quesseveur
pquessev@gmail.com
next prev parent reply other threads:[~2022-07-12 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 15:36 Change in 28.1 in opening a file from grep results on Windows Pascal Quesseveur
2022-07-12 16:01 ` Eli Zaretskii
2022-07-12 16:31 ` Pascal Quesseveur
2022-07-12 16:50 ` Eli Zaretskii
2022-07-12 17:04 ` Pascal Quesseveur [this message]
2022-07-12 17:13 ` Eli Zaretskii
2022-07-12 17:23 ` Pascal Quesseveur
2022-07-12 16:22 ` Eli Zaretskii
2022-07-12 16:56 ` Pascal Quesseveur
2022-07-12 17:09 ` Eli Zaretskii
2022-07-12 17:20 ` Pascal Quesseveur
2022-07-12 17:29 ` Eli Zaretskii
2022-07-12 17:41 ` Pascal Quesseveur
2022-07-12 20:07 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-13 12:14 ` Eli Zaretskii
2022-07-13 12:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-13 16:08 ` Pascal Quesseveur
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=825yk28doq.fsf@gmail.com \
--to=pquessev@gmail.com \
--cc=help-gnu-emacs@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.
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).