From: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
To: emacs-devel@gnu.org
Subject: Re: annoyances [Was: shrink-window-if-larger-than-buffer in VC-diff]
Date: Mon, 16 Aug 2010 09:54:32 +0100 [thread overview]
Message-ID: <i4aucq$tfp$1@dough.gmane.org> (raw)
In-Reply-To: <87vd7bbaa6.fsf@uwakimon.sk.tsukuba.ac.jp>
On 8/16/2010 2:45 AM, Stephen J. Turnbull wrote:
> I understand, but don't necessarily sympathize. For example, with
> find-file, it's pretty clear that automatically switching windows is a
> good thing.
As you can tell, it is not "clear" to me that it is a good thing. When the
user is displaying two windows, Emacs doesn't really know which window the user
wants to be in. The best thing to do would be to make no assumption. The
documentation of dired-find-file-other-window doesn't say that it is going to
switch windows. You might say that that is included in the semantics of
"find-file". But, then, would the semantics of "next-error" include putting
focus on the error message?
These switching actions are an example of over-enthusiasm on the part of Emacs,
just as s-w-i-l-t-b is. Whoever wrote these functions was thinking of one
particular workflow and forgetting that less can often be more.
Maybe in the case of C-x ` (is that `next-error' in your
> context, as it is for me?) it should be optional. I admit I'm an
> infrequent user of next-error, but I think it's quite natural to
> switch windows since it's documented as visiting the error buffer and
> the corresponding source file. This is almost always what I want. If
> you don't like that behavior, you need to write your own function that
> implements the workflow you want. As usual.[1]
I suppose you are right. I am a bit spoilt by VM, which seems to know how to
do just the right thing in terms of the user interface. One of the ideas I
have is to write a generic "browser" mode, using VM ideas, which can be
inherited by all modes like dired, diff, buffer-menu, VM, Gnus etc. and provide
a uniform user interface to all of them. This should also address some of the
key binding issues we were talking about in the other thread. I don't yet know
when I will get time to do it.
Cheers,
Uday
next prev parent reply other threads:[~2010-08-16 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 23:15 shrink-window-if-larger-than-buffer in VC-diff Chong Yidong
2010-08-15 1:14 ` Miles Bader
2010-08-15 7:07 ` Andreas Schwab
2010-08-15 9:38 ` annoyances [Was: shrink-window-if-larger-than-buffer in VC-diff] Uday S Reddy
2010-08-15 10:06 ` annoyances David Kastrup
2010-08-15 10:33 ` annoyances Uday S Reddy
2010-08-15 14:12 ` annoyances [Was: shrink-window-if-larger-than-buffer in VC-diff] Stephen J. Turnbull
2010-08-15 18:35 ` Uday S Reddy
2010-08-16 1:45 ` Stephen J. Turnbull
2010-08-16 8:54 ` Uday S Reddy [this message]
2010-08-15 22:44 ` shrink-window-if-larger-than-buffer in VC-diff Juanma Barranquero
2010-08-16 3:10 ` Chong Yidong
2010-08-16 23:06 ` Juanma Barranquero
2010-08-18 21:53 ` Chong Yidong
2010-08-20 9:06 ` martin rudalics
2012-10-27 13:45 ` martin rudalics
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='i4aucq$tfp$1@dough.gmane.org' \
--to=u.s.reddy@cs.bham.ac.uk \
--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.