From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Branislav Zahradník" <happy.barney@gmail.com>, 74509@debbugs.gnu.org
Subject: bug#74509: Feature request - smerge-mode
Date: Sun, 01 Dec 2024 18:51:22 -0500 [thread overview]
Message-ID: <jwvbjxvvulc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86bjxx817w.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Nov 2024 12:28:35 +0200")
>> # keybinding
>> would be nice to provide default keybinding for smerge-swap: C-c ^ s
Interesting. I've never found a use for that command, personally.
Could you give some hint for the situations where you found it handy?
>> # smerge-extend
>> Helpful when user intent to keep both.
Sorry: to keep both what?
>> (defun smerge-extend ()
>> "Copy the line directly following the conflict into both upper and lower sections.
Hmm... Why just one line and why only from the end?
[ IOW, here as well, I'm curious what is the kind of scenario where you
use that command. ]
>> This is useful when both versions need to share some common code that follows the conflict."
Hmm... my conflicts have usually 3 sections, so "both" isn't right.
[ Unless you specifically chose 2-way conflicts, I recommend you
investigate how to get 3-way conflicts, because they give a lot more
information and allow for example `smerge-resolve` to "just work" in
more cases. YMMV, but personally whenever I'm faced with a 2-way
conflict, I'm frustrated. ]
Stefan
next prev parent reply other threads:[~2024-12-01 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 8:17 bug#74509: Feature request - smerge-mode Branislav Zahradník
2024-11-30 10:28 ` Eli Zaretskii
2024-12-01 23:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-02 7:59 ` Branislav Zahradník
2024-12-03 3:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03 6:39 ` Branislav Zahradník
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=jwvbjxvvulc.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74509@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=happy.barney@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).