From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Juri Linkov <juri@jurta.org>
Cc: grischka <grishka@gmx.de>, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Side windows
Date: Wed, 14 Apr 2010 07:15:35 +0200 [thread overview]
Message-ID: <4BC54F77.4080409@swipnet.se> (raw)
In-Reply-To: <87ljcruevx.fsf_-_@mail.jurta.org>
Juri Linkov skrev 2010-04-14 01.31:
>> To give another example: A scrollbar is defined mostly by its action
>> to "scroll content in the associated window". Of course you could use
>> the scrollbar widget just as well to adjust your speaker volume, but
>> then it wouldn't be a scrollbar, even if it looked like one.
>
> There is a task in etc/TODO:
>
> ** Compilation error navigation bar, parallel to the scroll bar,
> indicating where in the buffer there are compilation errors.
> Perhaps we could arrange to display these error indications on top
> of the scroll bar itself. That depends on to what extent toolkit
> scroll bars are extensible.
>
> If it's possible to display such tab-like indications
> on the scroll bar, is it still called a scroll bar?
>
> If it's not possible, then what is an alternative?
> Maybe, 1-column side bar windows?
>
As Eli already said, the fringe. Scrollbars aren't the place for this.
How do you know when to remove these indications?
Jan D.
next prev parent reply other threads:[~2010-04-14 5:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 19:53 Gtk tabs in emacs, new branch grischka
2010-04-13 23:31 ` Side windows (was: Gtk tabs in emacs, new branch.) Juri Linkov
2010-04-14 3:18 ` Eli Zaretskii
2010-04-14 15:24 ` Side windows Jason Rumney
2010-04-14 16:52 ` Juri Linkov
2010-04-14 18:19 ` Eli Zaretskii
2010-04-14 23:54 ` Juri Linkov
2010-04-15 3:18 ` Eli Zaretskii
2010-04-15 23:46 ` Juri Linkov
2010-04-16 6:33 ` Eli Zaretskii
2010-04-14 5:15 ` Jan Djärv [this message]
2010-04-16 14:03 ` grischka
2010-04-16 20:48 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2016-09-22 9:07 Side Windows martin rudalics
2016-09-22 20:54 ` Juri Linkov
2016-09-24 19:05 ` martin rudalics
2016-09-23 8:38 ` Eli Zaretskii
2016-09-23 9:14 ` Eli Zaretskii
2016-09-24 19:06 ` martin rudalics
2016-09-24 19:27 ` Eli Zaretskii
2016-10-05 8:39 ` martin rudalics
2016-10-05 10:35 ` Eli Zaretskii
2016-10-05 13:13 ` Eli Zaretskii
2016-10-05 14:20 ` martin rudalics
2016-10-05 10:25 Angelo Graziosi
2016-10-05 10:26 Angelo Graziosi
2016-10-05 10:51 ` Eli Zaretskii
2016-10-05 11:01 ` Angelo Graziosi
2016-10-05 11:24 ` Kaushal Modi
2016-10-05 13:03 ` Eli Zaretskii
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=4BC54F77.4080409@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=grishka@gmx.de \
--cc=juri@jurta.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).