From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: General advice beyond Org Date: Sat, 19 May 2018 18:24:49 -0700 Message-ID: References: <7dc580d0ea76c21328dc586ffadb5499@openmail.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <7dc580d0ea76c21328dc586ffadb5499@openmail.cc> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sender: "help-gnu-emacs" To: edgar@openmail.cc Cc: help-gnu-emacs@gnu.org, emacs-orgmode@gnu.org List-Id: emacs-orgmode.gnu.org perhaps we can start thinking about improving registration between formats? if you export org [you posted to org mailng list] to a foreign format, you want your collaborator to be able to edit, save, send back without raising a sweat. now you have to integrate the changes. you want to do this without annoyance. suppose you export comments in the foreign format that contain the equivalent of persistent markers. you might or might not be willing to put org id or custom id on every heading, but there might be workarounds that are not so intrusive. maybe your source can contain comments with markers. dunno. if your exported document is a subtree within a huge org file that you edit all the time, registration allows your software to identify that subtree, so you're not trying to change anything outside that subtree. that alone is a win. but maybe we can do more. the markers can register sections or even paragraphs if you're doing intensive collaboration. the tricky part might be getting standard tools to understand that the mapping of markers takes precedence over everything else. details of this handwavey and possibly impossible brainstorm are left as an exercise for the reader.