unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: grischka <grishka@gmx.de>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Side windows (was: Gtk tabs in emacs, new branch.)
Date: Wed, 14 Apr 2010 02:31:30 +0300	[thread overview]
Message-ID: <87ljcruevx.fsf_-_@mail.jurta.org> (raw)
In-Reply-To: <4BC4CBB5.3050809@gmx.de> (grischka's message of "Tue, 13 Apr 2010 21:53:25 +0200")

> 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?

-- 
Juri Linkov
http://www.jurta.org/emacs/




  reply	other threads:[~2010-04-13 23:31 UTC|newest]

Thread overview: 13+ 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 ` Juri Linkov [this message]
2010-04-14  3:18   ` Side windows (was: Gtk tabs in emacs, new branch.) 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
2010-04-16 14:03   ` grischka
2010-04-16 20:48     ` Juri Linkov

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=87ljcruevx.fsf_-_@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=grishka@gmx.de \
    /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).