unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]]
@ 2006-12-27 21:16 Richard Stallman
  0 siblings, 0 replies; 4+ messages in thread
From: Richard Stallman @ 2006-12-27 21:16 UTC (permalink / raw)


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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]]
@ 2007-01-04  2:32 Richard Stallman
  0 siblings, 0 replies; 4+ messages in thread
From: Richard Stallman @ 2007-01-04  2:32 UTC (permalink / 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 -------

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]]
@ 2007-01-10 23:05 Richard Stallman
  2007-01-10 23:48 ` Stefan Monnier
  0 siblings, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2007-01-10 23:05 UTC (permalink / raw)


[I sent this message twice 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 -------

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-01-10 23:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-27 21:16 [cloos@jhcloos.com: Re: [jidanni@jidanni.org: ffap not UTF-8 ready]] Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2007-01-04  2:32 Richard Stallman
2007-01-10 23:05 Richard Stallman
2007-01-10 23:48 ` Stefan Monnier

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