unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	grishka@gmx.de, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Side windows
Date: Wed, 14 Apr 2010 19:52:01 +0300	[thread overview]
Message-ID: <87hbne9f86.fsf@mail.jurta.org> (raw)
In-Reply-To: <87y6gq5a66.fsf@home.jasonrumney.net> (Jason Rumney's message of "Wed, 14 Apr 2010 23:24:49 +0800")

>>>   ** 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?
>>
>> The fringe, I think.
>
> The fringe nearest the scroll-bar is the right place to display the
> indicators I think, but we need a new mechanism to display them, as they
> should not scroll with the buffer text.

Does this mean an additional fringe is necessary that doesn't scroll?

Then we have the same question as with multiple header lines:
whether to allow multiple fringes and header lines or implement them
as true windows placed on the left or on the top of the base window.

Using windows will allow implementing emulations of the scroll bar
like minimap.el, etc.  I'm not sure whether this is possible to do
with additional fringes?

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




  reply	other threads:[~2010-04-14 16:52 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 [this message]
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
  -- 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=87hbne9f86.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=grishka@gmx.de \
    --cc=jasonr@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).