From: Eli Zaretskii <eliz@gnu.org>
To: E Sabof <esabof@gmail.com>
Cc: 14598@debbugs.gnu.org
Subject: bug#14598: 24.3; global-hl-line-mode + text-scale-adjust + next-line + scrolling
Date: Sun, 16 Jun 2013 05:45:54 +0300 [thread overview]
Message-ID: <831u82vkm5.fsf@gnu.org> (raw)
In-Reply-To: <CAEp6DyaAWGBYwNUde5bvsRak+v1chwBj0aXmwOQPyiXP317v_Q@mail.gmail.com>
> Date: Sat, 15 Jun 2013 23:48:51 +0100
> From: E Sabof <esabof@gmail.com>
> Cc: psainty@orcon.net.nz, 14598@debbugs.gnu.org
>
> > > One way to do it would be for modes to identify themselves, by setting
> > > auto-window-vscroll to t.
> >
> > Then every mode will need to do that.
> >
>
> The idea is that in practice, the functionality isn't needed most of the
> time, but backfires with text-scale-adjust. The only two modes that I use
> that mix images and text are org-mode and w3m.
There are many more, and I expect more and more to do so.
> > > A perhaps better approach might be to make auto-window-vscroll only act
> > on
> > > lines significantly larger than default height (x4?), and not on any line
> > > with a non-standard height.
> >
> > You need to consider the window height as well (or only that), not
> > just the default font size. And if we go that way, I'd argue that
> > vscroll should be used regardless of the value of auto-window-vscroll.
> >
>
> At the moment I'm a bit confused as to how auto-window-vscroll works right
> now. I might try to dig a bit deeper at some point, and put together a
> prototype of how I think it should work.
What do you mean by "how auto-window-vscroll works"? If you mean how
its value is taken into account, look at line-move-partial. If you
mean anything else, please ask.
next prev parent reply other threads:[~2013-06-16 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 12:05 bug#14598: 24.3; global-hl-line-mode + text-scale-adjust + next-line + scrolling Phil Sainty
2013-06-12 17:27 ` Eli Zaretskii
2013-06-15 11:45 ` E Sabof
2013-06-15 11:55 ` Eli Zaretskii
2013-06-15 12:10 ` E Sabof
2013-06-15 12:45 ` Eli Zaretskii
2013-06-15 22:48 ` E Sabof
2013-06-16 2:45 ` Eli Zaretskii [this message]
2013-06-16 15:16 ` E Sabof
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=831u82vkm5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14598@debbugs.gnu.org \
--cc=esabof@gmail.com \
/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).