* Eshell output goes to buffers called `nil' and `t'
@ 2005-05-18 3:25 Daniel Brockman
0 siblings, 0 replies; only message in thread
From: Daniel Brockman @ 2005-05-18 3:25 UTC (permalink / raw)
Cc: John Wiegley
Hi John and emacs-devel,
I'm trying to get Eshell working with a recent CVS snapshot, but I
don't know where to start looking for the cause of this one problem.
I'm not sure if it's reproducible, but here's what I'm experiencing:
When I type `M-x eshell RET ls RET', there's no output. Instead, two
buffers called `nil' and `t' are created. The `nil' buffer is empty,
but the `t' buffer contains the output of the `ls' command. I can do
this any number of times, and all command output will keep going to
the mysterious `t' buffer.
I can actually use Eshell by splitting the frame and having the `t'
buffer in one window and the `*eshell*' buffer in another, but it's
not very convenient. :-)
Because this bug is so crippling, I suspect that it might be a problem
specific to my system; please let me know if you have any suggestions
on how to diagnose the problem.
--
Daniel Brockman <daniel@brockman.se>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-05-18 3:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-18 3:25 Eshell output goes to buffers called `nil' and `t' Daniel Brockman
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.