all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 4147@emacsbugs.donarmstrong.com
Subject: bug#4147: 23.1.50: Info-search command strange behaviour
Date: Wed, 16 Dec 2009 08:53:16 +0100	[thread overview]
Message-ID: <4B2891EC.4070500@gmx.at> (raw)
In-Reply-To: <87my1johye.fsf@mail.jurta.org>

 > It seems very easy to put the contents of the header line in a separate
 > buffer.  Do you intend to display that buffer using some mechanism other
 > than the header line?  I'm afraid this won't work for tabbar.el that relies
 > on the header line.

I never looked at tabbar.el so I can't tell.  But suppose you can make
it work that whatever it displays via `header-line-format' goes to a
separate buffer - and obviously relays back any user input on that
buffer's contents to the tabbar dispatcher which is the harder part.
Then we could display that buffer in a window attached to some other
window including a frame's root window.  That way tabbar wouldn't
interfere any more with other modes using the header line like info or
ruler-mode.  Also, tabs could be displayed on the left or right of a
window.

Moreover, users could choose between a one-tabbar-per-frame and a
one-tabbar-per-window setting.  In the former case the tabbar would
vanish only when tabbars are switched off or the frame gets deleted,
just like the toolbar.  In the latter case, a tabbar would disappear
whenever the associated window gets deleted.

martin





  reply	other threads:[~2009-12-16  7:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15  3:49 bug#4147: 23.1.50: Info-search command strange behaviour Jamie Lokier
2009-08-15 10:10 ` martin rudalics
2009-12-05  0:48   ` Juri Linkov
2009-12-05 19:50     ` Juri Linkov
2009-12-08 20:12       ` Juri Linkov
2009-12-14 21:54         ` Juri Linkov
2009-12-14 23:00           ` martin rudalics
2009-12-14 23:56             ` Juri Linkov
2009-12-15  8:16               ` martin rudalics
2009-12-16  0:45                 ` Juri Linkov
2009-12-16  7:53                   ` martin rudalics [this message]
2009-12-16  9:17                     ` Juri Linkov
2009-12-16 15:04                       ` martin rudalics
2009-12-16 19:21                         ` Drew Adams
     [not found]                         ` <87my1ibip3.fsf@mail.jurta.org>
     [not found]                           ` <4B29E99D.9060501@gmx.at>
2009-12-17 23:34                             ` Juri Linkov
     [not found]                               ` <4B2B318A.7010300@gmx.at>
2009-12-19  0:30                                 ` Juri Linkov
2009-12-19  9:09                                   ` martin rudalics
2009-12-21  0:34                                     ` Juri Linkov
2009-12-21  8:21                                       ` martin rudalics
2009-12-19  0:45                               ` Juri Linkov
2009-12-19  9:09                                 ` martin rudalics
2009-12-21  0:36                                   ` Juri Linkov
2009-12-21  8:21                                     ` martin rudalics
2009-12-15  4:07           ` Eli Zaretskii
2011-10-06  3:41 ` Glenn Morris

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=4B2891EC.4070500@gmx.at \
    --to=rudalics@gmx.at \
    --cc=4147@emacsbugs.donarmstrong.com \
    --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 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.