From: Eli Zaretskii <eliz@gnu.org>
To: Guido Kraemer <gkraemer@bgc-jena.mpg.de>
Cc: 28870@debbugs.gnu.org
Subject: bug#28870: 25.3; find-file-at-point with spaces in path
Date: Tue, 17 Oct 2017 19:43:26 +0300 [thread overview]
Message-ID: <83y3o9endd.fsf@gnu.org> (raw)
In-Reply-To: <1bfdb618-94c0-c8cf-8c88-a1375a5805ad@bgc-jena.mpg.de> (message from Guido Kraemer on Mon, 16 Oct 2017 21:35:58 +0200)
tags 28870 wishlist
thanks
> From: Guido Kraemer <gkraemer@bgc-jena.mpg.de>
> Date: Mon, 16 Oct 2017 21:35:58 +0200
>
> find-file-at-point does not work correctly if there are spaces in the
> path, but also exists in emacs 26.0.90.1 to reproduce:
>
> 1) create the file "~/new folder/New Folder/New Empty File"
> 2) emacs -q
> 3) go to *scratch* buffer
> 4) put the following in the scratch buffer:
>
> "~/new folder/New Folder/New Empty File"
> ".emacs.d/init.el"
>
> 5) place point on each and run `find-file-at-point`
>
> Observed bevior: the second line works fine, the first line does not
> complete correctly, see also here:
find-file-at-point doesn't currently support file names with spaces,
it's a missing feature. Patches to add that are welcome.
FWIW, I think if such a feature is added, it should support several
kinds of quoting: `..', '..', "..", ‘..’, etc., because we are talking
about free text, where such file names could be quoted in many ways.
Thanks.
next prev parent reply other threads:[~2017-10-17 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 19:35 bug#28870: 25.3; find-file-at-point with spaces in path Guido Kraemer
2017-10-17 16:43 ` Eli Zaretskii [this message]
[not found] ` <b0233c2e-10d2-fc57-344f-38c30b405f40@bgc-jena.mpg.de>
2017-10-17 18:44 ` Eli Zaretskii
2021-01-07 16:16 ` H. Dieter Wilhelm
2021-09-03 7:18 ` Lars Ingebrigtsen
2021-09-03 16:22 ` H. Dieter Wilhelm
[not found] ` <8635pip16d.fsf@duenenhof-wilhelm.de>
[not found] ` <87r1d1p33c.fsf@gnus.org>
2021-10-04 12:51 ` Eli Zaretskii
2021-10-04 20:08 ` H. Dieter Wilhelm
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=83y3o9endd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28870@debbugs.gnu.org \
--cc=gkraemer@bgc-jena.mpg.de \
/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.