debug eshell init

debug eshell init

[Fabio]

Hello,

A new buffer named *eshell* pops up but shows no content. Minibuffer
shows an error named 'wrong type argument: characterp [31]' when
starting eshell by M-x eshell. It works though when I start Emacs with
the -q option. I already commented out all (e)shell-specific .emacs
stuff, but still no luck

Is there any way to view/start a debug-log when starting any function
in Emacs? The tedious alternative would be to search my .emacs by
trial-and-error...

I use the ubuntu snapshot package of GNU Emacs 23.0.91.1.

cheers,
Fabio

Re: debug eshell init

[Peter Dyballa]

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

Re: debug eshell init

[Fabio]

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!

Re: debug eshell init

[Eli Zaretskii]

> From: Fabio <phaebz@googlemail.com>
> Date: Thu, 17 Sep 2009 05:17:14 -0700 (PDT)
> 
> 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)

Sounds like a bug that should be reported.  Please use "M-x
report-emacs-bug RET" to do that.

Re: debug eshell init

[Kevin Rodgers]

Fabio wrote:
> 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.

help-char should be a character, not a vector.

-- 
Kevin Rodgers
Denver, Colorado, USA

Re: debug eshell init

[Fabio]

> Sounds like a bug that should be reported.  Please use "M-x
> report-emacs-bug RET" to do that.

I am not really familliar with bug reporting. What would be the best
way to tell a developer about it? Anyway, I think I really got down to
the problem and I guess it was my fault after all.

The help key was mapped to underscore C-_ :
(global-set-key [?\C-_] 'help-command)

[?\C-_] evaluates to [31]. That is the cause.

That way, it works in terms of mapping, but ehelp is not able to
handle this vector. I used this vector syntax for *special* keys like
Function keys, e.g. [f6] or the windows-key, e.g. [?\s-f] etc. Is
there is a better way to do that?

Re: debug eshell init

[Peter Dyballa]

Am 21.09.2009 um 19:29 schrieb Fabio:

> That way, it works in terms of mapping, but ehelp is not able to
> handle this vector. I used this vector syntax for *special* keys like
> Function keys, e.g. [f6] or the windows-key, e.g. [?\s-f] etc. Is
> there is a better way to do that?


This should also work:

	(global-set-key (kbd "C-_")	'help-command)
	(global-set-key	(kbd "A-<")	'other-frame)
	(global-set-key (kbd "ESC <M-left>") 'tabbar-backward-group)

--
Greetings

   Pete

                (This space left blank for technical reasons.)

Re: debug eshell init

[Fabio]

> This should also work:
>
>         (global-set-key (kbd "C-_")   'help-command)

Thanks again!

Re: debug eshell init

[Fabio]

> This should also work:
>
>         (global-set-key (kbd "C-_")   'help-command)

Thanks again!