From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: compilation-goto-locus, pop-up-windows, same-window-regexps
Date: Mon, 17 Mar 2003 19:35:13 -0500 [thread overview]
Message-ID: <200303180035.h2I0ZDdV015515@rum.cs.yale.edu> (raw)
In-Reply-To: 87ptopy1yg.fsf@gnu.org
> > I think there's a better solution: use special-display-buffer-names.
> > You can (for example) specify
>
> At the moment I don't think that would help me. I only use one Emacs
> frame (and the doc string says "List of buffer names that should have
> their own special frames.").
The docstring should be improved, obviously.
> The doc string refers me to same-window-regexps,
This predates the (same-window . t) parameter which came together
with the (same-frame . t) parameter.
I actually happen to dislike same-window-(regexps|buffer-names) because:
- It is more difficult to remove an element from a list than to add one.
So I prefer adding ("*foo*" (same-window . nil)) over removing "*foo*"
especially since "\\*fo" or even "." might have caused "*foo*" to be
kept on the same window.
- it is declared as a defcustom but it is updated by packages,
so not only custom gets all confused but it's difficult for a user
to change the variable (especially remove entries) since she might
have to do it in an eval-after-load.
- same-window-* takes precedence over special-display-*, which makes
the above two points that much more painful.
> and that I have already set to (".") -- but as
> described in my first message of this thread, using this setting for
> same-window-regexps and pop-up-windows nil still results in some
> strange effects.
I think the strange effects are due to places that bind pop-up-windows
rather than rely on the special-display-* (or same-window-*) functionality.
Stefan
next prev parent reply other threads:[~2003-03-18 0:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 10:43 compilation-goto-locus, pop-up-windows, same-window-regexps Alex Schroeder
2003-03-17 4:52 ` Richard Stallman
2003-03-17 9:14 ` Alex Schroeder
2003-03-17 23:24 ` Richard Stallman
2003-03-17 23:41 ` Stefan Monnier
2003-03-18 0:04 ` Alex Schroeder
2003-03-18 0:35 ` Stefan Monnier [this message]
2003-03-18 0:01 ` Alex Schroeder
2003-03-19 8:49 ` Richard Stallman
2003-03-21 22:52 ` Alex Schroeder
2003-03-24 2:05 ` Richard Stallman
2003-03-24 20:35 ` Alex Schroeder
2003-03-24 23:02 ` Robert J. Chassell
2003-03-26 0:39 ` Alex Schroeder
2003-03-26 14:01 ` Robert J. Chassell
2003-03-26 22:33 ` Alex Schroeder
2003-03-27 10:05 ` Oliver Scholz
2003-03-24 2:05 ` Richard Stallman
2003-03-24 15:36 ` Stefan Monnier
2003-03-24 20:41 ` Alex Schroeder
2003-03-24 21:06 ` 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=200303180035.h2I0ZDdV015515@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@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.
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.