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: Fri, 28 Nov 2014 07:25:36 -0800 (PST) [thread overview]
Message-ID: <5df4c77f-ec7f-4084-88bc-737288ae815e@default> (raw)
In-Reply-To: <87y4qw5elz.fsf@mail.linkov.net>
> > 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
>
> Or the size of the region of difference or sameness.
Maybe. Or both:
Diff: 623 chars, A: 2349, B: 1358
Same: 623 chars, A: 2349, B: 1358
No match
> > Dunno what the names might be. They could be the buffer names
> > (possibly truncated, if long), if different.
>
> There is no displayable information associated with windows
> other than buffer names.
Yes, but names can be assigned. In this case, only two names
are needed. Just as for Ediff, we could use A & B, e.g., A
for the selected window.
> >> 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'.
>
> There are still open questions about this new variable, e.g.:
> what should be recorded in `last-selected-window' in case of
> `C-x 0' (`delete-window') when the last window is deleted?
Pick one. The (newly) selected window, for example. Or reset
it to nil or whatever (i.e., none). Selected window makes
sense, I think.
Unless we are going to record a whole history, as for buffers,
we cannot set it to the previous "last". Imagine five `C-x 0'
in a row.
prev parent reply other threads:[~2014-11-28 15:25 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
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 [this message]
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=5df4c77f-ec7f-4084-88bc-737288ae815e@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).