From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Marking/highlighting text temporarily Date: Thu, 30 Apr 2015 09:45:55 +0800 Message-ID: <87pp6m5qy4.fsf@ericabrahamsen.net> References: <87a8xyrn39.fsf@pinto.chemeng.ucl.ac.uk> <87bnieufde.fsf@mbork.pl> <87zj5xewsp.fsf@pinto.chemeng.ucl.ac.uk> <87iockmyxy.fsf@ericabrahamsen.net> <87bnicshhc.fsf@ericabrahamsen.net> <87r3r57zre.fsf@ericabrahamsen.net> <87lhhb2uot.fsf@ericabrahamsen.net> <87oam7p6a7.fsf@nicolasgoaziou.fr> <87mw1r865s.fsf@ericabrahamsen.net> <878udahabq.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YndYP-0000zq-MC for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 21:46:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YndYL-0003Ip-Kb for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 21:46:17 -0400 Received: from plane.gmane.org ([80.91.229.3]:33701) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YndYL-0003IX-Do for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 21:46:13 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YndYJ-0000dW-7n for emacs-orgmode@gnu.org; Thu, 30 Apr 2015 03:46:11 +0200 Received: from 114.248.23.63 ([114.248.23.63]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Apr 2015 03:46:11 +0200 Received: from eric by 114.248.23.63 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Apr 2015 03:46:11 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Eric Abrahamsen writes: > >> Yup, "annotation mechanism" is about right. Just to be clear, you think >> it fits into the category of incubation-prior-to-core? > > I think so. > >> If anyone thinks that this mechanism warrants actual new Org syntax, I'd >> be happy to work on implementing that. > > I also think a new syntax is needed. But, please, let's keep it as > simple as possible. We're just talking about annotations-plus-metadata here, right? Not actual in-text TODOs? >From what I can tell, rasmus seems to be proposing an in-text TODO, while John's headed in the direction of replicating Track Changes functionality. I've definitely wanted some sort of a track changes equivalent in Org, but we'd want to be careful about this. Assuming we're just talking about annotations on steriods, here are some things I'd personally like to have: 1. Annotations attached to arbitrary text in the buffer. The buffer text should be visible, the annotation data invisible (basically the way links work right now). 2. Plain annotation: just a chunk of free-form paragraph text that is attached to the buffer text. 3. Replacement text: an alternate version of the buffer text; this could be the basis of track changes stuff. 4. Timestamps 5. Custom highlighting 6. Full element status: this would allow parsing of the various properties, and more fully-featured export options. 7. "Author" metadata would probably be unnecessary with full access to the export channels, but it might still be desirable. 8. Options-line switches to export with annotation, export without annotation, and export using replacement text. That's all I can think of, just trying to get the ball rolling. I don't have any opinions about actual syntax, though something with curly braces might be nice. Eric