GNU bug report logs - #17089
Fw: bug#17084: It must be a bug

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17089 in the body.
You can then email your comments to 17089 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jakub Jankiewicz <jcubic <at> onet.pl>
To: bug-gnu-emacs <at> gnu.org
Subject: Fw: bug#17084: It must be a bug
Date: Mon, 24 Mar 2014 17:32:01 +0100

[Message part 1 (text/plain, inline)]

Forget about the list.

Begin forwarded message:

Date: Mon, 24 Mar 2014 17:30:58 +0100
From: Jakub Jankiewicz <jcubic <at> onet.pl>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Subject: Re: bug#17084: It must be a bug


It pup up message with `unread-command-char` `debug-on-error' have no effect,
it don't enter debuger. And it have nothing to do with my config since when I
load .emacs file using load-file it work fine, I enter debuger. Also I run
emacs with --debug-init.

So it's wrong message and debuger don't work.

The *Messages* have:

Entering debugger...
message: Symbol's value as variable is void: unread-command-char

also *Backtrace* buffer is empty and it's not show up. I have the same when I
try to execute non-exiting function:

(foobar)

foobar: Symbol's value as variable is void: unread-command-char

It's Emacs fault since my .emacs run fine when I run it using load-file.

PS: are there other files that Emacs can run on init, maybe I miss something?

On Mon, 24 Mar 2014 16:53:41 +0100
Michael Heerdegen <michael_heerdegen <at> web.de> wrote:

> Jakub Jankiewicz <jcubic <at> onet.pl> writes:
> 
> > When I run emacs -q and run M-x load-file "~/.emacs" I don't get that
> > message and have normal message with backtrace.
> 
> I'm not sure what this bug report is exactly about.  That the debugger
> doesn't pop up in your situation?  Note that this is controlled by the
> user option `debug-on-error'.
> 
> Or is it about the error you get about `unread-command-char' when
> loading your Emacs?  Then you should bisect your config file and try to
> find out what causes the error, i.e., please post a recipe starting from
> emacs -Q reproducing the problem.  Also a backtrace of the error you get
> would be helpful.
> 
> Michael.

--
Jakub Jankiewicz, Web Developer
http://jcubic.pl


--
Jakub Jankiewicz, Web Developer
http://jcubic.pl

[signature.asc (application/pgp-signature, attachment)]

Message #8 received at 17089 <at> debbugs.gnu.org (full text, mbox):

From: Jakub Jankiewicz <jcubic <at> onet.pl>
To: 17089 <at> debbugs.gnu.org
Subject: Re: bug#17089: Acknowledgement (Fw: bug#17084: It must be a bug)
Date: Mon, 24 Mar 2014 17:42:28 +0100

[Message part 1 (text/plain, inline)]

Ignore this.

On Mon, 24 Mar 2014 16:33:03 +0000
help-debbugs <at> gnu.org (GNU bug Tracking System) wrote:

> Thank you for filing a new bug report with debbugs.gnu.org.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  bug-gnu-emacs <at> gnu.org
> 
> If you wish to submit further information on this problem, please
> send it to 17089 <at> debbugs.gnu.org.
> 
> Please do not send mail to help-debbugs <at> gnu.org unless you wish
> to report a problem with the Bug-tracking system.
> 

--
Jakub Jankiewicz, Web Developer
http://jcubic.pl

[signature.asc (application/pgp-signature, attachment)]

Message #11 received at 17089 <at> debbugs.gnu.org (full text, mbox):

From: Stefan <monnier <at> IRO.UMontreal.CA>
To: Jakub Jankiewicz <jcubic <at> onet.pl>
Cc: 17089 <at> debbugs.gnu.org
Subject: Re: bug#17089: Fw: bug#17084: It must be a bug
Date: Mon, 24 Mar 2014 14:18:58 -0400

> message: Symbol's value as variable is void: unread-command-char

Look for unread-command-char in all your .el and .elc files and rename
it to unread-command-event.

`unread-command-char' is an old name that's been obsolete for many years
and we finally got rid of it.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.