unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Nikolaus Rath <Nikolaus@rath.org>, help-gnu-emacs@gnu.org
Subject: RE: Frame for opening rgrep links?
Date: Sun, 9 Nov 2014 15:55:20 -0800 (PST)	[thread overview]
Message-ID: <81878128-c21a-4752-be57-91ac70b290a2@default> (raw)
In-Reply-To: <545FF909.1010808@rath.org>

> > Sounds like the window for buffer *grep* is a dedicated window.
> >
> > Check your values of options `special-display-buffer-names' and
> > `special-display-regexps'.
> 
> special-display-buffer-names is a variable defined in `window.el'.
> Its value is nil
> 
> special-display-regexps is a variable defined in `window.el'.
> Its value is nil
> 
> > Or if you use only option `display-buffer-alist' then check its
> > value - see the doc for an explanation of this complicated option.
> > See also the doc of `display-buffer', which you'll need to
> understand
> > the doc of `display-buffer-alist' .  Look for an entry that
> > corresponds by name or regexp etc. to `*grep*' or `*compile*'.
> 
> I don't seem to have a "display-buffer-alist" option (Emacs 23.4.1).
> 
> Anything I could look at?

I should have said to first check whether the window for `*grep*'
is in fact dedicated.  With your cursor in that window, do this:
`M-: (window-dedicated-p (selected-window))'.  If it says `t'
then the window is dedicated; if is says `nil' then it is not.

Perhaps someone else has another suggestion, if it is not
dedicated.  If it is, then you will need to look further to find
out why.

Normally, in Emacs 23, one of those two `special-display-*' options
is used to automatically make a buffer be displayed in a dedicated
window.  But code can also call `set-window-dedicated-p' explicitly
to make it so.

You can also use `M-: (special-display-p (buffer-name))', to
see whether the buffer is special-display (which implies that it
is displayed in a dedicated window).  If the displayed value is
anything other than `nil' then it is.

Again, perhaps someone else has another suggestion.



  reply	other threads:[~2014-11-09 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-09 21:15 Frame for opening rgrep links? Nikolaus Rath
2014-11-09 22:44 ` Drew Adams
2014-11-09 23:30   ` Nikolaus Rath
2014-11-09 23:55     ` Drew Adams [this message]
2014-11-10  0:11       ` Nikolaus Rath
2014-11-16 19:26 ` Nikolaus Rath

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=81878128-c21a-4752-be57-91ac70b290a2@default \
    --to=drew.adams@oracle.com \
    --cc=Nikolaus@rath.org \
    --cc=help-gnu-emacs@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.
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).