unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: henning <henning.red@googlemail.com>
Subject: Re: Lock buffer to window
Date: Mon, 11 Sep 2006 00:23:30 -0700 (PDT)	[thread overview]
Message-ID: <6242158.post@talk.nabble.com> (raw)
In-Reply-To: <u1wqmg5ak.fsf@gmail.com>


Thanks, but you are right, its not really what I want to do, I would like to
force a window to show current buffer and not switch buffer until I
explicitly say so. I have been trying to implement this but it was harder
than I had imagined. Maybe I can get by with what you suggested though.

Cheers,

H


Mathias Dahl-4 wrote:
> 
> henning <henning.red@googlemail.com> writes:
> 
> 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.
> 
> 

-- 
View this message in context: http://www.nabble.com/Lock-buffer-to-window-tf2237460.html#a6242158
Sent from the Emacs - Help forum at Nabble.com.

  parent reply	other threads:[~2006-09-11  7:23 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 ` Lock buffer to window Mathias Dahl
2006-09-08  8:00   ` Mathias Dahl
2006-09-11  7:23   ` henning [this message]
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=6242158.post@talk.nabble.com \
    --to=henning.red@googlemail.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).