From: Jakub Jankiewicz <jcubic@onet.pl>
To: 17084@debbugs.gnu.org
Subject: bug#17084: Fw: bug#17084: It must be a bug
Date: Mon, 24 Mar 2014 17:42:14 +0100 [thread overview]
Message-ID: <20140324174214.7a75f37e@jcubic> (raw)
In-Reply-To: <20140324142748.1c58647a@jcubic>
[-- 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 --]
next prev parent reply other threads:[~2014-03-24 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 13:27 bug#17084: undefined variable access trigger "variable is void: unread-command-char" Jakub Jankiewicz
2014-03-24 14:42 ` bug#17084: It must be a bug Jakub Jankiewicz
2014-03-24 15:53 ` Michael Heerdegen
2014-03-24 16:42 ` Jakub Jankiewicz [this message]
2014-03-25 9:48 ` bug#17084: Close [invalid] Jakub Jankiewicz
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140324174214.7a75f37e@jcubic \
--to=jcubic@onet.pl \
--cc=17084@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).