From: Richard Copley <rcopley@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Glenn Morris <rgm@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Stephan.Mueller@microsoft.com,
Noam Postavsky <npostavs@users.sourceforge.net>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Regarding smerge upper/lower; needs NEWS
Date: Thu, 15 Mar 2018 16:09:03 +0000 [thread overview]
Message-ID: <CAPM58oiUhnPbpapi26eOLQJrWWD6wdjYZXVnATNN2DKkO1e5nw@mail.gmail.com> (raw)
In-Reply-To: <jwvvadx4ak3.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On 15 March 2018 at 15:43, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > In "smerge-ediff", I think.
>
> smerge-ediff is a command which basically *leaves* SMerge (the whole
> purpose of SMerge is to do the conflict resolution directly in the one
> buffer rather than going through Ediff, which is a fine tool but too
> heavyweight for my taste in 99% of the cases (tho I really appreciate it
> for that remaining 1%)).
>
> Also the upper/lower (or any other nomenclature SMerge uses) only
> affects the name of the generated buffers: Ediff labels will simply
> always be A/B with corresponding key-bindings and the upper/lower
> terminology of SMerge just disappears.
>
> So I guess what you're saying is that we should improve the consistency
> in the naming used by SMerge and Ediff. That's a good point.
> And indeed upper/lower doesn't work for Ediff.
>
>
> Stefan
>
Thanks Stefan and Kaushal.
I'll revert the change locally for now.
I don't use Smerge itself (perhaps I should learn), so I suppose it's
natural that I don't understand why UPPER and LOWER are such good labels
that it's important to keep them.
[-- Attachment #2: Type: text/html, Size: 1725 bytes --]
next prev parent reply other threads:[~2018-03-15 16:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 14:01 Regarding smerge upper/lower; needs NEWS Kaushal Modi
2017-03-24 19:46 ` Glenn Morris
2017-04-07 18:06 ` Richard Copley
2017-04-07 19:09 ` Noam Postavsky
2017-04-07 19:23 ` Richard Copley
2017-04-07 19:24 ` Richard Copley
2017-04-07 19:53 ` Richard Copley
2017-04-13 0:49 ` Noam Postavsky
2017-04-13 18:32 ` Stefan Monnier
2017-04-13 19:03 ` Noam Postavsky
[not found] ` <CY1PR03MB2251867FBF42034CF55007ADF0020@CY1PR03MB2251.namprd03.prod.outlook.com>
2017-04-13 19:34 ` Stephan Mueller
2018-03-15 14:37 ` Richard Copley
2018-03-15 15:04 ` Stefan Monnier
2018-03-15 15:30 ` Richard Copley
2018-03-15 15:43 ` Stefan Monnier
2018-03-15 16:09 ` Richard Copley [this message]
2018-03-15 15:30 ` Kaushal Modi
2018-03-15 15:37 ` Richard Copley
2018-03-15 15:39 ` Kaushal Modi
2018-03-15 16:45 ` Glenn Morris
2018-03-15 17:00 ` Eli Zaretskii
2018-03-15 17:06 ` Óscar Fuentes
2018-03-15 17:15 ` Eli Zaretskii
2018-03-15 18:15 ` Stefan Monnier
2018-03-15 18:45 ` Drew Adams
2018-03-15 19:05 ` Stefan Monnier
2018-03-15 19:44 ` Drew Adams
2018-03-15 17:14 ` Richard Copley
2018-03-15 18:54 ` Stefan Monnier
2018-03-15 20:10 ` Richard Copley
2018-03-16 2:20 ` Noam Postavsky
2018-03-16 12:23 ` Stefan Monnier
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=CAPM58oiUhnPbpapi26eOLQJrWWD6wdjYZXVnATNN2DKkO1e5nw@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=Stephan.Mueller@microsoft.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
--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).