From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Marking/highlighting text temporarily Date: Mon, 18 May 2015 18:25:20 +0200 Message-ID: <878uclua33.fsf@gmx.us> References: <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> <87pp6m5qy4.fsf@ericabrahamsen.net> <873837gyn9.fsf@nicolasgoaziou.fr> <87d21yw6m6.fsf@pank.eu> <87lhgmrtrd.fsf@nicolasgoaziou.fr> <87k2w6uit7.fsf@gmx.us> <87zj51ubpg.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50651) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuNr5-0008C7-Dy for emacs-orgmode@gnu.org; Mon, 18 May 2015 12:25:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YuNr1-0000ml-C1 for emacs-orgmode@gnu.org; Mon, 18 May 2015 12:25:27 -0400 Received: from mout.gmx.net ([212.227.15.18]:56683) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuNr1-0000mS-1c for emacs-orgmode@gnu.org; Mon, 18 May 2015 12:25:23 -0400 Received: from x200s ([104.238.169.146]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MPlsg-1YpPlo1MNm-004xA0 for ; Mon, 18 May 2015 18:25:22 +0200 In-Reply-To: <87zj51ubpg.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 18 May 2015 17:50:19 +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: >> My guess would be that most notes are short. For such notes, but not >> necessarily for longer notes, [@:NOTE] would be more convenient. > > This is very limited: you cannot write two paragraphs in your note. Fine whit me. For that I I have inlinetasks. >> Though I don't know what the "@" signifies.=20 > > AnnoTate? I did not see that coming. That's a "meh" from me :) >> I think whatever is the value of #+TODO makes more sense as prefixes. > > You turn every annotation into a task. Again, this is very restrictive. I don't think so, e.g. #+TODO: DISCUSS DISAGREE | RESOLVED DROPPED And judging from the manual people are doing much more complicated stuff than that (my usage is pretty simple). > Since you're talking about "TODO functionality", what features would > this share with regular tasks, defined with headlines or inlinetasks? The tags. They are notes related to say a sentence, so you put a note at the end of a sentence. Spatial TODOs. > Anyway, we're speaking of two different things, e.g., I think it's > important to be able to mark exactly which part of the document you're > annotating. I agree they are different. > [TODO: ...] cannot do that. Its virtues are compactness, being similar to a list, being C-k friendly, and, IMO, more intuitive. =E2=80=93Rasmus --=20 There are known knowns; there are things we know that we know