From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 19170@debbugs.gnu.org
Subject: bug#19170: 25.0.50; enhancement request: `compare-windows' use across frames
Date: Wed, 26 Nov 2014 19:18:39 -0800 (PST) [thread overview]
Message-ID: <3dcedc6e-0613-4af5-a061-02395bc9a506@default> (raw)
In-Reply-To: <877fyhfno0.fsf@mail.linkov.net>
> > Some things that I think are missing, or that might be helpful:
> >
> > 1. Maybe echo some indication of which two windows are compared
> > (?).
>
> Currently `compare-windows' displays in the echo area "Mark set"
> which is mostly useless. We could overwrite it with more specific
> messages, e.g.
>
> Next difference between window1 and window2
> Next match between window1 and window2
> No more matching points between window1 and window2
Please do.
And maybe print the point values too, unless they're the same buffer?
Different, A: 2349, B: 1358
Same: A: 2349, B: 1358
No match
Dunno what the names might be. They could be the buffer names
(possibly truncated, if long), if different.
> > I'm thinking that having that last-selected window recorded
> > always might be a good thing, useful for more than just
> > `compare-windows'. (And perhaps (?) the NORECORD arg of
> > `select-window' should control updating of `last-window-selected'
> > also. Dunno.)
> >
> > What do you think? Does this make sense?
>
> We already have a lot of `last-...' variables, so a new variable
> for the last selected window makes sense. Then it would be
> convenient to compare `(selected-window)' with `last-selected-
> window'.
Please do. I'm sure that whatever you come up with will be good.
IMO, this will make the command much more useful. I've been
using it for decades, but never gave much thought to trying
to improve it. It is a very useful command.
next prev parent reply other threads:[~2014-11-27 3:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 19:24 bug#19170: 25.0.50; enhancement request: `compare-windows' use across frames Drew Adams
2014-11-24 22:19 ` Juri Linkov
2014-11-24 22:34 ` Drew Adams
2014-11-25 0:13 ` Drew Adams
2014-11-25 0:37 ` Juri Linkov
2014-11-25 4:09 ` Drew Adams
2014-11-25 21:39 ` Juri Linkov
2014-11-25 22:00 ` Drew Adams
2014-11-25 22:56 ` Juri Linkov
2014-11-25 23:40 ` Drew Adams
2014-11-27 0:57 ` Juri Linkov
2014-11-27 3:18 ` Drew Adams [this message]
2014-11-28 0:54 ` Juri Linkov
2014-11-28 7:29 ` martin rudalics
2014-11-28 15:31 ` Drew Adams
2014-11-28 21:15 ` Juri Linkov
2014-11-28 22:20 ` Drew Adams
2014-11-29 0:50 ` Juri Linkov
2014-11-29 1:53 ` Drew Adams
2014-12-05 0:51 ` Juri Linkov
2014-11-28 15:25 ` Drew Adams
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=3dcedc6e-0613-4af5-a061-02395bc9a506@default \
--to=drew.adams@oracle.com \
--cc=19170@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).