From: tolugboji <tolugboji@protonmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Differences with side-by-side modification
Date: Thu, 21 Oct 2021 10:54:19 +0000 [thread overview]
Message-ID: <aOuYBM5cmlXyG7ScOhyU1RkUWge7mZfyDK1F_ADLvIT0fGjAryRGEaOmNNdqjYIYIZFlNm9AvFAB8Q8sEoTgIurVrU0owa9iQAzvfutcNKw=@protonmail.com> (raw)
In-Reply-To: <87v91qwuj5.fsf@web.de>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, October 21st, 2021 at 10:18 AM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> tolugboji tolugboji@protonmail.com writes:
>
> > Got confused on what to do because the window seemed to recognise the mouse
> >
> > over options, but pressing mouse button did nothing.
>
> Note that by default Ediff uses a standalone control frame (which means
>
> "window" in the outside world) and that frame should be selected to
>
> enter the control commands. Dunno if that is related to your
>
> experiences.
>
> Anyway, it's possible to edit the currently Ediffed buffers. You can,
>
> for example, copy regions from one side to the other. The quick help
>
> (key: ?) is your friend. ? typed a second time removes the quick help.
>
> It's also possible to edit the buffers manually while they are Ediffed.
>
> You then hit ! to refresh the diff highlighting. h to toggle the
>
> highlighting if it distracts while editing.
>
> Michael.
That helps a lot Michael. Was initially bothered by the small command frame
that pops up and having to use ?. But using ? again to reduce the frame
is good and I like the highlighting.
I have some code that I need to split up into different files, and can get
to do some emacs practice doing so. I come from vscode and similar internal
environments (one big mess when tools are invented internally).
next prev parent reply other threads:[~2021-10-21 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 9:23 Differences with side-by-side modification tolugboji via Users list for the GNU Emacs text editor
2021-10-21 9:33 ` tomas
2021-10-21 9:45 ` tolugboji
2021-10-21 9:54 ` tomas
2021-10-21 9:57 ` Michael Heerdegen
2021-10-21 10:04 ` tolugboji
2021-10-21 10:12 ` tomas
2021-10-21 10:18 ` Michael Heerdegen
2021-10-21 10:54 ` tolugboji [this message]
2021-10-21 18:32 ` tolugboji
2021-10-21 20:15 ` Joost Kremers
2021-10-21 21:16 ` tolugboji
2021-10-21 9:35 ` Joost Kremers
2021-10-22 2:08 ` pliyanag
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='aOuYBM5cmlXyG7ScOhyU1RkUWge7mZfyDK1F_ADLvIT0fGjAryRGEaOmNNdqjYIYIZFlNm9AvFAB8Q8sEoTgIurVrU0owa9iQAzvfutcNKw=@protonmail.com' \
--to=tolugboji@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).