From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Marking/highlighting text temporarily Date: Wed, 29 Apr 2015 22:54:17 +0800 Message-ID: <87sibj6l46.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> <87r3r33xo3.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnTO3-0000Pu-3U for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 10:54:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnTNv-0002Wc-Fb for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 10:54:54 -0400 Received: from plane.gmane.org ([80.91.229.3]:51075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnTNv-0002WP-8j for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 10:54:47 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YnTNl-00007s-WE for emacs-orgmode@gnu.org; Wed, 29 Apr 2015 16:54:38 +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 ; Wed, 29 Apr 2015 16:54:37 +0200 Received: from eric by 114.248.23.63 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Apr 2015 16:54:37 +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 Rasmus writes: > Hi, > > Eric Abrahamsen writes: > >> Just to be clear, you think it fits into the category of >> incubation-prior-to-core? > > I think inlinetasks/comments that are actually *inline* would be nice! > >> If anyone thinks that this mechanism warrants actual new Org syntax, I'd >> be happy to work on implementing that. But to be honest, I think it sits >> pretty comfortably on top of what's already available. The only slight >> awkwardness comes when you'd like a different face for the annotation >> links (currently solved with John Kitchin's hi-lock trick), and the fact >> that the link export routines don't have access to the exportation >> info/plist channels (ie, when exporting an annotation link to ODT, I'd >> like to be able to give the annotation an "author" element, but as far >> as I know I can't get access to that). These aren't major flaws. > > See my other post. In addition you'd need to be able to turn them off via > > #+OPTIONS: annotations:nil > > >> I'll admit I have dreamed of a syntax that looks like: [[body text to >> annotate][TODO:Look this up on the internet:@work]]. > > I don't like the example. The ordering is weird. Do the first and the > second bracket need to be tied together? Or would something like this > work: > > body text to annotate [todo@work: Look this up on the internet] > > Or > > [todo@work: Look this up on the internet]{body text to annotate} > [todo@work look this up on the internet: body text to annotate] Okay, so you're basically proposing taking this to a much higher level. I'm totally in favor, in principle, and don't actually care too much what the actual syntax looks like. I do think it would be important to specify the text being annotated, so your first example above wouldn't be too ideal. The others I'd be happy with. As the veteran of several small projects that have died of mission creep, I still wouldn't mind keeping org-comments (I do think it should be renamed org-annotate) as-is, and letting the "real" inline todo project progress separately. Eric