Re: ffap not UTF-8 ready

[Kenichi Handa <handa@m17n.org>]

In article <87y7ryjuml.fsf@zip.com.au>, Kevin Ryde <user42@zip.com.au> writes:

> Kenichi Handa <handa@m17n.org> writes:
> >
> > It seems that this is because the variable
> > ffap-string-at-point-mode-alist doesn't contain a multibyte
> > character in CHARS.

> Perhaps "(thing-at-point 'filename)", in thing-at-point-file-name-chars,
> has the same problem.

!! The variable thing-at-point-file-name-chars is defined as
    "-~/[:alnum:]_.${}#%,:".
I've forgotten about [:XXX:] notation.  I've just read
src/regex.c and found that [:alnum:] also works for
multibyte characters (it matches with a multibyte character
whose syntax is "word"), and [:multibyte:] is available too.
So, the current definition of thing-at-point-file-name-chars
works in most cases.  But, considering that a non-word
multibyte character can also be used in a file name,
perhaps, defining that as
   "-~/[:alnum:][:multibyte:]_.${}#%,:"
is better.

And, I think ffap.el should also use that kind of pattern
instead of something like this: "0-9A-Za-z".

---
Kenichi Handa
handa@m17n.org