Re: emacs22.1(win) - eshell problem

[Jason Rumney]

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.