all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Schroeder <alex@gnu.org>
Subject: Re: compilation-goto-locus, pop-up-windows, same-window-regexps
Date: Wed, 26 Mar 2003 01:39:33 +0100	[thread overview]
Message-ID: <87he9r7ygq.fsf@gnu.org> (raw)
In-Reply-To: <m18xaxx-000IeGC@rattlesnake.com> ("Robert J. Chassell"'s message of "Mon, 24 Mar 2003 23:02:53 +0000 (UTC)")

"Robert J. Chassell" <bob@rattlesnake.com> writes:

> It sounds to me that you are seeking what GNOME/sawfish calls a
> `group'.  As far as I know, GNU Emacs does not handle groups.  (I have
> never used groups.)

> What you want is an additional kind of undo.  A `within the current
> type of group' undo:  not an undo that pops the buffer pointer from
> the current stack, but one that pops the stack of `significant buffers
> for the current context'.

> Challenging ideas.

It depends.  I gave a rather long rationale for my wishes, and 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.

Certainly groups and other fancy window manipulation might be
interesting, but just as you said -- I never used them.  I never use
such fancy stuff because it is hard to form accurate mental models,
and it is hard to design good user interfaces for these things.

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.

Now I switched to a very limited window manager -- essentially it
looks like a big terminal emulater.  There is just one (big) frame
visible at all times.  So I started to use Emacs window managing to
lay out the things the way I want them, and I mangled the Gnus window
management configuration such that Gnus presents me with one buffer
only, and does not touch the existing window configuration (there
still is the occasional problem, but that is stuff that can be fixed
as well, and I will report that to the Gnus mailing list).

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.  Perhaps other
people have other problems, and it might be nice to solve them, too,
but they did not submit bug reports (yet), and so we can postpone that
for later.  All IMHO, of course.

Alex.

  reply	other threads:[~2003-03-26  0:39 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 [this message]
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=87he9r7ygq.fsf@gnu.org \
    --to=alex@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.