From: jari <jari.aalto@cante.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hochberg@dmhsoftware.com, 8439@debbugs.gnu.org
Subject: bug#8439: [PATCH] ffap.el -- detect paths with spaces (v2)
Date: Fri, 19 Oct 2012 13:05:56 +0300 [thread overview]
Message-ID: <20121019100556.GT19374@picasso.cante.net> (raw)
In-Reply-To: <83a9vi23mi.fsf@gnu.org>
On 2012-10-19 11:49, Eli Zaretskii wrote:
| >
| > 1. New variable ffap-paths-with-spaces controls if the behavior is in use.
| > By default it is set to "t" in Windows/Cygwin where spaces in paths
| > are encountered.
|
| GNU Coding Standards frown upon using "path" for anything except
| PATH-style lists of directories. Use "file name" or "leading
| directories" instead.
|
| > 2. The "path skipping" is based on finding longest distance:
| >
| > - from first "drive letter", "/" or "\"
| > - until last "/", "\" followed by last non-matching-char-not-usually-found-in-file-names
|
| What will this do to text such as the one below?
|
| C:\emacs\bin\prog1.exe on Windows or /usr/bin/prog1 on Unix.
User can enable/disable if spaces are taken into account. If enabled,
the result is:
"C:\emacs\bin\prog1.exe on Windows or /usr/bin/prog1"
If disabled, depending on cursor position:
"C:\emacs\bin\prog1.exe"
"/usr/bin/prog1"
If you have strategiy to make it better, please suggest.
| > 3. In Cygwin Emacs the paths are expected to be in "/cygdrive/<letter>/"
| > format.
|
| What about Posix-standard /foo/bar/baz, which is the usual case on
| Cygwin?
Only "<drive letter>:" is converted into "/cygdrive/<drive letter>" under
Cygwin.
Jari
next prev parent reply other threads:[~2012-10-19 10:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 15:24 bug#8439: [PATCH] ffap.el -- detect paths with spaces Jari Aalto
2011-07-03 23:29 ` Lars Magne Ingebrigtsen
2012-10-19 7:39 ` bug#8439: [PATCH] ffap.el -- detect paths with spaces (v2) Jari Aalto
2012-10-19 9:49 ` Eli Zaretskii
2012-10-19 10:05 ` jari [this message]
2012-10-19 11:15 ` Yigal Hochberg
2012-10-19 11:22 ` Eli Zaretskii
2012-10-19 12:15 ` Nicolas Richard
2012-10-19 21:47 ` Andrew W. Nosenko
2012-10-19 22:23 ` Eli Zaretskii
2012-10-19 22:36 ` Yigal Hochberg
2012-10-19 22:57 ` Andrew W. Nosenko
2012-10-19 23:24 ` Yigal Hochberg
2012-10-20 1:45 ` Stefan Monnier
2012-10-20 11:01 ` Juri Linkov
2012-10-19 8:35 ` Jari Aalto
2012-10-20 1:44 ` Stefan Monnier
2012-10-20 1:49 ` Daniel Colascione
2012-10-20 7:56 ` bug#8439: [PATCH] ffap.el -- detect paths with spaces (v3) jari
2012-10-20 8:45 ` bug#8439: [PATCH] ffap.el -- detect paths with spaces (v4) jari
2012-10-20 10:20 ` Eli Zaretskii
2012-10-21 0:18 ` Stefan Monnier
2012-10-21 8:07 ` Jari Aalto
2019-11-23 13:31 ` bug#6695: " Lars Ingebrigtsen
2020-08-14 13:08 ` Lars Ingebrigtsen
2020-08-15 9:07 ` Eli Zaretskii
2020-08-15 10:13 ` Lars Ingebrigtsen
2012-10-20 8:11 ` bug#8439: [PATCH] ffap.el -- detect paths with spaces (v2) Eli Zaretskii
2012-10-21 0:16 ` Stefan Monnier
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=20121019100556.GT19374@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=8439@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hochberg@dmhsoftware.com \
/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).