From: Samuel Wales <samologist@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [OT] org and diff
Date: Tue, 27 Dec 2022 19:30:26 -0700 [thread overview]
Message-ID: <CAJcAo8sRKGoYD1f80vJKz6n+E6W3DXzNDHNanr2dBRmHo6LHzw@mail.gmail.com> (raw)
In-Reply-To: <87h6xuctqm.fsf@mbork.pl>
hi marcin,
thanks for your blog post on my crash-proof editing idea.
more below
On 12/17/22, Marcin Borkowski <mbork@mbork.pl> wrote:
>
> On 2022-12-17, at 03:06, Samuel Wales <samologist@gmail.com> wrote:
>
>> marcin> One question I'd ask is: how important a legible diff is to
>> you? I keep my Org files in Git, too, but if /I/ know what was
>> changed, I just don't care about diff going nuts and I treat it as
>> (more or less) Git's internal implementation detail.
>>
>> for org, i mostly use git for reviewing changes. it is only one step
>> more sophisticated than saving old and diffing.
>>
>> i have lots of tools for improving diff, but this intermingling
[n.b. i have an still unpubolished package for 30 years that
postprocesses diff and is extremely powerful, and it can if you are
reviewing an ientire repo changes, to some degree nullify the
intermingling issue, but its integration with magit, and magit's bugs
with intra-hunk staging [2 bugs ime], make the intermingling an issue.
with no bugs, less of an issue, mnerely because it is desirable to use
magit instead of merely reviewing it and intra-hunk staging [and
killing] is part of that. but i use old magit, with --- +++, istead
of new magit, which does not supply headers. idk if new magit fixes
the bugs.
so really i was askig about the intermingling issue and whetehr it
could be mitigated at the magit/git level.]
> Well, "months of changes" seems tough. I sometimes (rarely) have to
> enter 2 days' worth of changes... It requires discipline, but
> discipline pays off in /so many areas of life/...
not sure what you men to say in this case about discipline. my
circumstances if i told you about you'd be surprised. my physical
survival is very much at issue and i have no support for dalin with
it.
i.e. not sure if this was aimed at me or a general comment, and the
emphasis i wasn't sure what it was referring to.
>
>> days as normal. i find reviewing changes to be valuable. every once
>> in a while i discover data corruption or something that i forgot etc.
>
> Yes, same here.
>
>> i wonder if diff, or difftastic, could be taught or postprocessed to
>> do merely one thing: try to preserve stuff between "^\\*+ ". that is
>> probably too optimistic, but imagine a --preserve-between option.
>
> I afraid so. Difftastic does not support Org mode format. However, the
huh. so it's a hard problem [i.e. parser needed rather than merely
kluydging with entries]. :[
> tree-sitter page claims that Org parser is under way, so there's hope
> (AFAIK difftastic uses tree-sitter under the hood).
great.
>
> Best,
> mbork
>
> --
> Marcin Borkowski
> http://mbork.pl
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-12-28 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 5:15 [OT] org and diff Samuel Wales
2022-11-13 5:32 ` Ihor Radchenko
2022-11-13 6:06 ` Samuel Wales
2022-11-15 16:58 ` Max Nikulin
2022-11-13 5:38 ` Samuel Wales
2022-11-13 9:32 ` Marcin Borkowski
2022-11-22 3:06 ` Samuel Wales
2022-11-22 3:17 ` Samuel Wales
2022-12-17 2:06 ` Samuel Wales
2022-12-17 8:36 ` Marcin Borkowski
2022-12-17 8:41 ` Ihor Radchenko
2022-12-28 2:30 ` Samuel Wales [this message]
2022-12-28 2:32 ` Samuel Wales
2022-12-28 6:35 ` Marcin Borkowski
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=CAJcAo8sRKGoYD1f80vJKz6n+E6W3DXzNDHNanr2dBRmHo6LHzw@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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.