From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Marking/highlighting text temporarily
Date: Wed, 29 Apr 2015 09:52:34 -0400 [thread overview]
Message-ID: <m2h9rzhwil.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87r3r3873i.fsf@ericabrahamsen.net>
Eric Abrahamsen writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Would this be eligible?
>>
>> Not that my .02€ are worth much, but I think the idea of inline notes is
>> good, but I don't think it should be done using links. See e.g. the
>> discussion on citation which introduced a [cite:⋯] command. A [comment:⋯]
>> command would also IMO make much more sense than [[comment:X][Y]] as was
>> allowed last time I read your patch (in the weekend, I think).
>
> Wow, I just went back and looked at the cite thread. That was
> bewildering. I don't see a direct connection here, though -- cite was
> needed for very specific academic purposes, with very clearly-defined
> needs. Comment is much floppier: good for anything from notes-to-self,
> to notes-to-editor, to notes-to-no-one.
>
> *None* of the complexity is in the format itself: if you unloaded
> org-comment, the comment links would be perfectly human-readable. All of
> the complexity is in helper functions for manipulating them. I suppose
> it would be possible to define some non-link syntax for them, but why do
> that when the link syntax works perfectly well?
The only reason I can see (coming from someone who uses links liberally
for other purposes ;) is just to avoid the hacks required to get extra
functionality, e.g. as you alluded to applying different faces, storing
additional information (author, timestamp, etc...), avoiding a need to
add a link type-checking for collecting comments (although, this is not
a very difficult step).
On the link side, they work perfectly well for the simplest kind of
comment, and because of that, there is a working prototype already. But,
I think extending it beyond this will require the hackery described
above. I don't have a sense if it is more work than defining a new
syntax, or the long term maintenance costs of that approach. For me, it
is work I already know how to do. I admit though, that does not mean it
is better than a new syntax ;)
Maybe a study of the cite syntax code would clarify the differences. Can
anyone point me to a code repository where we could read that code?
>
>> On inclusion in contrib I think you can put anything org-ish there. It's
>> better if the copyright is cleared in case we want to make it part of
>> core, but it's not necessary. There's little difference between core and
>> contrib as neither are included in Emacs and thus are hard to rely on.
>>
>> Since you use cl-lib (last I checked) it could not be part of Org before
>> 8.4.
>
> Ah, that's a good point. cl-lib isn't necessary, just convenient, and
> could be removed.
>
> Thanks,
> Eric
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-04-29 13:52 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 [this message]
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
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=m2h9rzhwil.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).