unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: etc/TODO:Horizontal scrollbar
Date: 05 Jul 2003 00:36:05 +0200	[thread overview]
Message-ID: <5x8yrdyl62.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200307041542.h64FgGo04392@raven.dms.auburn.edu>

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> Dhruva Krishnamurthy wrote:
>    
>    I will send an image for those interested with the
>    horizontal scroll-bar under the minibuffer. It looks like the minibuffer
>    is sandwiched between the modeline and the horizontal scroll-bar. Just
>    imagine when you type a long line in the modeline, the horizontal
>    scroll-bar's THUMB is moving/scrolling. It is quite distracting. This is
>    my opinion though.
> 
> All of this only seems to apply to the minibuffer's horizontal
> scroll-bar.  It would appear that only windows in which truncation is
> in effect should get a horizontal scroll-bar.  (I do not see what
> sense it makes for windows that use continuation lines.)

That's true .. just like a vertical scroll bar is really unnecessary
for a buffer which fits entirely in its window...

> For most
> people, it seems that horizontal scroll-bars would only be used in
> vertically split windows.  (And thus not in the minibuffer.)  For
> people who have truncate-lines set to t, it might be possible to
> design the variable horizontal-scroll-bar-mode such that it would be
> possible to exclude the minibuffer from the list of windows getting a
> horizontal scroll-bar, assuming that it looks really that annoying.

The latest "big changes" I made allow vertical scroll bars to be
configured "per-window" and "per-buffer"; of course, vertical scroll
bars should be equally flexible.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-07-04 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 12:29 etc/TODO:Horizontal scrollbar Dhruva Krishnamurthy
2003-07-02 14:12 ` Robert J. Chassell
2003-07-03 15:48   ` Richard Stallman
2003-07-04  4:33     ` Dhruva Krishnamurthy
2003-07-04 13:27       ` Robert J. Chassell
2003-07-04 15:42       ` Luc Teirlinck
2003-07-04 22:36         ` Kim F. Storm [this message]
2003-07-05 22:26         ` Richard Stallman
2003-07-05 23:05           ` Luc Teirlinck
2003-07-05 22:25       ` Richard Stallman
2003-07-03  0:55 ` Luc Teirlinck
2003-07-03 11:51   ` Frank Schmitt
2003-07-03 14:45     ` Luc Teirlinck
2003-07-04 22:43       ` Kim F. Storm
2003-07-04 21:32         ` Luc Teirlinck
2003-07-06 18:53         ` Richard Stallman
2003-07-07  0:08           ` Kim F. Storm
2003-07-07  2:01             ` Luc Teirlinck
2003-07-07 11:45               ` Dhruva Krishnamurthy
2003-07-08 20:01                 ` Richard Stallman
2003-07-07  3:03             ` Luc Teirlinck
2003-07-03 15:48 ` Richard Stallman

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=5x8yrdyl62.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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).