From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Tweaking magit/diff mode to be more helpful in text editing
Date: Wed, 01 Jun 2016 11:08:24 +0800 [thread overview]
Message-ID: <87lh2psj13.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAP_d_8WrNnsSWS-vqxwQqaYay=zvsqDvOGQgTVbq=fbLPgC3Hw@mail.gmail.com
Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Tue, May 31, 2016 at 12:49 PM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>
>> 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?
>
> I have an idea.
> Whether it’s clever or stupid, is up to you.
>
> Do not fill paragraphs based on line width.
> Wrap lines at stable positions based on sentence structure
> such as sentence and clause boundaries
> like I’m doing here.
>
> This way, diffs will be compact
> (the worst case is when a single line grows too long
> and you split it at a logical point near the middle)
> and line breaks will be eliminated anyway
> when the document is rendered to HTML
> or whatever other form.
>
> (One disadvantage is that it looks like a poem.)
Ha, that would be quite a mental adjustment! I might give it a shot,
though. Perhaps my writing would improve if I treated it like poetry...
next prev parent reply other threads:[~2016-06-01 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 6:49 Tweaking magit/diff mode to be more helpful in text editing Eric Abrahamsen
2016-05-31 7:48 ` Yuri Khan
2016-06-01 3:08 ` Eric Abrahamsen [this message]
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
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=87lh2psj13.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.
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).