From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: svn and smerge-mode
Date: Wed, 27 Aug 2008 13:47:08 -0400 [thread overview]
Message-ID: <jwvprnucpyg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <18613.5027.950825.923293@kahikatea.snap.net.nz> (Nick Roberts's message of "Wed, 27 Aug 2008 20:43:15 +1200")
>> Basically, the only effect of turning on smerge-mode should be to
>> highlight the conflicts with font-lock (as long as you don't use the C-x
>> ^ prefix, obviously). So which part of smerge-mode annoys you?
>> And more importantly, which part caused you to lose information?
> I just use it too infrequently to remember how it works.
> ISTR I lost my original working (.#) file trying to exit smerge-ediff. It
> wasn't clear to me where the changes I had selected were going to end up (I
> thought I would need to save the *ediff-merge* buffer). Even though I quit
> smerge-ediff without selecting any changes, I was told:
> Conflict resolution finished; you may save the buffer
> Evidently this actually only differed by the conflict markers,
> e.g.,"<<<<<<< filename" vs "<<<<<<< variant A").
> I thought that when I saved this buffer the original working was removed
> although I can't reproduce this now.
> In summary, smerge-mode seems to start off quite innocently but may lead you
> into places that you don't want to be.
So it sounds like a problem in the smerge-ediff code. I never use(d)
that code, so it's not really a surprise. If you can provide
a reproducible testcase, that would be very helpful, but otherwise just
give us as detailed a description as possible (e.g. what .#* file are
you talking about?).
Stefan
next prev parent reply other threads:[~2008-08-27 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 9:23 svn and smerge-mode Nick Roberts
2008-08-26 13:46 ` Stefan Monnier
2008-08-27 8:43 ` Nick Roberts
2008-08-27 17:47 ` Stefan Monnier [this message]
2008-08-27 2:37 ` Miles Bader
2008-08-27 8:47 ` Nick Roberts
2008-08-27 9:36 ` Miles Bader
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=jwvprnucpyg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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).