From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Marking/highlighting text temporarily Date: Mon, 18 May 2015 16:49:20 -0400 Message-ID: <87egmdfw6n.fsf@ericabrahamsen.net> References: <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> <87pp6m5qy4.fsf@ericabrahamsen.net> <873837gyn9.fsf@nicolasgoaziou.fr> <87d21yw6m6.fsf@pank.eu> <87lhgmrtrd.fsf@nicolasgoaziou.fr> <87k2w6uit7.fsf@gmx.us> <87fv6t28qb.fsf@delle7240.chemeng.ucl.ac.uk> <874mn9u9t3.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33942) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuRyn-0003d9-N9 for emacs-orgmode@gnu.org; Mon, 18 May 2015 16:49:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YuRyi-0005zt-TR for emacs-orgmode@gnu.org; Mon, 18 May 2015 16:49:41 -0400 Received: from plane.gmane.org ([80.91.229.3]:55986) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuRyi-0005zn-NV for emacs-orgmode@gnu.org; Mon, 18 May 2015 16:49:36 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YuRyh-0005we-L2 for emacs-orgmode@gnu.org; Mon, 18 May 2015 22:49:35 +0200 Received: from rrcs-50-74-38-66.nyc.biz.rr.com ([50.74.38.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 May 2015 22:49:35 +0200 Received: from eric by rrcs-50-74-38-66.nyc.biz.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 May 2015 22:49:35 +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: > Eric S Fraga writes: > >> On Monday, 18 May 2015 at 15:16, Rasmus wrote: >>> Nicolas Goaziou writes: >>>> I don't know what is a TODO functionality since you suggest to not make >>>> it appear in the agenda. >>> >>> E.g. "Sentence about BAR [TODO: add reference to FOO and check BAZ]". I >>> don't need that in my agenda. >> >> Exactly. I use inlinetasks a lot for file local TODO items that are not >> meant to appear in my agenda. They are notes for things I need to do, >> typically, to finish a paper. Being able to "C-c / t" to find them all >> easily is great. I would expect the same functionality from any >> replacement. > > Would it be bad if I admit I have no idea how to use sparse trees? The > remind me of Vim, except in Vim i eventually figured out that I could quit > it via :q. > > I would probably use occur or a restricted agenda. > > I would want inlinetodos in my "global"/usual agenda. > >> In terms of format, I also dislike opening and closing tags except for >> short formatting uses. I would prefer [COMMENT: this is very >> interesting] and [TODO: I need to update this]. Or even [[TODO:...]] to >> be less worried about running into problems with text use of [...]. > > I think [[TODO:]] is a link... We're coming back around to the beginning of the conversation! I still think we started off talking about two different things. One is a replacement for inlinetasks that's actually inline. The other is an annotation system that could be used for collaboration, and might be taking aim at Track Changes in some way. It looks like we've gone off in the inlinetasks direction. I'll admit that what I really want is an honest-to-goodness first-class-citizen inline TODO. Something attached to a specific run of text, that has a TODO keyword and tags. Probably scheduling? Probably not properties, I don't know. Personally I'd prefer that the contents of the TODO were hidden (a la links), because (like Eric F) I would use this for notes on pieces of writing, and having big ugly chunks of highlighted spaghetti in the middle of a paragraph makes it hard to write. How technically difficult would that be? If it slows down agenda creation too badly, maybe we could have a user option that defaults to skipping inline todos in agenda creation. I was lukewarm about Nicolas' earlier syntax proposal because it simply doesn't seem distinct enough from footnotes. Just some random reactions, Eric