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: Tue, 28 Apr 2015 15:32:59 -0400 [thread overview]
Message-ID: <m2fv7k121g.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87r3r57zre.fsf@ericabrahamsen.net>
Eric Abrahamsen writes:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Hi Eric,
>>
>> I added some functions in the attachment. they colorize the comments,
>> add an org-comment menu to the org-menu, and some functions for pop to
>> and delete comments from the list mode, and a hydra for commands to
>> insert comments. Do you want to get this up on github to facilitate
>> developing it?
>
> Oh great! Thanks a lot. We are duplicating effort a bit here (but only a
> bit, I'd also written display/delete functions for the list buffer), so
> yes, it would be good to coordinate development.
>
> I suppose it depends a bit on where this is going to end up: I'm
> assuming either org/contrib/lisp, or else as an Elpa package. I don't
> see much difference, except in terms of accessibility to contributors --
> I don't have access to the Org repo, but putting it there might get more
> contributors on balance. As a package only I would have direct access.
> What do you think?
I think on github you can give others direct access, or respond to pull
requests. Either way works.
>
> The hydra thing is interesting -- I wasn't aware of that package. Better
> not to require it unconditionally though, right?
You could make this conditional if hydra is installed. It is
sufficiently simple that you could leave it out too.
>
> Thanks,
> Eric
>
>> Eric Abrahamsen writes:
>>
>>> Eric Abrahamsen
>>
>>
>> <eric@ericabrahamsen.net> writes:
>>>
>>>> Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>>>>
>>>>> On 25-Apr-2015, at 6:22 am, John Kitchin <jkitchin@andrew.cmu.edu>
>>>>> wrote:
>>>>>
>>>>> Inspired by this conversation, I hacked up this functional comment
>>>>> link:
>>>>>
>>>>> http://kitchingroup.cheme.cmu.edu/blog/2015/04/24/Commenting-in-org-files/
>>>>>
>>>>>
>>>>> It has a custom link type that exports in html and latex, and when
>>>>> you click on it, it asks if you want to delete the comment.
>>>>>
>>>>> Nice. One small issue is that when I highlight a text and add comment
>>>>> to it, and then delete the comment, one space following the last word
>>>>> is removed.
>>>>>
>>>>> Also, it would be good to make the comment stand out in LaTeX (and
>>>>> other) exports, preferably by pushing it to the margin (so it does not
>>>>> move everything else).
>>>>
>>>> Hang on a bit, I'm wasting my afternoon expanding this...
>>>
>>> Okay, this is as far as I got today. I changed some behavior from John's
>>> implementation: when following the links, it seemed like displaying the
>>> comment text would be more useful than deleting it -- I think many of us
>>> have "delete-org-link" functions lying around. I also couldn't get the
>>> add-comment thing to work, as it complained when there was no region, so
>>> I changed how that works.
>>>
>>> Lastly, I spent most of my time learning how tabular list mode works,
>>> and haven't actually tested the export. Will save that for tomorrow.
>>> Otherwise, here's the introduction from the Commentary. Comments and
>>> suggestions very welcome!
>>>
>>>
>>>
>>> Provides a new link type for Org that allows you to create comments
>>> on arbitrary chunks of text. The link prefix is "comment:".
>>>
>>> Add comments with `org-comment-add-comment'. Following the link
>>> will display the text of the comment in a pop-up buffer. The
>>> buffer is in special-mode, hit "q" to dismiss it.
>>>
>>> Call `org-comment-display-comments' to see all comments in a buffer.
>>>
>>> See the `org-comment-[backend]-export-style' options for ways to
>>> format comments in export.
>>>
>>> TODO:
>>>
>>> 1. Better export customization options.
>>> 2. What does the ODT comment XML look like?
>>> 3. More functions in the display comment buffer: copy as
>>> kill... what else?
>>> 4. More functions in the comments list buffer, to display, pop to,
>>> delete, and edit comment text.
>>> 5. Is it possible to have multi-line filled tabular list items?
>>> Long comments are not very useful if you can't see the whole thing.
>>> 5. Allow multiple comment list buffers attached to different Org
>>> buffers.
>>> 6. Maybe a minor mode for ease of manipulating comments?
>>
>> --
>> 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
--
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-28 19:33 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 [this message]
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
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=m2fv7k121g.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).