all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@jurta.org>
Cc: David Reitter <david.reitter@gmail.com>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Info-use-header-line
Date: Sat, 18 Oct 2008 15:08:34 -0400	[thread overview]
Message-ID: <jwv7i85pvsy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87tzb9yhjo.fsf@jurta.org> (Juri Linkov's message of "Sat, 18 Oct 2008 19:45:47 +0300")

>> Header lines may be set by minor modes and not just the major mode being
>> implemented.  An example is tabbar.
>> Is it a good idea to hide the header line if the user chooses to not
>> display a header line in a mode?  I think not.
>> 
>> A really good solution would, by the way, show global and local header
>> lines, but I think there's only one header line allowed at this point.

> There is a special buffer-local mode tabbar-local-mode, but it requires
> explicit enabling in every Info buffer.  So I agree that a simpler
> solution is to not overwrite the global value of the header line at all
> when Info-use-header-line is nil as implemented in your patch.

There's indeed a conflict between several possible uses of header-lines.
I'm not sure what we should about it in general.  In this specific case,
leaving the header-line alone sounds like a good idea: it doesn't solve
the problem, but allows the user to work around it.


        Stefan




  reply	other threads:[~2008-10-18 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18  2:50 Info-use-header-line David Reitter
2008-10-18 16:45 ` Info-use-header-line Juri Linkov
2008-10-18 19:08   ` Stefan Monnier [this message]
2008-10-20  2:41     ` Info-use-header-line David Reitter
2008-10-18 17:32 ` Info breadcrumbs line (was: Info-use-header-line) Juri Linkov
2008-10-18 21:58   ` Info breadcrumbs line Stefan Monnier

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=jwv7i85pvsy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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.