From: Peter Povinec <spepo.42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55016@debbugs.gnu.org
Subject: bug#55016: 28.1; xref-find-references finds no matches if project dir contains a space
Date: Tue, 19 Apr 2022 10:57:29 -0700 [thread overview]
Message-ID: <CAJDw7KtwvH=JxaTOu=W5cgSC0ihOXyEV--R1eyMZHrvww02ALg@mail.gmail.com> (raw)
In-Reply-To: <8335i9ug94.fsf@gnu.org>
On Tue, Apr 19, 2022 at 10:37 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> Actually, one more idea: perhaps the quoting makes things first
> because your file names begin with "~/"? In that case, doing
> something like this instead should do better:
>
> (shell-quote-argument (expand-file-name rootdir))
That works! Both 'space dir' and 'nospace' dir cases work the same way now.
BTW, the symlinks are not essential to my recipe. You can instead
create two new
directories and copy in xref.el in Step 1.
Thanks for your help and super fast response.
Peter
next prev parent reply other threads:[~2022-04-19 17:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJDw7KtwvH=JxaTOu=W5cgSC0ihOXyEV--R1eyMZHrvww02ALg@mail.gmail.com' \
--to=spepo.42@gmail.com \
--cc=55016@debbugs.gnu.org \
--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 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.