From: Eli Zaretskii <eliz@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 20569@debbugs.gnu.org
Subject: bug#20569: 24.5; Vertical scroll bar is shorter than frame in info buffer
Date: Thu, 14 May 2015 18:15:00 +0300 [thread overview]
Message-ID: <83wq0bi423.fsf@gnu.org> (raw)
In-Reply-To: <87d223476s.fsf@moondust.localdomain>
> From: nljlistbox2@gmail.com (N. Jackson)
> Date: Thu, 14 May 2015 10:31:07 -0300
>
> At 05:11 -0300 on Thursday 2015-05-14, Jan D. wrote:
>
> > The top row is a header row, it does not scroll, so there is no point
> > in having the scroll bar extend into it.
>
> It is visually unappealing.
>
> More importantly, it is inconsistent with usage in other software.
>
> For example, in a GUI file management program such as Dolphin or
> Nautilus the top row of the client area of the window is also a header (
> it contains the field headings such as "Name", "Date", and
> "Permissions"), yet the scroll bar extends past this header to meet up
> with the decorations across the top of the window.
If the scroll bar extended past the header line, users would expect
that line to scroll, which it doesn't.
Anyway, this is how the header line was designed and implemented in
Emacs. We have tabulated-list-mode for the other kind. The Info
reader uses the header line for a good reason: it shows there stuff
that needs to be always visible, so it cannot be the first line of the
buffer, or behave like one.
next prev parent reply other threads:[~2015-05-14 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 0:46 bug#20569: 24.5; Vertical scroll bar is shorter than frame in info buffer N. Jackson
2015-05-14 8:11 ` Jan D.
2015-05-14 10:14 ` martin rudalics
2015-05-14 13:31 ` N. Jackson
2015-05-14 15:15 ` Eli Zaretskii [this message]
2015-05-28 19:09 ` N. Jackson
2015-05-30 9:45 ` Eli Zaretskii
2015-05-14 15:57 ` Stefan Monnier
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=83wq0bi423.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20569@debbugs.gnu.org \
--cc=nljlistbox2@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 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.