From: Richard Stallman <rms@gnu.org>
Subject: [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]]
Date: Wed, 03 Jan 2007 21:32:08 -0500 [thread overview]
Message-ID: <E1H2IOm-0002dQ-82@fencepost.gnu.org> (raw)
[I sent this message a week ago but did not get a response.]
Would someone please DTRT and ack?
------- Start of forwarded message -------
From: James Cloos <cloos@jhcloos.com>
To: emacs-devel@gnu.org
In-Reply-To: <E1GzG0T-0001eu-7N@fencepost.gnu.org> (Richard Stallman's message
of "Tue\, 26 Dec 2006 12\:22\:29 -0500")
Copyright: Copyright 2006 James Cloos
Date: Tue, 26 Dec 2006 13:58:12 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Cc: rms@gnu.org
Subject: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]
X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO
autolearn=failed version=3.0.4
|> ffap is not UTF-8 ready, I put the cursor on ./???? or whatever and it
|> acts like the file Doesn't exist.
I tried it on several filenames (all of which exist on my filesystem).
On every file where the first character was ASCII and was not modified
by a combining character, ffap worked as expected.
But on every file where the second character was a combining character
(such as the file named C?.utf8 -- that is a C followed by U+0336, which
is called COMBINING LONG STROKE OVERLAY) ffap failed to recognize the
string as being a filename. It also failed when the string started
with a non-ASCII character, such as a kanji or a greek character.
Some testing shows that (ffap-string-at-point) skips strings such as
those described above. I guess this is because of the default value
of ffap-string-at-point-mode-alist. For finding files it looks for
strings of "--:$+<>@-Z_a-z~*?", dropping "<@" from the beginning and
dropping "@>;.,!:" from the end. That first string needs to be
expanded to support non-ASCII characters which might be used for
filenames.
- -JimC
- --
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------
next reply other threads:[~2007-01-04 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 2:32 Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-10 23:05 [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]] Richard Stallman
2007-01-10 23:48 ` Stefan Monnier
2006-12-27 21:16 Richard Stallman
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=E1H2IOm-0002dQ-82@fencepost.gnu.org \
--to=rms@gnu.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 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).