From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: compilation-goto-locus, pop-up-windows, same-window-regexps
Date: Wed, 26 Mar 2003 14:01:24 +0000 (UTC) [thread overview]
Message-ID: <m18yBT2-000IeGC@rattlesnake.com> (raw)
In-Reply-To: <87he9r7ygq.fsf@gnu.org> (message from Alex Schroeder on Wed, 26 Mar 2003 01:39:33 +0100)
... I gave a rather short solution: Let pop-up-windows do what it
is supposed to do -- prevent window splitting -- and we'll see how
it goes and perhaps other things need fixing thereafter.
I am not quite sure I understand your suggestion. The
`pop-up-windows' variable does not seem to be frame-oriented at all.
Back when I used an ordinary window manager, I used frames to "group"
stuff. I had a Gnus frame, an IRC frame, a programming frame, etc.
Ah ... like running multiple instances of Emacs, each devoted to a
topic. (As it happens, I am running four different instances right
now.)
Are you suggesting that I should be able to run one instance of Emacs,
but have a frame for my mail related buffers, a frame for my Emacs
Lisp related buffers, a frame for my CVS and compilation related
buffers, and so on?
This would require implementing a new function that might be called
`keep-same-frame'. My current CVS/compilation `group' consists of
three buffers: `how-to-emacs', `*cvs*', and `*compilation*'.
So, should I be able to run
(keep-same-frame "how-to-emacs" "*cvs*")
and create a grouping of those two buffers, and then later run
(keep-same-frame-addition "*compilation*")
to add to that grouping?
What I'm trying to say is that we should not let ourselves get
distracted by possible neat solutions to my problem, when a very
simple and limited solution might solve my problem. ...
Good point. But I don't see any simple solution, other than running
different instances of Emacs. But I am often blind to what Emacs can
already do. Does anyone know of a simple and limited solution to the
current problem?
--
Robert J. Chassell Rattlesnake Enterprises
http://www.rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.teak.cc bob@rattlesnake.com
next prev parent reply other threads:[~2003-03-26 14:01 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
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 [this message]
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=m18yBT2-000IeGC@rattlesnake.com \
--to=bob@rattlesnake.com \
--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.