Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: ding@gnus.org, bugs@gnus.org
Subject: Re: BUG: ngnus-0.10 can't send messages
Date: Tue, 24 Jun 2008 20:40:52 +0900	[thread overview]
Message-ID: <b4m8wwvjc1n.fsf@jpl.org> (raw)
In-Reply-To: <4860C51B.5030604@mat.ucm.es>

>>>>> Uwe Brauer wrote:
> the question still puzzles me, why does everything work with ngnus-0.6?

>>>>> In <87od60tp06.fsf@mat.ucm.es> Uwe Brauer wrote:
> Debugger entered--Lisp error: (wrong-type-argument stringp ("Uwe Brauer" "oub@mat.ucm.es"))
>   string-match("\\<Mc\\([^aeiou]\\)" ("Uwe Brauer" "oub@mat.ucm.es") 0)
>   mail-extract-address-components("Uwe Brauer <oub@mat.ucm.es>" t)
>   message-bogus-recipient-p("Uwe Brauer <oub@mat.ucm.es>")
>   message-check-recipients()
>   message-fix-before-sending()
>   message-send(nil)
>   message-send-and-exit(nil)
>   call-interactively(message-send-and-exit)

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.

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

(with-temp-buffer
  (emacs-lisp-mode)
  (let ((cur (current-buffer))
	files)
    (dolist (dir load-path)
      (dolist (file (directory-files dir t "\\.el\\(\\.gz\\)?\\'"))
	(message "%s" file)
	(condition-case nil
	    (progn
	      (insert-file-contents file)
	      (goto-char (point-min))
	      (while (re-search-forward "([\t\n\r ]*string-match[\t\n\r ]"
					nil t)
		(goto-char (match-beginning 0))
		(condition-case nil
		    (when (= (length (read cur)) 4)
		      (push file files)
		      (goto-char (point-max)))
		  (error
		   (goto-char (match-end 0)))))
	      (erase-buffer))
	  (error))))
    (nreverse files)))



  reply	other threads:[~2008-06-24 11:40 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 [this message]
2008-06-24 13:37           ` Uwe Brauer
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=b4m8wwvjc1n.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=oub@mat.ucm.es \
    /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).