all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: , 28870@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	stefan@marxist.se, guido.kraemer@uni-leipzig.de
Subject: bug#28870: 25.3; find-file-at-point with spaces in path
Date: Mon, 04 Oct 2021 22:08:15 +0200	[thread overview]
Message-ID: <86k0iso8nk.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <83czol6jgy.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Oct 2021 15:51:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Yes, ffap, spaces and Windows is a general problem, I seem to recall?
>> But I don't remember the details; I don't use Windows myself.
>
> Spaces in file names is not specific to Windows, although Windows
> systems tend to have more of them.  I suggest to dig deeper into
> ffap.el to understand what exactly trips it on Windows.

For your information: Orgmode 9.4 manages already to open its links -
like [[PATH][LINK_NAME]] - with spaces in paths on Windows (and Linux)!

-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany





      reply	other threads:[~2021-10-04 20:08 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
     [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 [this message]

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=86k0iso8nk.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=28870@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=guido.kraemer@uni-leipzig.de \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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.