all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "19259@debbugs.gnu.org" <19259@debbugs.gnu.org>
Subject: bug#19259: [External] : Re: bug#19259: 25.0.50; Be able to use `compare-windows' in either direction
Date: Tue, 13 Jul 2021 21:57:42 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488717B6D90136282F5D707F3149@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87mtqqndhh.fsf@gnus.org>

> > Especially when `compare-windows' is used repeatedly (e.g. bound to a
> > repeatable key etc.), it can be helpful to be able to sometimes
> > compare backward, toward bob, instead of always forward, toward eob.
> > Please add this enhancement.
> 
> A few days after this bug report (apparently),
> `compare-windows-get-window-function' was added:
> 
> commit 96e6fd3c155b1851e0acd477789535a45b8d3187
> Author:     Juri Linkov <juri@linkov.net>
> AuthorDate: Fri Dec 5 02:50:41 2014 +0200
> 
>     Compare with the most recently used window by default.
> 
>     * lisp/vc/compare-w.el (compare-windows-get-window-function):
>     New defcustom.
> 
> This can be redefined by the user to respond to `C-u' and the like, so I
> don't think there's anything more to do here, and I'm closing this bug
> report.

So your decision is "won't fix".  Telling users they
can, essentially, redefine the command is not what
this request was about.

The request is clearly about fixing `compare-windows'
so that it can go either way - acting like `ediff'.
It specifically mentions `ediff' as a model behavior
in this regard.





      reply	other threads:[~2021-07-13 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 22:53 bug#19259: 25.0.50; Be able to use `compare-windows' in either direction Drew Adams
2014-12-05  0:57 ` Juri Linkov
2014-12-05  2:12   ` Drew Adams
2021-07-13 20:52 ` Lars Ingebrigtsen
2021-07-13 21:57   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488717B6D90136282F5D707F3149@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=19259@debbugs.gnu.org \
    --cc=larsi@gnus.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.