ls in eshell will cause the prompt jumped to mid of buf

[Richard Stallman]

Can someone please DTRT, then ack?

He also said

    I encounted this issue in emacs-unicode-2 in windows xp and 22.0.91.1 in  
    ubuntu.

Date: Wed, 19 Sep 2007 09:39:02 +0800
To: address@hidden
Subject: Re: ls in eshell will cause the prompt jumped to mid of buf
From: "William Xue" <address@hidden>
Organization: SMILING
Cc: address@hidden
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
In-Reply-To: <address@hidden>

OK, please let me descript what I have done step by step.

1. emacs -q
2. M-x eshell
3. ls
4. ls
5. do 'ls' to list the files, until the prompt reachs the bottom
6. ls, then the prompt will scroll to the half of a page. I think it  
should be still stayed at the bottom.

If you do 'ls' in a path where has lots of files and can not be displayed  
in one page, the prompt will
appear in the half of the page directly, instead of the bottom of the page.

Is it a intended behavior? If yes, how to disable the feature?

I asked this (a intended behavior?), because if I do the following:
1.  emacs -q
2. C-x C-f
3. then hit 'enter', 'enter'..... in the keyboard
it will do the same behavior as in eshell (scroll to the half of a page).

But after I set following in .emacs, it can scroll line by line.

  '(scroll-conservatively 10000)
  '(scroll-down-aggressively 0.01)
  '(scroll-margin 3)
  '(scroll-preserve-screen-position t)
  '(scroll-up-aggressively 0.01)

But the above settings did not effect the 'eshell'. And I could not get  
help from *info* or the web
(http://www.gnu.org/software/emacs/manual/html_node/eshell/Smart-scrolling.html),
  
they are
empty.

At last, let me make clear my request, that is: how to scroll line by line  
in eshell?

Thanks in advance!


On Wed, 19 Sep 2007 03:34:06 +0800, Richard Stallman <address@hidden> wrote:

>     in eshell, if the files listed by ls are too many to display in  
> current
>     view of the buf, the prompt will scroll to the midle of it.
>
> Could you please send me a *precise* test case for this bug?  The test
> case should start with `emacs -q', so that your .emacs file does not
> affect it, and it should show exactly what text to put in the buffer,
> what commands to execute, and how and where to click.  Also please say
> exactly what incorrect results you get.