From: Peter Povinec <spepo.42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55016@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#55016: 28.1; xref-find-references finds no matches if project dir contains a space
Date: Mon, 25 Apr 2022 18:05:41 -0700 [thread overview]
Message-ID: <CAJDw7KseZso8PN_L3bf4vW-Dc8WbpMVfT7xQmXYa7Uy432xOJA@mail.gmail.com> (raw)
In-Reply-To: <83ilqznj23.fsf@gnu.org>
On Sat, Apr 23, 2022 at 10:32 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> Thanks. Peter, can you try the patch proposed by Dmitry and see if it
> works in your case?
I am having a hard time applying that patch. First, it has long lines that
have been wrapped at 80. Second, even after manually fixing those I get
this error from git apply:
error: patch fragment without header at line 29: @@ -190,10 +193,10 @@
semantic-symref-parse-tool-output-one-line
Is it just me, or does it fail for you too?
What is the best way to apply such a patch to my local sources?
Thanks,
Peter
next prev parent reply other threads:[~2022-04-26 1:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 4:52 bug#55016: 28.1; xref-find-references finds no matches if project dir contains a space Peter Povinec
2022-04-19 7:13 ` Eli Zaretskii
2022-04-19 17:06 ` Peter Povinec
2022-04-19 17:32 ` Eli Zaretskii
2022-04-19 17:36 ` Eli Zaretskii
2022-04-19 17:57 ` Peter Povinec
2022-04-19 18:17 ` Eli Zaretskii
2022-04-19 18:24 ` Eli Zaretskii
2022-04-24 2:00 ` Dmitry Gutov
2022-04-24 5:31 ` Eli Zaretskii
2022-04-25 2:08 ` Dmitry Gutov
2022-04-25 11:48 ` Eli Zaretskii
2022-04-26 2:05 ` Dmitry Gutov
2022-04-26 12:00 ` Eli Zaretskii
2022-04-26 12:28 ` Dmitry Gutov
2022-04-26 12:36 ` Eli Zaretskii
2022-04-27 1:57 ` Dmitry Gutov
2022-04-27 13:53 ` Eli Zaretskii
2022-04-26 1:05 ` Peter Povinec [this message]
2022-04-26 2:07 ` Dmitry Gutov
2022-04-26 4:57 ` Peter Povinec
2022-04-26 11:18 ` Eli Zaretskii
2022-04-26 12:30 ` Dmitry Gutov
2022-04-27 3:00 ` Peter Povinec
2022-10-31 1:00 ` Dmitry Gutov
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=CAJDw7KseZso8PN_L3bf4vW-Dc8WbpMVfT7xQmXYa7Uy432xOJA@mail.gmail.com \
--to=spepo.42@gmail.com \
--cc=55016@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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).