From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: smerge-ediff "MINE" and "OTHER" monikers unhelpful
Date: Wed, 27 Nov 2013 12:37:58 -0500 [thread overview]
Message-ID: <jwvppplhhrf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8761ref7hy.fsf@fencepost.gnu.org> (David Kastrup's message of "Wed, 27 Nov 2013 11:45:29 +0100")
> For one thing, smerge-ediff (purportedly as opposed to the smerge-mode
> not visibly involved in the user interaction) does not expose _any_ of
We can't assume that the user of smerge-ediff does not also use smerge.
So it's important to keep a connection between the names used in smerge
and the names used in ediff. Maybe in your case it's not helpful, but
I think the added text should clarify the problem (and the 5/6 extra
chars may occasionally push the extra info past the truncation, but
this truncation problem exists even without those extra 5/6 chars).
> git pull -r
> it labels the upstream changes as "MINE" and my own changes as "OTHER".
Of course, any tool is free top put the 2 in whichever order they
prefer. Maybe we should revisit the MINE/OTHER names used so far.
But whichever name we use there will need to also be present in
smerge-ediff.
Stefan
next prev parent reply other threads:[~2013-11-27 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zjowpn2s.fsf@fencepost.gnu.org>
2013-11-23 1:42 ` smerge-ediff "MINE" and "OTHER" monikers unhelpful Stefan Monnier
2013-11-23 6:23 ` David Kastrup
2013-11-23 14:33 ` Stefan Monnier
2013-11-23 15:03 ` David Kastrup
2013-11-23 14:07 ` David Kastrup
2013-11-25 15:40 ` Stefan Monnier
2013-11-27 10:45 ` David Kastrup
2013-11-27 17:37 ` Stefan Monnier [this message]
2013-11-27 18:07 ` David Kastrup
2013-11-27 18:45 ` David Kastrup
2013-11-27 20:46 ` Stefan Monnier
2013-11-27 20:54 ` David Kastrup
2013-11-28 8:44 ` Thien-Thi Nguyen
2013-11-28 18:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvppplhhrf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dak@gnu.org \
--cc=emacs-devel@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 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.