From: "Drew Adams" <drew.adams@oracle.com>
To: "'David De La Harpe Golden'" <david@harpegolden.net>
Cc: 'Alan Mackenzie' <acm@muc.de>,
"'Lennart Borgman \(gmail\)'" <lennart.borgman@gmail.com>,
'Glenn Morris' <rgm@gnu.org>,
emacs-devel@gnu.org
Subject: RE: visual marks [was: Preserving sanity in Emacs [Re: rampant region highlighting]
Date: Mon, 7 Apr 2008 10:02:47 -0700 [thread overview]
Message-ID: <000601c898d1$34daf210$c2b22382@us.oracle.com> (raw)
In-Reply-To: <47FA412F.2080505@harpegolden.net>
> The mark ring marks of course aren't necessarily in display order,
> they're in the order you set them, so without any visual
> differentiation between the different mark ring mark highlights,
> you can't really tell from the display which mark you'll end up
> at when you hit C-u C-SPC, you just know it's one of 'em - once
> I could see the marks, I found myself wanting "jump to next/prev
> mark relative to point, in display order" more than "pop mark".
OT, FWIW:
In Icicles, you can "see" the list of marks (the text of their lines) as a set
of completions in *Completions*. And you can sort them in various ways (so you
can access them in various orders). By default, they are in buffer order
(position), not mark-ring order.
next prev parent reply other threads:[~2008-04-07 17:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 19:43 rampant region highlighting Glenn Morris
2008-04-06 21:50 ` David De La Harpe Golden
2008-04-06 22:00 ` Glenn Morris
2008-04-06 22:17 ` David De La Harpe Golden
2008-04-06 22:52 ` Chong Yidong
2008-04-06 23:00 ` Preserving sanity in Emacs [Re: rampant region highlighting] Alan Mackenzie
2008-04-06 23:01 ` Chong Yidong
2008-04-07 22:28 ` Alan Mackenzie
2008-04-07 22:18 ` Glenn Morris
2008-04-06 23:50 ` David De La Harpe Golden
2008-04-06 23:58 ` Lennart Borgman (gmail)
2008-04-07 1:19 ` David De La Harpe Golden
2008-04-07 4:33 ` visual marks [was: " Drew Adams
2008-04-07 15:43 ` David De La Harpe Golden
2008-04-07 16:03 ` Lennart Borgman (gmail)
2008-04-07 17:40 ` David De La Harpe Golden
2008-04-07 17:02 ` Drew Adams [this message]
2008-04-07 0:49 ` Robert J. Chassell
2008-04-07 21:26 ` Alan Mackenzie
2008-04-07 21:37 ` Lennart Borgman (gmail)
2008-04-08 10:05 ` Alan Mackenzie
2008-04-08 10:20 ` Lennart Borgman (gmail)
2008-04-08 15:35 ` Richard Stallman
2008-04-07 23:07 ` David De La Harpe Golden
2008-04-08 10:31 ` Alan Mackenzie
2008-04-08 17:52 ` David De La Harpe Golden
2008-04-08 18:09 ` Chong Yidong
2008-04-07 23:54 ` Mathias Dahl
2008-04-06 22:09 ` rampant region highlighting Chong Yidong
2008-04-06 22:18 ` Glenn Morris
2008-04-06 22:37 ` Chong Yidong
2008-04-07 15:22 ` Stefan Monnier
2008-04-07 18:30 ` Glenn Morris
2008-04-07 19:21 ` Chong Yidong
2008-04-07 20:25 ` Glenn Morris
2008-04-07 21:01 ` Chong Yidong
2008-04-07 21:13 ` Chong Yidong
2008-04-07 21:54 ` Glenn Morris
2008-04-07 4:30 ` Chong Yidong
2008-04-07 18:29 ` Glenn Morris
2008-04-06 23:40 ` Thomas Lord
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='000601c898d1$34daf210$c2b22382@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=david@harpegolden.net \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=rgm@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 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).