From: Fabio <phaebz@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: debug eshell init
Date: Thu, 17 Sep 2009 05:17:14 -0700 (PDT) [thread overview]
Message-ID: <5e46f691-270e-4c2f-bed8-0d30d18346ae@p23g2000vbl.googlegroups.com> (raw)
In-Reply-To: mailman.6857.1253179338.2239.help-gnu-emacs@gnu.org
On Sep 17, 11:21 am, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 17.09.2009 um 01:07 schrieb Fabio:
>
> > Is there any way to view/start a debug-log when starting any function
> > in Emacs?
>
> (setq debug-on-error t)
>
> in your init file?
>
> --
> Greetings
>
> Pete
>
> If all else fails read the instructions.
> - Donald Knuth
I was able to pin down the villain: I remapped the help key C-h...
ehelp does not like that...
I get a *Backtrace* buffer with this content:
Debugger entered--Lisp error: (wrong-type-argument characterp [31])
char-to-string([31])
byte-code(...) ... ("/usr/share/emacs/23.0.91/lisp/ehelp.elc" .
1297))
require(ehelp)
byte-code(...)
require(term)
byte-code(...)
load("em-term")
eshell-mode()
eshell(nil)
call-interactively(eshell t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
I am considering a default help-key mapping so that ehelp does not
complain.
Thank you very much Pete!
next prev parent reply other threads:[~2009-09-17 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 23:07 debug eshell init Fabio
2009-09-17 9:21 ` Peter Dyballa
[not found] ` <mailman.6857.1253179338.2239.help-gnu-emacs@gnu.org>
2009-09-17 12:17 ` Fabio [this message]
2009-09-17 17:04 ` Eli Zaretskii
2009-09-18 3:09 ` Kevin Rodgers
[not found] ` <mailman.6876.1253207067.2239.help-gnu-emacs@gnu.org>
2009-09-21 17:29 ` Fabio
2009-09-21 18:30 ` Peter Dyballa
[not found] ` <mailman.7144.1253558160.2239.help-gnu-emacs@gnu.org>
2009-09-22 9:15 ` Fabio
2009-09-22 9:16 ` Fabio
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=5e46f691-270e-4c2f-bed8-0d30d18346ae@p23g2000vbl.googlegroups.com \
--to=phaebz@googlemail.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.