Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
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: Mon, 23 Jun 2008 19:57:40 +0200	[thread overview]
Message-ID: <v9od5sjap7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87hcbpkcb7.fsf@mat.ucm.es> (Uwe Brauer's message of "Thu, 19 Jun 2008 11:23:56 +0200")

[ Please send your reply to ding@gnus.org, see Mail-Followup-To. ]

On Thu, Jun 19 2008, Uwe Brauer wrote:

>>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>    > I don't think so.
>
>    > I can't reproduce (nor understand) this problem.  It seems that
>    > `mail-extract-address-components' returns something unexpected.
>    > Please show us what is returned in your version for the following
>    > expressions (use M-x ielm).  The current CVS HEAD code of
>    > `message-bogus-recipient-p' differs to ngnus-0.10, though it doesn't
>    > seem to be relevant.  But still, could you also try with current CVS
>    > HEAD?
>
> You mean I should download the current CVS version and not ngnus-0.10?

Yes.

>    > ,----[ M-x ielm RET ]
>    > | ELISP> (require 'mail-extr)
> here I got already a problem 
>
> --8<------------------------schnipp------------------------->8---
> Debugger entered--Lisp error: (void-function shell-directory-tracker)
>   shell-directory-tracker("(require 'mail-extr)\n")
>   run-hook-with-args(shell-directory-tracker "(require 'mail-extr)\n")
>   comint-send-input()
>   ielm-send-input()
>   ielm-return()
>   #<compiled-function nil "...(41)" [last-command-event pabbrev-mode
>   #pabbrev-expansion pabbrev-expansion-suggestions last-command
>   #prev-binding pabbrev-expand-maybe pabbrev-suggestions-goto-buffer
>   #pabbrev-expand nil key-binding char-to-string fboundp] 3
>   #("/home/oub/xemacs/site-lisp/versch/pabbrev.elc" . 18473) nil>() 
>   call-interactively(pabbrev-expand-maybe)
>   recursive-edit()
>   byte-code("..." [buffer-read-only noninteractive debugger-buffer
>   middlestart debugger-args debugger-batch-max-lines pop-to-buffer
>   debugger-mode debugger-setup-buffer count-lines 2 "...\n" message
>   buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable
>   "" nil recursive-edit standard-output] 3) 
>   debug(error (buffer-read-only #<buffer "*Article*">))
>   call-interactively(delete-blank-lines)
> --8<------------------------schnapp------------------------->8---
>
>    > | mail-extr
>    > | ELISP> (mail-extract-address-components "Uwe Brauer <oub@mat.ucm.es>" t)
>    > | (("Uwe Brauer" "oub@mat.ucm.es"))
>    > | 
>    > | ELISP> (nth 0 (mail-extract-address-components "Uwe Brauer
>    > <oub@mat.ucm.es>" t)) 
>    > | ("Uwe Brauer" "oub@mat.ucm.es")
>    > | 
>    > | ELISP> (cadr (nth 0 (mail-extract-address-components "Uwe
>    > Brauer <oub@mat.ucm.es>" t))) 
>    > | "oub@mat.ucm.es"
>    > | ELISP> (require 'message)
>    > | message
>    > | ELISP> (message-bogus-recipient-p "Uwe Brauer <oub@mat.ucm.es>")
>    > | nil
>    > | ELISP> emacs-version
>    > | "21.5  (beta27) \"fiddleheads\" (+CVS-20060704) XEmacs Lucid"
>    > | ELISP> 
>    > `----
> the other call do not work neither; all the time I obtain the same error.
> But now it seems that pabbrev might be the problem, a very nifty
> function which I use frequently


So it seem pabbrev breaks ielm?  Please try without pabbrev, starting
from "xemacs -vanilla -f ielm".  Replace "~/src/links/plain_No/lisp"
with the directory of No Gnus on your system.


,----[ xemacs -vanilla -f ielm ]
| *** Welcome to IELM ***  Type (describe-mode) for help.
| ELISP> (progn
|   (push "~/src/links/plain_No/lisp" load-path)
|   (car load-path))
| "~/src/links/plain_No/lisp"
| ELISP> (require 'mail-extr)
| mail-extr
| ELISP> (locate-library "mail-extr")
| "/usr/share/xemacs/xemacs-packages/lisp/mail-lib/mail-extr.elc"
| ELISP> (mail-extract-address-components "Uwe Brauer <oub@mat.ucm.es>" t)
| (("Uwe Brauer" "oub@mat.ucm.es"))
| 
| ELISP> (nth 0 (mail-extract-address-components "Uwe Brauer <oub@mat.ucm.es>" t))
| ("Uwe Brauer" "oub@mat.ucm.es")
| 
| ELISP> (cadr (nth 0 (mail-extract-address-components "Uwe Brauer <oub@mat.ucm.es>" t)))
| "oub@mat.ucm.es"
| ELISP> (require 'message)
| message
| ELISP> (locate-library "message")
| "/home/dept/ste/src/links/plain_No/lisp/message.elc"
| ELISP> (message-bogus-recipient-p "Uwe Brauer <oub@mat.ucm.es>")
| nil
| ELISP> emacs-version
| "21.5  (beta27) \"fiddleheads\" (+CVS-20060704) XEmacs Lucid"
| ELISP>
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2008-06-23 17:57 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 [this message]
2008-06-24  9:57       ` Uwe Brauer
2008-06-24 11:40         ` Katsumi Yamaoka
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=v9od5sjap7.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).