all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Rajesh Vaidheeswarran" <rv@gnu.org>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: ffap not UTF-8 ready
Date: Thu, 12 Oct 2006 21:18:19 +0530	[thread overview]
Message-ID: <a4cf0b680610120848h715ae460m3997fdde9cdeb135@mail.gmail.com> (raw)
In-Reply-To: <E1GXkhN-00088v-Ka@fencepost.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]

I don't regularly read emacs-devel mails. I will, however, check this out
when I return to the US in a couple of weeks.

rv

On 10/12/06, Richard Stallman <rms@gnu.org> wrote:
>
> [I sent this message a week ago but did not get a response.]
>
>     > Since we already have regexp constructs for multibyte
>     > characters, I guess we should make ffap use them now.
>
>     I agree.  In ffap.el, similar regexps are used not only in
>     ffap-string-at-point-mode-alist but also in the other
>     places.  So, I'd like to ask the maintainer of that file to
>     check throughout the file.
>
> Rajesh Vaidheeswarran <rv@gnu.org>, do you read me?
>
>

[-- Attachment #1.2: Type: text/html, Size: 1126 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

      reply	other threads:[~2006-10-12 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GSrVS-0000rW-Qr@jidanni.org>
2006-10-02  7:22 ` ffap not UTF-8 ready Kenichi Handa
2006-10-02 13:49   ` Stefan Monnier
2006-10-02 21:05   ` Kevin Ryde
2006-10-03  1:20     ` Kenichi Handa
     [not found]       ` <E1GUliX-0003XK-Lx@fencepost.gnu.org>
2006-10-03 23:26         ` Kenichi Handa
2006-10-04 16:22           ` Richard Stallman
2006-10-11 20:29           ` Richard Stallman
2006-10-12 15:48             ` Rajesh Vaidheeswarran [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=a4cf0b680610120848h715ae460m3997fdde9cdeb135@mail.gmail.com \
    --to=rv@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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 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.