From: Alan Mackenzie <acm@muc.de>
Subject: Re: Should we move 20.x related stuff out of NEWS ?
Date: Mon, 19 Apr 2004 10:26:32 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1040419095141.337A-100000@acm.acm> (raw)
In-Reply-To: <m3llktvucb.fsf@kfs-l.imdomain.dk>
On 18 Apr 2004, Kim F. Storm wrote:
>Alan Mackenzie <acm@muc.de> writes:
>> >Surely, the user can type C-c C-u after every isearch result. The
>> >problem is only in its inconvenience. C-c C-u doesn't leave mark at
>> >previous position, so it's not easy to return to previous position to
>> >continue isearch.
>> A bit like C-M-a. Admitted, that is an inconvenience. And it remains
>> irksome, even after having got into the habit of doing C-u <space> before
>> each C-c C-u. ;-(
>To me it seems sensible for C-c C-u to set a mark before jumping for
>the first time, while repeating C-c C-u immediately shouldn't set a
>mark.
>WDOT?
C-M-u (in programming modes) doesn't set the mark, and this is (for me at
any rate) correct. I don't want my mark stack flooded out with
uninteresting places, typically 20 or 10 or fewer lines apart.
On the other hand, I've often wondered whether C-M-a ought to set the
mark. I often do a C-u C-<space> first. Maybe I should try advising
C-M-[ae] to set the mark.
I don't use Outline mode much (in fact only for reading NEWS). Is C-c
C-u more like C-M-u or more like C-M-a? Maybe `beginning-of-defun'
should jump to the highest level enclosing heading in outline mode, and
maybe it should set the mark, too. It would be trivial to code, since
there's a hook already there specially for this purpose
(`beginning-of-defun-function').
>Kim F. Storm <storm@cua.dk> http://www.cua.dk
--
Alan Mackenzie (Munich, Germany)
acm@muc.de
next prev parent reply other threads:[~2004-04-19 10:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 17:40 Should we move 20.x related stuff out of NEWS ? Kim F. Storm
2004-04-15 18:55 ` Juri Linkov
2004-04-16 1:31 ` Miles Bader
2004-04-16 2:08 ` David Kastrup
2004-04-16 2:33 ` Miles Bader
2004-04-16 13:28 ` Stefan Monnier
2004-04-17 14:09 ` Juri Linkov
2004-04-18 21:47 ` Richard Stallman
2004-04-17 7:15 ` Richard Stallman
2004-04-17 8:42 ` Alan Mackenzie
2004-04-17 14:09 ` Juri Linkov
2004-04-18 14:35 ` Alan Mackenzie
2004-04-18 17:10 ` Adrian Aichner
2004-04-18 17:21 ` Adrian Aichner
2004-04-18 21:39 ` Kim F. Storm
2004-04-19 6:58 ` Kai Grossjohann
2004-04-19 10:26 ` Alan Mackenzie [this message]
2004-04-22 3:18 ` Juri Linkov
2004-04-22 23:38 ` Kim F. Storm
2004-04-25 4:55 ` Juri Linkov
2004-04-25 23:36 ` Richard Stallman
2004-04-26 4:59 ` Juri Linkov
2004-04-26 6:18 ` Miles Bader
2004-04-26 14:10 ` Richard Stallman
2004-04-22 2:54 ` isearch (was: Re: Should we move 20.x related stuff out of NEWS ?) Juri Linkov
2004-04-23 17:21 ` Richard Stallman
2004-04-23 17:44 ` Stefan Monnier
2004-04-23 18:35 ` Drew Adams
2004-04-16 18:08 ` Should we move 20.x related stuff out of NEWS ? Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.1040419095141.337A-100000@acm.acm \
--to=acm@muc.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).