* backporting changes to exported results for collaborative editing
@ 2017-02-07 1:15 Samuel Wales
2017-02-07 5:31 ` Marcin Borkowski
0 siblings, 1 reply; 3+ messages in thread
From: Samuel Wales @ 2017-02-07 1:15 UTC (permalink / raw)
To: emacs-orgmode
suppose you export a subtree to ascii or html, and then a bunch of
people want to help you edit it. obviously you want the changes back
in org.
obviously the best would be if you could give them the source,
complete with comments. but assume that they are not computer people,
and not org people, and you don't want to give them your irrelevant
comments.
also assume you also don't want to give them your irrelevant tasks and
you do not use org-export-with-tasks.
it might be that i already know the answer: just do the best you can
with diff, and request small sets of changes at a time, or request
manual instructions for changes. but perhaps you have ideas?
--
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it -- at any time.
"You’ve really gotta quit this and get moving, because this is murder
by neglect." --- very true words by Johanna Kaiser spoken to US NIH in
conference call with Walter Koroshetz, NINDS director
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>
Denmark: free Karina Hansen NOW.
UPDATE 2016-10: home, but not fully free
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: backporting changes to exported results for collaborative editing
2017-02-07 1:15 backporting changes to exported results for collaborative editing Samuel Wales
@ 2017-02-07 5:31 ` Marcin Borkowski
2017-02-07 18:20 ` Charles C. Berry
0 siblings, 1 reply; 3+ messages in thread
From: Marcin Borkowski @ 2017-02-07 5:31 UTC (permalink / raw)
To: Samuel Wales; +Cc: emacs-orgmode
On 2017-02-07, at 02:15, Samuel Wales <samologist@gmail.com> wrote:
> suppose you export a subtree to ascii or html, and then a bunch of
> people want to help you edit it. obviously you want the changes back
> in org.
>
> obviously the best would be if you could give them the source,
> complete with comments. but assume that they are not computer people,
> and not org people, and you don't want to give them your irrelevant
> comments.
>
> also assume you also don't want to give them your irrelevant tasks and
> you do not use org-export-with-tasks.
>
> it might be that i already know the answer: just do the best you can
> with diff, and request small sets of changes at a time, or request
> manual instructions for changes. but perhaps you have ideas?
Maybe this could be automated a bit? Like, org -> markdown, then
people's edits, then diff generating a patch, then some tool existing
only in my dreams currently that converts the md patch to an org patch,
and then apply that patch to the original org? For small enough
changes, that could actually work, no?
Best,
--
Marcin Borkowski
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: backporting changes to exported results for collaborative editing
2017-02-07 5:31 ` Marcin Borkowski
@ 2017-02-07 18:20 ` Charles C. Berry
0 siblings, 0 replies; 3+ messages in thread
From: Charles C. Berry @ 2017-02-07 18:20 UTC (permalink / raw)
To: Marcin Borkowski; +Cc: emacs-orgmode
On Tue, 7 Feb 2017, Marcin Borkowski wrote:
>
> On 2017-02-07, at 02:15, Samuel Wales <samologist@gmail.com> wrote:
>
>> suppose you export a subtree to ascii or html, and then a bunch of
>> people want to help you edit it. obviously you want the changes back
>> in org.
>>
>> obviously the best would be if you could give them the source,
>> complete with comments. but assume that they are not computer people,
>> and not org people, and you don't want to give them your irrelevant
>> comments.
>>
>> also assume you also don't want to give them your irrelevant tasks and
>> you do not use org-export-with-tasks.
>>
>> it might be that i already know the answer: just do the best you can
>> with diff, and request small sets of changes at a time, or request
>> manual instructions for changes. but perhaps you have ideas?
>
> Maybe this could be automated a bit? Like, org -> markdown, then
> people's edits, then diff generating a patch, then some tool existing
> only in my dreams currently that converts the md patch to an org patch,
> and then apply that patch to the original org? For small enough
> changes, that could actually work, no?
>
Maybe, but this sequence might be easier:
- export subtree to md =edit-me.md= (body-only not needed but cleaner)
- distribute to editor and retrieve as =editted.md=
- in a shell run ~pandoc -o editted.org editted.md~
- M-x ediff-regions RET
- select all of =editted.org=
- select original subtree
- Use `##' to skip the whitespace only diffs.
- resolve the differences as appropriate and/or save the diffs.
Babel blocks/results are *not* be handled seamlessly, so more would
need to be done if your editor wants to revise them. Otherwise, just
skip them.
I guess this might work with ascii or html, but I've not tried it.
Chuck
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-02-07 18:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-07 1:15 backporting changes to exported results for collaborative editing Samuel Wales
2017-02-07 5:31 ` Marcin Borkowski
2017-02-07 18:20 ` Charles C. Berry
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).