Thank you for the reply. But I don't have a write access to the
Emacs CVS, so I ask someone to install it.
Please email the patch and change log to emacs-devel
and ask someone to install it.
___
emacs-pretest-bug mailing list
In [EMAIL PROTECTED]
Richard Stallman [EMAIL PROTECTED] wrote:
Thank you for the reply. But I don't have a write access to the
Emacs CVS, so I ask someone to install it.
Please email the patch and change log to emacs-devel
and ask someone to install it.
It has already been
Please install your patch in the trunk. If it proves correct,
we can install it in 22.2.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
In [EMAIL PROTECTED] Richard Stallman wrote:
The way I posted, to make the syntax of all non-ASCII characters
`word', has a weakness. It is not effective to charsets that
are created after loading mail-extr.el.
So, what about the first proposed fix?
The one that patched this
In [EMAIL PROTECTED] Kenichi Handa wrote:
In article [EMAIL PROTECTED], Katsumi Yamaoka [EMAIL PROTECTED] writes:
The way I posted, to make the syntax of all non-ASCII characters
`word', has a weakness. It is not effective to charsets that
are created after loading mail-extr.el.
As a
The way I posted, to make the syntax of all non-ASCII characters
`word', has a weakness. It is not effective to charsets that
are created after loading mail-extr.el.
Regards,
So, what about the first proposed fix?
The one that patched this particular function?
If people have doubts that changing that syntax table is generally
correct, what about the previous patch that alters just the
particular function?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
In article [EMAIL PROTECTED], Richard Stallman [EMAIL PROTECTED] writes:
If people have doubts that changing that syntax table is generally
correct, what about the previous patch that alters just the
particular function?
At the moment, I don't have a time to study the code and his
patch. So,
think it needs time to be tested widely. I'm not well informed
about RFC2822 and what mail-extr.el does (especially the voodoo
operation, which is disabled by default for Japanese names), too.
RFC2822 only talks about the transmission-format, which is made of bytes,
not chars. It's probably
In [EMAIL PROTECTED] Kenichi Handa wrote:
In article [EMAIL PROTECTED], Richard Stallman [EMAIL PROTECTED] writes:
If people have doubts that changing that syntax table is generally
correct, what about the previous patch that alters just the
particular function?
At the moment, I don't have
In article [EMAIL PROTECTED], Katsumi Yamaoka [EMAIL PROTECTED] writes:
So, my suggestion it to do that and see if it works well if
no one can investigate the code and RFC-822.
The way I posted, to make the syntax of all non-ASCII characters
`word', has a weakness. It is not effective to
In [EMAIL PROTECTED] Kenichi Handa wrote:
In article [EMAIL PROTECTED], Katsumi Yamaoka [EMAIL PROTECTED] writes:
[...] and the patch[1] I posted first is better.
But please don't merge it hastily if you have a doubt even if it
is little.
I don't know about the code of mail-extr.el nor the
Sorry for the late response on this matter.
In article [EMAIL PROTECTED], Katsumi Yamaoka [EMAIL PROTECTED] writes:
In [EMAIL PROTECTED] Katsumi Yamaoka wrote:
I hope this is fixed in Emacs 22.2 (or possibly 22.1). I've been
annoyed that `mail-extract-address-component' sometimes fails to
In [EMAIL PROTECTED] Kenichi Handa wrote:
Sorry for the late response on this matter.
Please don't mind, since the most important thing now is to release
Emacs 22.1.
In article [EMAIL PROTECTED], Katsumi Yamaoka [EMAIL PROTECTED] writes:
I hope this is fixed in Emacs 22.2 (or possibly
In [EMAIL PROTECTED] Katsumi Yamaoka wrote:
*** mail-extr.el~ Sun Jan 21 21:57:52 2007
--- mail-extr.el Mon May 14 03:16:51 2007
[...]
!(not (eq (char-after ? ))
Sorry, this line has to be corrected into:
!
Hi,
I hope this is fixed in Emacs 22.2 (or possibly 22.1). I've been
annoyed that `mail-extract-address-component' sometimes fails to
parse addresses containing non-ASCII names correctly. Japanese
people often use their native names in the From header. Since
they sometimes use non-ASCII
16 matches
Mail list logo
