From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Marking/highlighting text temporarily
Date: Mon, 18 May 2015 15:16:52 +0200 [thread overview]
Message-ID: <87k2w6uit7.fsf@gmx.us> (raw)
In-Reply-To: 87lhgmrtrd.fsf@nicolasgoaziou.fr
Hi,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> But note that I am more interested in an inline noting/todo functionality
>> as opposed to annotation functionality.
>
> Inline noting is
>
>
> Text[@:1][@]
>
> * Annotations
>
> [@:1:] My note.
My guess would be that most notes are short. For such notes, but not
necessarily for longer notes, [@:NOTE] would be more convenient. Though I
don't know what the "@" signifies. I think whatever is the value of
#+TODO makes more sense as prefixes.
I don't think it would be easy to convince coauthors of documents, who are
not using Emacs, that this is something "easy" to use. I guess not many
people do XML in Nano or Notepad, since keeping track of opening and
closing tags is a pain.
Formatting tags, e.g. *, are somehow natural and shorter. Blocks are
"easy" to see.
> 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.
>> Also, for annotation, would it not be annoying, in review session say, to
>> have the notes so "far away" from the text? Perhaps not with the right
>> helping tools.
>
> Again, not with proper tooling, e.g, remote editing like footnotes.
But this is a change to the *format*, not its principal editor.
—Rasmus
--
Er du tosset for noge' lårt!
next prev parent reply other threads:[~2015-05-18 13:17 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 [this message]
2015-05-18 15:44 ` Eric S Fraga
2015-05-18 16:31 ` Rasmus
2015-05-18 20:49 ` Eric Abrahamsen
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=87k2w6uit7.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).