all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Tweaking magit/diff mode to be more helpful in text editing
Date: Tue, 31 May 2016 14:49:35 +0800	[thread overview]
Message-ID: <87shwyvi0w.fsf@ericabrahamsen.net> (raw)

So I do a fair amount of writing in Org, in files that are kept in a git
repository, and I've found that, when editing large documents, it can be
nice to have the Magit Diff buffer open to one side, which I can refresh
from time to time and see the edits I've made. It's kind of an
alternative to Track Changes, etc.

I've set `magit-diff-refine-hunk' to 'all, and that helps distinguish
the actual edits from the fact that the paragraphs have been re-filled.
It's not ideal, but it's okay.

I'm currently editing someone else's (very long) document, and instead
of actually using track changes in LibreOffice, I'd much rather give him
a clean odt document exported from Org, and along with that an html
document made using diff2html or one of the other similar tools, so he
can check the edits if he wants.

What I'd really like is to find a way (either a diff algorithm or a
Magit tweak) of only showing the actual edits, not the filling. And then
to still be able to export that in a way that will allow me to give the
author a file only showing those edits.

Does anyone have any clever ideas in that direction?

Thanks!
Eric




             reply	other threads:[~2016-05-31  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  6:49 Eric Abrahamsen [this message]
2016-05-31  7:48 ` Tweaking magit/diff mode to be more helpful in text editing Yuri Khan
2016-06-01  3:08   ` Eric Abrahamsen
2016-05-31  7:55 ` tomas
2016-06-01  4:00   ` Eric Abrahamsen
2016-06-01  4:17     ` Yuri Khan
2016-06-01  5:08       ` Eric Abrahamsen

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=87shwyvi0w.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@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.