GNU bug report logs -
#11594
message-send-and-exit now fails
Previous Next
Reported by: Jim Meyering <jim <at> meyering.net>
Date: Thu, 31 May 2012 08:20:02 UTC
Severity: important
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11594 in the body.
You can then email your comments to 11594 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Thu, 31 May 2012 08:20:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jim Meyering <jim <at> meyering.net>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 31 May 2012 08:20:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I built emacs from the latest on the trunk and found
that I can no longer send mail in the usual manner (using gnus).
It worked fine with a snapshot from 2012-05-24.09h10 UTC.
Here's how it fails, now:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
auth-source-search(:host "localhost" :port "smtp" :user nil :max 1 :require nil :create nil)
smtpmail-try-auth-methods(#<process smtpmail> (dsn 8bitmime enhancedstatuscodes etrn size) "localhost" "smtp" nil)
byte-code("...elided..." [host process-buffer buffer-undo-list coding-system-for-write coding-system-for-read port get-buffer-create format "*trace of SMTP session to %s*" t erase-buffer binary open-network-stream "smtpmail" :type :return-list :capability-command "EHLO %s.\n" smtpmail-fqdn :end-of-command "^[0-9]+ .*.\n" :success "^2.*\n" :always-query-capabilities :starttls-function #[(capabilities) "\301\302\"\205.\303\207" [capabilities string-match "[ -]STARTTLS" "STARTTLS.\n"] 3] :client-certificate :use-starttls-if-possible throw done plist-get :error "Unable to contact server" set-process-filter smtpmail-process-filter :greeting smtpmail-response-code "No greeting: %s" 400 "Connection not allowed: %s" set-buffer-process-coding-system raw-text-unix make-local-variable smtpmail-read-point :capabilities smtpmail-command-or-throw "HELO %s" delete "" split-string ...] 24)
smtpmail-via-smtp(("11557 <at> debbugs.gnu.org" "monnier <at> iro.umontreal.ca" "rgm <at> gnu.org") #<buffer smtpmail temp>)
smtpmail-send-it()
message-smtpmail-send-it()
#[nil " \207" [message-send-mail-function] 1]()
gnus-agent-send-mail()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit nil nil)
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#11594
; Package
emacs,gnus
.
(Thu, 31 May 2012 18:33:01 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
Jim Meyering writes:
> I built emacs from the latest on the trunk and found
> that I can no longer send mail in the usual manner (using gnus).
Actually, Gnus is completely hosed and doesn't even start up for me and
it appears that the auth code is involved (as I could not find any
suspect changes in Gnus between the last working version and yesterdays
pull).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#11594
; Package
emacs,gnus
.
(Thu, 31 May 2012 18:58:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 11594 <at> debbugs.gnu.org (full text, mbox):
Achim Gratz <Stromeko <at> nexgo.de> writes:
> Jim Meyering writes:
>> I built emacs from the latest on the trunk and found
>> that I can no longer send mail in the usual manner (using gnus).
>
> Actually, Gnus is completely hosed and doesn't even start up for me and
> it appears that the auth code is involved (as I could not find any
> suspect changes in Gnus between the last working version and yesterdays
> pull).
The byte compiler seems broken:
emacs -Q
(setq m (byte-compile '(lambda () (defmacro m ()) (m))))
#[nil "\300\301\302\303B\"\210\301 \207" [defalias m macro #[nil "\300\207" [nil] 1]] 4]
(funcall m)
=> error: (invalid-function m)
In emacs-24 branch:
#[nil "\300\301\302\"\210\303\207" [defalias m (macro . #[nil "\300\207" [nil] 1]) nil] 3]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Thu, 31 May 2012 20:04:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 11594 <at> debbugs.gnu.org (full text, mbox):
Johan Bockgård <bojohan <at> gnu.org> writes:
> The byte compiler seems broken:
>
> emacs -Q
>
> (setq m (byte-compile '(lambda () (defmacro m ()) (m))))
>
> #[nil "\300\301\302\303B\"\210\301 \207" [defalias m macro #[nil "\300\207" [nil] 1]] 4]
>
> (funcall m)
>
> => error: (invalid-function m)
byte code:
args: nil
0 constant defalias
1 constant m
2 constant macro
3 constant <compiled-function>
args: nil
0 constant nil
1 return
4 cons
5 call 2
6 discard
7 constant m
8 call 0
9 return
> In emacs-24 branch:
>
> #[nil "\300\301\302\"\210\303\207" [defalias m (macro . #[nil "\300\207" [nil] 1]) nil] 3]
byte code:
args: nil
0 constant defalias
1 constant m
2 constant <compiled macro>
args: nil
0 constant nil
1 return
3 call 2
4 discard
5 constant nil
6 return
There are two differences:
- (cons 'macro #[nil ...]) vs '(macro . #[nil ...]) (a performance
regression)
- (m) is not macro-expanded
Andreas.
--
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Thu, 31 May 2012 21:42:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 11594 <at> debbugs.gnu.org (full text, mbox):
Andreas Schwab <schwab <at> linux-m68k.org> writes:
> There are two differences:
>
> - (cons 'macro #[nil ...]) vs '(macro . #[nil ...]) (a performance
> regression)
> - (m) is not macro-expanded
Actually, this doesn't seem to be responsible.
I think the bug is in this part:
2012-05-30 Stefan Monnier <monnier <at> iro.umontreal.ca>
...
(byte-compile-output-file-form): Move print-vars binding.
(byte-compile-output-docform): Simplify accordingly.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Thu, 31 May 2012 22:05:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 11594 <at> debbugs.gnu.org (full text, mbox):
Johan Bockgård <bojohan <at> gnu.org> writes:
> I think the bug is in this part:
>
> 2012-05-30 Stefan Monnier <monnier <at> iro.umontreal.ca>
>
> ...
> (byte-compile-output-file-form): Move print-vars binding.
> (byte-compile-output-docform): Simplify accordingly.
... since the #N= stuff seems to be mostly missing in the elc files now.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Fri, 01 Jun 2012 01:31:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 11594 <at> debbugs.gnu.org (full text, mbox):
> There are two differences:
> - (cons 'macro #[nil ...]) vs '(macro . #[nil ...]) (a performance
> regression)
> - (m) is not macro-expanded
Actually, I think his tests are buggy. When I try it on Emacs-24 and
Emacs-23, the macro is not expanded either. As for the performance,
the difference only applies to non-toplevel defmacros.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#11594
; Package
emacs
.
(Fri, 01 Jun 2012 16:29:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 11594 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>> There are two differences:
>
>> - (cons 'macro #[nil ...]) vs '(macro . #[nil ...]) (a performance
>> regression)
>> - (m) is not macro-expanded
>
> Actually, I think his tests are buggy.
Yes, I realized this. What causes the problems is that print-circle is
not bound correctly. See my other posts in this thread.
Reply sent
to
Stefan Monnier <monnier <at> iro.umontreal.ca>
:
You have taken responsibility.
(Fri, 01 Jun 2012 19:53:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jim Meyering <jim <at> meyering.net>
:
bug acknowledged by developer.
(Fri, 01 Jun 2012 19:53:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 11594-done <at> debbugs.gnu.org (full text, mbox):
> Yes, I realized this. What causes the problems is that print-circle is
> not bound correctly. See my other posts in this thread.
Indeed, eliminating print-circle from byte-compile-output-docform was
correct when I did it (at which point -defmumble did not call
byte-compile-output-docform any more), but later I re-added the call to
byte-compile-output-docform and forgot to re-add the corresponding
print-circle. Thanks for helping me catch it, should be fixed now,
Stefan
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 30 Jun 2012 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 12 years and 130 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.