all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org, dmoncayo@gmail.com
Subject: Re: Should ending successful Isearch with C-g restore the relativewindow position?
Date: Tue, 15 Jan 2013 16:36:42 +0000	[thread overview]
Message-ID: <20130115163642.GC3430@acm.acm> (raw)
In-Reply-To: <B9A1EBB2DF28482EB9AD7E8C477F358C@us.oracle.com>

Hello again, Drew.

On Tue, Jan 15, 2013 at 08:22:08AM -0800, Drew Adams wrote:
> > > > Recentering is the default, always was.

> > > Just the _default_?  Does that mean that there is a simple user
> > > setting that changes the behavior from the default so that it
> > > returns things as they were before searching?

> > No, I don't think it does.  You might be being a bit too pedantic
> > here.

> Dunno why you think that, but OK.  So what was meant then by "the
> default"?  What's the alternative behavior, and how does a user get it?

I think Eli meant nothing more than "what Emacs in general usually does,
when no other special action is taken", but he can confirm that himself
if he wants.  The alternative is carefully to scroll the contents of the
window to the desired position, something which is out of reach of normal
users.

> > I think it would be easy enough to record the window position in
> > isearch for this.

> Is that the alternative for users to "the default" behavior - recoding
> Isearch?  Not a rhetorical question.  If I'm missing something I'd like
> to know what the suggestion is.

Recoding isearch is certainly an alternative, but it's not for the faint
of heart.

> > But... If C-g restores the window position, then sooner or later
> > somebody's going to want C-<space> to do the same.  Seems perfectly
> > reasonable.

> Why?  The doc makes clear that the intention of `C-g' (for successful
> search) is to take you back where you were.  Including window position
> as part of where you were would be a natural and reasonable extension
> for the `C-g' behavior.

> I would not object if that were optional for users, if there is someone
> who really thinks we should also keep the current behavior.

> But what does any of this have to do with `C-SPC'?  Sorry, you've lost
> me.  The question is about `C-g' in the case of search success.

I suppose it's the way I use isearch.  I frequently use C-g to go back to
my starting position, but I also use C-<space> to do this (completing the
search in the process).  So, to me, C-g and C-<space> are semantically
very close.  Were I a mere user, I'd get somewhat irritated if C-g
restored the original scroll-position, but C-<space> didn't.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2013-01-15 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 22:29 Should ending successful Isearch with C-g restore the relative window position? Drew Adams
2013-01-14 23:07 ` Dani Moncayo
2013-01-14 23:17   ` Drew Adams
2013-01-15  3:49     ` Eli Zaretskii
2013-01-15 14:58       ` Drew Adams
2013-01-15 15:09         ` Alan Mackenzie
2013-01-15 16:22           ` Should ending successful Isearch with C-g restore the relativewindow position? Drew Adams
2013-01-15 16:36             ` Alan Mackenzie [this message]
2013-01-15 16:54               ` Should ending successful Isearch with C-g restore therelativewindow position? Drew Adams
2013-01-15 16:34         ` Should ending successful Isearch with C-g restore the relative window position? Eli Zaretskii
2013-01-15 16:58           ` Drew Adams
2013-01-15 17:10             ` Eli Zaretskii
2013-01-15 17:59               ` Drew Adams
2013-01-15 18:25                 ` Eli Zaretskii
2013-01-15 22:04               ` Drew Adams
2013-01-16 16:55                 ` Should ending successful Isearch with C-g restore therelative " Drew Adams
2013-01-16 21:29                   ` Should ending successful Isearch with C-g restore the relative " Juri Linkov
2013-01-16 22:16                     ` Drew Adams
2013-01-17 21:35                       ` Juri Linkov
2013-01-15  9:52   ` Juri Linkov

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=20130115163642.GC3430@acm.acm \
    --to=acm@muc.de \
    --cc=dmoncayo@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --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.