Jason Rumney | 12 Jun 15:48 2007
Picon

Re: emacs22.1(win) - eshell problem

Robert Gloeckner wrote:
> M-x eshell does not create an interactive eshell-buffer. the screen is empty. 
> if the buffer is killed and M-x eshell is called a second time, the eshell-
> buffer is created as usual.
>   

Presumably this is reproducable every time you start emacs? If not, it
will be difficult to find the cause, but next time it happens, try to
remember what you did in the emacs session before you tried eshell.

Is this reproducible if you start emacs from the command-line as "emacs
-Q" ?

If not, please try the following.

Start emacs again as "emacs -Q"
Open your .emacs file in a buffer (C-x C-f ~/.emacs)
Evaluate it (M-x eval-buffer)
See if you can reproduce it.

If you can reproduce it this way, then repeat the above 4 steps, but
instead of eval-buffer, select part of your .emacs file and use
eval-region. Repeat this using a smaller region each time until you find
which statements are required to trigger the bug.

If you can't reproduce it with eval-buffer, then there are many more
possibilities we can try to narrow down the problem, but for now, I'll
keep it simple.
Eli Zaretskii | 12 Jun 21:44 2007
Picon

Re: emacs22.1(win) - eshell problem

> Date: Tue, 12 Jun 2007 14:48:48 +0100
> From: Jason Rumney <jasonr <at> gnu.org>
> Cc: bug-gnu-emacs <at> gnu.org
> 
> Robert Gloeckner wrote:
> > M-x eshell does not create an interactive eshell-buffer. the screen is empty. 
> > if the buffer is killed and M-x eshell is called a second time, the eshell-
> > buffer is created as usual.
> >   
> 
> Presumably this is reproducable every time you start emacs? If not, it
> will be difficult to find the cause, but next time it happens, try to
> remember what you did in the emacs session before you tried eshell.
> 
> Is this reproducible if you start emacs from the command-line as "emacs
> -Q" ?

Right, because I cannot reproduce this on my machine.
Jason Rumney | 12 Jun 21:58 2007
Picon

Re: emacs22.1(win) - eshell problem

Eli Zaretskii wrote:
> Right, because I cannot reproduce this on my machine.
>   

I received a reply directly from Robert. It seems the problem is
triggered by something in his .emacs file. He is going to narrow it down
and send more information when he has it.
Robert Gloeckner | 15 Jun 13:16 2007
Picon

Antw: Re: emacs22.1(win) - eshell problem

I figured out which line caused the problem:
		(global-set-key (kbd "C-x C-[") 'backward-page)
causes eshell not to work properly.
The message buffer says:
	("D:\\Programme\\EMACS\\emacs-22.1\\bin\\emacs.exe" "-Q")
	Loading encoded-kb...done
	For information about the GNU Project and its goals, type C-h C-p.
	Mark set
	Loading edmacro...done
	backward-page
	Loading eshell...done
	Loading esh-mode...done
	Loading em-alias...done
	Loading em-banner...done
	Loading em-basic...done
	Loading em-cmpl...done
	Loading em-dirs...done
	Loading em-glob...done
	Loading em-hist...done
	Loading em-ls...done
	Loading em-prompt...done
	Loading em-script...done
	Loading em-term...
	term-set-escape-char: Key sequence M-x starts with non-prefix key 

I commented-out the line and everything is fine ... but why?

Ciao,
Robert
(Continue reading)


Gmane