From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: BUG: ngnus-0.10 can't send messages
Date: Tue, 24 Jun 2008 15:37:10 +0200 [thread overview]
Message-ID: <87r6anned5.fsf@mat.ucm.es> (raw)
In-Reply-To: <b4m8wwvjc1n.fsf@jpl.org>
>>>>> "Katsumi" == Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>> Uwe Brauer wrote:
>> the question still puzzles me, why does everything work with
>> ngnus-0.6?
> Do you know where the regexp "\\<Mc\\([^aeiou]\\)" comes from?
> Isn't it in your XEmacs init file? GREP found no file containing
> "aeiou" in my system.
Still I don't understand why it works in 0.6.
But yes there are files with aeiou on my system
To start with my init file, which has
(defadvice mail-extract-address-components (after capitalize first activate)
"Capitalize names extracted from first.last@..., first_last@..., and
\"first last\" <...> addresses."
(let ((case-fold-search nil))
(if (or (string-match "\\`[a-z---]+\\([._][a-z---]+\\)+@"
(ad-get-arg 0)) ; ADDRESS
(string-match "\\`\"[a-z---]+\\( [a-z---]+\\)+\" <"
(ad-get-arg 0))) ; ADDRESS
(setcar ad-return-value
(capitalize (car ad-return-value))))))
(defadvice mail-extract-address-components (after capitalize-mc last activate)
"Fix capitalization of \"Mc\" names, e.g. \"Mcdonald\" -> \"McDonald\"."
(let ((full-name (car ad-return-value))
(case-fold-search nil)
(start 0))
(while (and full-name (string-match "\\<Mc\\([^aeiou]\\)" full-name start))
(aset full-name (match-beginning 1)
(upcase (aref full-name (match-beginning 1))))
(setq start (match-end 0)))))
It is also in
site-lisp/packages/ngnus-0.10/lisp/gnus-art.el
(defun gnus-button-mid-or-mail-heuristic (mid-or-mail)
In reftex
(defcustom reftex-abbrev-parameters '(4 2 "^aeiou" "aeiou")
The most likely culprit seem to me the defadvice things. I will
comment them out and see what happens, (still insisting that in 0.6 it
works): ok now gnus-0.10 works. The question is, how could this
defadvice function work again under 0.10???
> In addition, I found in and around `message-bogus-recipient-p'
> and `mail-extract-address-components' no `string-match' form in
> which the third argument `0' (or equivalent) is specified. So,
> I guess the backtrace might have reported the one caused by the
> one other than `mail-extract-address-components'. How about re-
> reproducing the problem after loading some doubtful el (not elc)
> files? Those will be the ones that the following program reports
> (type C-j at the end of the last line in the *scratch* buffer):
ok I will try that after having tried, that for should me this tricks.
Uwe Brauer
next prev parent reply other threads:[~2008-06-24 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87od60tp06.fsf@mat.ucm.es>
2008-06-18 18:05 ` Reiner Steib
[not found] ` <87hcbpkcb7.fsf@mat.ucm.es>
2008-06-23 17:57 ` Reiner Steib
2008-06-24 9:57 ` Uwe Brauer
2008-06-24 11:40 ` Katsumi Yamaoka
2008-06-24 13:37 ` Uwe Brauer [this message]
2008-06-24 17:29 ` Reiner Steib
2008-06-24 23:59 ` Katsumi Yamaoka
2008-06-25 11:33 ` Uwe Brauer
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=87r6anned5.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).