bug#17084: undefined variable access trigger "variable is void: unread-command-char"

bug#17084: undefined variable access trigger "variable is void: unread-command-char"

[Jakub Jankiewicz]

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

whenever I use undefined varaible this message is triggered:

(message "%s" some-undefined-variable)

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

(in *Messages* buffer)

or

(mapcar 'car some-undefined-var)

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

when it's in .emacs file or when I call eval-last-sexp (C-x C-e)

Strange but when I call emacs -q I don't have that error I have
message from debuger (*Backtrace* buffer)

Emacs version:

GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.8.2) of 2013-07-27 on
roseapple, modified by Debian

I don't know what inside by .emacs is causing this, I don't have
unread-command-char in any mode I'm using.

Any idea how to find the root of the bug?

--
𝑱𝒂𝒌𝒖𝒃 𝑱𝒂𝒏𝒌𝒊𝒆𝒘𝒊𝒄𝒛 (𝑊𝑒𝑏 𝐷𝑒𝑣𝑒𝑙𝑜𝑝𝑒𝑟)
http://jcubic.pl

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

bug#17084: It must be a bug

[Jakub Jankiewicz]

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

When I run emacs -q and run M-x load-file "~/.emacs" I don't get that message
and have normal message with backtrace.

So this must be somewhere in Emacs not in my customizations.

--
𝑱𝒂𝒌𝒖𝒃 𝑱𝒂𝒏𝒌𝒊𝒆𝒘𝒊𝒄𝒛 (𝑊𝑒𝑏 𝐷𝑒𝑣𝑒𝑙𝑜𝑝𝑒𝑟)
http://jcubic.pl

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

bug#17084: It must be a bug

[Michael Heerdegen]

Jakub Jankiewicz <jcubic@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.

bug#17084: Fw: bug#17084: It must be a bug

[Jakub Jankiewicz]

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

Forget about the list.

Begin forwarded message:

Date: Mon, 24 Mar 2014 17:30:58 +0100
From: Jakub Jankiewicz <jcubic@onet.pl>
To: Michael Heerdegen <michael_heerdegen@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@web.de> wrote:

> Jakub Jankiewicz <jcubic@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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

bug#17084: Close [invalid]

[Jakub Jankiewicz]

[-- Attachment #1: Type: text/plain, Size: 222 bytes --]

Ok, I found the reason, I had "emacs-24.1/lisp/emacs-lisp" in my load-path
path.

--
𝑱𝒂𝒌𝒖𝒃 𝑱𝒂𝒏𝒌𝒊𝒆𝒘𝒊𝒄𝒛 (𝑊𝑒𝑏 𝐷𝑒𝑣𝑒𝑙𝑜𝑝𝑒𝑟)
http://jcubic.pl

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]