From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21139-done@debbugs.gnu.org
Subject: bug#21139: 25.0.50; shell-mode doesn't respect comint-scroll-to-bottom-on-output/input
Date: Sat, 8 Aug 2015 19:01:54 +0100 [thread overview]
Message-ID: <CAAdUY-L7jP=5bWsgZ=E2XyoOHdgSzAAz-F7-LBarTyjPJJnR_w@mail.gmail.com> (raw)
In-Reply-To: <83a8u2qhid.fsf@gnu.org>
THanks Eli. Indeed, that's what I was looking for.
I'll close this now.
2015-08-08 10:03 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
>> Date: Mon, 27 Jul 2015 11:46:56 +0100
>> From: Artur Malabarba <bruce.connor.am@gmail.com>
>>
>> 1. Set `comint-scroll-to-bottom-on-output` and
>> `comint-scroll-to-bottom-on-input` to nil via the customize interface
>> (or via `setq-default`)
>> 2. Run `M-x shell`
>> 3. Run a couple of shell commands so you have enough output to fill
>> the screen (`ls -al ~/` should do it).
>> 4. Hit `C-l` twice so point is at the top of the screen.
>> 5. Type `date` on the prompt and hit `RET`.
>> 6. The window scrolls until point is at the bottom.
>>
>>
>> It would seem that, by setting those variables to nil, the window
>> should not scroll. If this is not intended to be the case, then these
>> variables' docstrings are unclear to me.
>
> The variable comint-scroll-to-bottom-on-output
> (a.k.a. comint-move-point-for-output) control whether _point_ moves.
> In the scenario you described, point does not move, it stays at EOB.
> What happens is that the window is scrolled to place point on the last
> line of the window; this is controlled by another variable,
> comint-scroll-show-maximum-output, which attempts to show as much of
> the shell buffer as possible. if you set it to nil, you will have
> what you want in this scenario.
>
> IOW, this doesn't look like a bug, but intended behavior, and you need
> to customize another variable to have what you want.
next prev parent reply other threads:[~2015-08-08 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 10:46 bug#21139: 25.0.50; shell-mode doesn't respect comint-scroll-to-bottom-on-output/input Artur Malabarba
2015-07-27 15:44 ` Glenn Morris
2015-07-27 17:01 ` Artur Malabarba
2015-07-28 19:55 ` Glenn Morris
2015-08-08 9:03 ` Eli Zaretskii
2015-08-08 18:01 ` Artur Malabarba [this message]
2015-08-09 2:26 ` Glenn Morris
2015-08-09 9:05 ` Artur Malabarba
2015-08-09 14:49 ` Eli Zaretskii
2015-08-10 9:26 ` Artur Malabarba
2015-08-11 18:51 ` Eli Zaretskii
2015-08-12 5:57 ` Glenn Morris
2015-08-12 12:42 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAdUY-L7jP=5bWsgZ=E2XyoOHdgSzAAz-F7-LBarTyjPJJnR_w@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=21139-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).