From: Richard Stallman <rms@gnu.org>
Subject: [Lute.Kamstra@cwi.nl: Not a real bug: vertical scrolling with variable height fonts.]
Date: Sun, 23 Jun 2002 12:13:03 -0600 (MDT) [thread overview]
Message-ID: <200206231813.g5NID3224495@aztec.santafe.edu> (raw)
I think I agree with him. Would someone like to work on this?
------- Start of forwarded message -------
X-Authentication-Warning: occarina.pna.cwi.nl: lute set sender to Lute.Kamstra@cwi.nl using -f
To: bug-gnu-emacs@gnu.org
Subject: Not a real bug: vertical scrolling with variable height fonts.
From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Organization: CWI
Sender: bug-gnu-emacs-admin@gnu.org
Date: 22 Jun 2002 09:57:18 +0200
Dear People,
This is more of a feature request than a bug report. It concerns
vertical scrolling using GNU Emacs 21 new redisplay engine.
In GNU Emacs 20, all the lines in a frame were of equal height and a
frame's size was measured in terms lines. As a result, a line was
either visible or it was not. If you moved the point past the last
visible line, the frame would be redisplayed and you could find your
cursor somewhere in the middle of the window.
In GNU Emacs 21, lines can have different heights. It can therefore
happen that only the upper part of the last line is visible. If you
move the point into such a last line, the frame is redisplayed, but
only to show the last line in its entirely. This behavior is
confusing for me. When the frame is redisplayed, I automatically look
for the point in the middle of the window and in this case the point
is still on the last line. Moving the point further down causes
another redisplay that does leave the point in the middle of the
window.
I would prefer the following behavior. If the point moves into a last
line that is partly visible, let the triggered redisplay position that
line in the middle of the window (instead of on the bottom of the
window). I find this behavior more consistent.
Could you implement my proposal an introduce a option that lets the
user choose between the current behavior and my preferred behavior?
Regards,
Lute Kamstra.
- --
Lute Kamstra
CWI department PNA4
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------
reply other threads:[~2002-06-23 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200206231813.g5NID3224495@aztec.santafe.edu \
--to=rms@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).