From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Marking/highlighting text temporarily
Date: Mon, 18 May 2015 16:49:20 -0400 [thread overview]
Message-ID: <87egmdfw6n.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 874mn9u9t3.fsf@gmx.us
Rasmus <rasmus@gmx.us> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Monday, 18 May 2015 at 15:16, Rasmus wrote:
>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> 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
next prev parent reply other threads:[~2015-05-18 20:49 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 6:19 Marking/highlighting text temporarily Vikas Rawal
2015-04-24 6:42 ` Thomas S. Dye
2015-04-24 7:53 ` Marcin Borkowski
2015-04-24 7:05 ` Glyn Millington
2015-04-24 7:13 ` Eric Abrahamsen
2015-04-24 7:19 ` Eric Abrahamsen
2015-04-24 7:38 ` Fabrice Niessen
2015-04-24 7:40 ` Eric S Fraga
2015-04-24 7:58 ` Marcin Borkowski
2015-04-24 8:48 ` Eric S Fraga
2015-04-24 21:38 ` Vikas Rawal
2015-04-25 0:52 ` John Kitchin
2015-04-25 1:34 ` Eric Abrahamsen
2015-04-25 4:13 ` Vikas Rawal
2015-04-25 7:47 ` Eric Abrahamsen
2015-04-25 9:08 ` Eric Abrahamsen
2015-04-26 18:14 ` John Kitchin
2015-04-27 6:13 ` Eric Abrahamsen
2015-04-27 10:27 ` John Kitchin
2015-04-27 11:11 ` Marcin Borkowski
2015-04-27 12:37 ` Eric Abrahamsen
2015-04-27 12:58 ` John Kitchin
2015-04-27 13:06 ` Eric Abrahamsen
2015-04-27 23:35 ` John Kitchin
2015-04-28 2:28 ` Eric Abrahamsen
2015-04-28 19:32 ` John Kitchin
2015-04-29 8:41 ` Eric Abrahamsen
2015-04-29 9:57 ` Rasmus
2015-04-29 12:14 ` Eric Abrahamsen
2015-04-29 12:31 ` Rasmus
2015-04-29 13:57 ` John Kitchin
2015-04-29 13:52 ` John Kitchin
2015-04-29 10:39 ` Nicolas Goaziou
2015-04-29 12:34 ` Eric Abrahamsen
2015-04-29 12:51 ` Rasmus
2015-04-29 13:21 ` Eric S Fraga
2015-04-29 14:00 ` John Kitchin
2015-04-29 14:42 ` Eric S Fraga
2015-04-29 14:54 ` Eric Abrahamsen
2015-04-29 13:16 ` Eric S Fraga
2015-04-29 14:56 ` Eric Abrahamsen
2015-04-29 13:38 ` John Kitchin
2015-04-29 21:51 ` Nicolas Goaziou
2015-04-30 1:45 ` Eric Abrahamsen
2015-04-30 9:58 ` Rasmus
2015-04-30 11:32 ` Eric S Fraga
2015-04-30 13:45 ` John Kitchin
2015-05-03 13:33 ` Eric Abrahamsen
2015-05-08 10:19 ` Nicolas Goaziou
2015-05-18 9:57 ` Rasmus
2015-05-18 11:48 ` Nicolas Goaziou
2015-05-18 13:16 ` Rasmus
2015-05-18 15:44 ` Eric S Fraga
2015-05-18 16:31 ` Rasmus
2015-05-18 20:49 ` Eric Abrahamsen [this message]
2015-05-18 15:50 ` Nicolas Goaziou
2015-05-18 16:25 ` Rasmus
2015-05-18 16:56 ` Nicolas Goaziou
2015-05-18 17:28 ` Rasmus
2015-05-18 18:36 ` Eric S Fraga
2015-05-19 8:14 ` Nicolas Goaziou
2015-04-28 10:48 ` Eric Abrahamsen
2015-04-25 9:04 ` Eric S Fraga
2015-05-18 21:42 ` Marcin Borkowski
2015-05-28 10:52 ` Alan Schmitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87egmdfw6n.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).