unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Guido Kraemer <gkraemer@bgc-jena.mpg.de>, 28870@debbugs.gnu.org
Subject: bug#28870: 25.3; find-file-at-point with spaces in path
Date: Thu, 07 Jan 2021 17:16:21 +0100	[thread overview]
Message-ID: <86czygyb6y.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <83y3o9endd.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Oct 2017 19:43:26 +0300")

Hello 

While working on a cheap solution for my own nuisances on Windows I
found that for the upcoming Gnu Emacs-28 setting

(setq ffap-file-name-with-spaces 1)

is working quite fine!  FYI: ffap is checking if the file or path
exists.  So ffap-string-at-point might work for test strings but then
ffap is more reluctant... ;-)

     Dieter

Eli Zaretskii <eliz@gnu.org> writes:

> 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.
>
>
>
>

-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany





  parent reply	other threads:[~2021-01-07 16:16 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
     [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 [this message]
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

  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=86czygyb6y.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=28870@debbugs.gnu.org \
    --cc=eliz@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 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).