From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28870@debbugs.gnu.org, Guido Kraemer <gkraemer@bgc-jena.mpg.de>
Subject: bug#28870: 25.3; find-file-at-point with spaces in path
Date: Fri, 03 Sep 2021 18:22:36 +0200 [thread overview]
Message-ID: <1MiuGK-1msFSd0qFY-00exbp@mrelayeu.kundenserver.de> (raw)
In-Reply-To: <1bfdb618-94c0-c8cf-8c88-a1375a5805ad@bgc-jena.mpg.de>
From Emacs master: In the NEWS file:
---
*** New variable 'ffap-file-name-with-spaces'.
If non-nil, 'find-file-at-point' and friends will try to guess more
expansively to identify a file name with spaces.
DieterAm 03.09.2021 09:18 schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:
>
> > 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... ;-)
>
> So it seems like this has been fixed now (with that setting), so I'm
> closing this bug report.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-03 16:22 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
2021-09-03 7:18 ` Lars Ingebrigtsen
2021-09-03 16:22 ` H. Dieter Wilhelm [this message]
[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=1MiuGK-1msFSd0qFY-00exbp@mrelayeu.kundenserver.de \
--to=dieter@duenenhof-wilhelm.de \
--cc=28870@debbugs.gnu.org \
--cc=gkraemer@bgc-jena.mpg.de \
--cc=larsi@gnus.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.