unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: Lock buffer to window
Date: Fri, 08 Sep 2006 09:56:35 +0200	[thread overview]
Message-ID: <u1wqmg5ak.fsf@gmail.com> (raw)
In-Reply-To: mailman.6613.1157699819.9609.help-gnu-emacs@gnu.org

henning <henning.red@googlemail.com> writes:

> When using dired or rdired (from ESS) I sometimes want to keep a
> buffer in a certain window. However, commands such as e.g. 'man'
> might change the buffer in that window. Is there a way to dedicate a
> window to a particular buffer so that that window becomes invisible
> to commands that request a window for showing output? calculator is
> another such example where I obviously dont want the man page to
> show up in the tiny window created by the calculator command.

This doesn't solve the problem in the exact way you want, but you
might want to try it out anyway:

Try this:

(setq special-display-buffer-names
      (append special-display-buffer-names (list "*Help*")))

Then use any of the help commands, `C-h f' for example. Notice how the
*Help* buffer opens in a new frame instead of splitting the current
window.

If you want to do more advanced matching of buffer names, try
`special-display-regexps' instead.

       reply	other threads:[~2006-09-08  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6613.1157699819.9609.help-gnu-emacs@gnu.org>
2006-09-08  7:56 ` Mathias Dahl [this message]
2006-09-08  8:00   ` Lock buffer to window Mathias Dahl
2006-09-11  7:23   ` henning
2007-05-23 19:14 Nikolaj Fogh
     [not found] ` <mailman.1165.1180017190.32220.help-gnu-emacs@gnu.org>
2007-05-24 14:05   ` Nikolaj Fogh
2007-05-24 14:32 ` Nikolaj Schumacher
2007-05-24 21:45   ` Xavier Maillard
2007-05-24 21:45 ` Xavier Maillard
  -- strict thread matches above, loose matches on Subject: below --
2006-09-11 12:28 martin rudalics
2006-09-08  7:16 henning

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=u1wqmg5ak.fsf@gmail.com \
    --to=brakjoller@gmail.com \
    /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.
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).