From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ashton Wiersdorf <ashton@wiersdorfmail.net>
Cc: luangruo@yahoo.com, jporterbugs@gmail.com,
Eli Zaretskii <eliz@gnu.org>,
74430@debbugs.gnu.org
Subject: bug#74430: 30.0.92; pixel-scroll-precision-mode hiding Eshell prompt after some commands
Date: Fri, 3 Jan 2025 09:55:50 +0100 [thread overview]
Message-ID: <6a70f32f-c1d0-4bb7-b5ee-970ee51930d7@gmx.at> (raw)
In-Reply-To: <m2y0zsu5au.fsf@wiersdorfmail.net>
> I'm curious: does anyone know what the rationale is for
> `pixel-scroll-precision-mode` setting this to `nil`? It doesn't seem
> like something that you'd want… Did this behavior change in Emacs 30?
Apparently. AFAICT the rationale was to fix Bug#65214. I think the two
ways to handle that bug and the present one are:
- Add two new values for 'make-cursor-line-fully-visible', say 'always'
and 'never', a mode would not be permitted to override.
- Add a second customizable variable say
'pixel-scroll-precision-mode-make-cursor-line-fully-visible'
that would control the behavior.
More experienced users could also try to set the buffer local value of
'make-cursor-line-fully-visible' in 'after-change-major-mode-hook'.
martin
next prev parent reply other threads:[~2025-01-03 8:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:52 bug#74430: 30.0.92; pixel-scroll-precision-mode hiding Eshell prompt after some commands Ashton Wiersdorf
2024-11-21 10:53 ` Eli Zaretskii
2024-11-21 18:37 ` Jim Porter
2024-11-21 23:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-22 6:58 ` Eli Zaretskii
2024-11-30 10:07 ` Eli Zaretskii
2024-12-14 9:38 ` Eli Zaretskii
2024-12-28 11:13 ` Eli Zaretskii
2024-12-31 23:51 ` Ashton Wiersdorf
2025-01-01 3:10 ` Jim Porter
2025-01-01 9:02 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-01 10:31 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 0:09 ` Ashton Wiersdorf
2025-01-03 8:26 ` Eli Zaretskii
2025-01-03 8:55 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-18 9:17 ` Eli Zaretskii
2025-01-18 9:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-18 10:49 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-18 12:05 ` Eli Zaretskii
2024-11-25 5:13 ` Jim Porter
2024-11-30 10:07 ` Eli Zaretskii
2024-12-14 9:38 ` Eli Zaretskii
2024-12-14 18:40 ` Ashton Wiersdorf
2024-12-15 19:10 ` Jim Porter
2024-12-27 20:09 ` Ashton Wiersdorf
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a70f32f-c1d0-4bb7-b5ee-970ee51930d7@gmx.at \
--to=bug-gnu-emacs@gnu.org \
--cc=74430@debbugs.gnu.org \
--cc=ashton@wiersdorfmail.net \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=luangruo@yahoo.com \
--cc=rudalics@gmx.at \
/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 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.