emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Marking/highlighting text temporarily
Date: Thu, 30 Apr 2015 09:45:55 +0800	[thread overview]
Message-ID: <87pp6m5qy4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 878udahabq.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Yup, "annotation mechanism" is about right. Just to be clear, you think
>> it fits into the category of incubation-prior-to-core?
>
> I think so.
>
>> If anyone thinks that this mechanism warrants actual new Org syntax, I'd
>> be happy to work on implementing that.
>
> I also think a new syntax is needed. But, please, let's keep it as
> simple as possible.

We're just talking about annotations-plus-metadata here, right? Not
actual in-text TODOs?

From what I can tell, rasmus seems to be proposing an in-text TODO,
while John's headed in the direction of replicating Track Changes
functionality. I've definitely wanted some sort of a track changes
equivalent in Org, but we'd want to be careful about this.

Assuming we're just talking about annotations on steriods, here are some
things I'd personally like to have:

1. Annotations attached to arbitrary text in the buffer. The buffer text
   should be visible, the annotation data invisible (basically the way
   links work right now).
2. Plain annotation: just a chunk of free-form paragraph text that is
   attached to the buffer text.
3. Replacement text: an alternate version of the buffer text; this could
   be the basis of track changes stuff.
4. Timestamps
5. Custom highlighting
6. Full element status: this would allow parsing of the various
   properties, and more fully-featured export options.
7. "Author" metadata would probably be unnecessary with full access to
   the export channels, but it might still be desirable.
8. Options-line switches to export with annotation, export without
   annotation, and export using replacement text.

That's all I can think of, just trying to get the ball rolling. I don't
have any opinions about actual syntax, though something with curly
braces might be nice.

Eric

  reply	other threads:[~2015-04-30  1:46 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 [this message]
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
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=87pp6m5qy4.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).