From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"Alain.Cochard@unistra.fr" <Alain.Cochard@unistra.fr>
Subject: Re: How to move from inline tasks to drawers? [was: How to change the width of a latex exported inlinetask?]
Date: Tue, 05 Nov 2019 07:49:34 -0500 [thread overview]
Message-ID: <m2zhhaxzc1.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <874kzi7l70.fsf@ucl.ac.uk>
I use it when editing papers mostly. The main difference is I can put
them inline {>~ @jk here is a comment.~<} in a paragraph. I use them to
mark {>.tpyos.<}, text for {>-deletion-<} removal, or {>+insertion+<},
{y>highlighted text <y}, etc. There is some reasonable export code for
these in html and latex. They are like a generalization of an org-link
in a sexp like form, so you can include metadata like an author name, or
other things.
These have a track change kind of functionality (that turns out to be
quite hard to fully replicate) so you can accept or reject each
editmark. Similar to org-links, each editmark can have a variety of
other actions, e.g. a typo has an action to spell check it, and a
file/audio mark can open or play the file.
I also have some diff functions to generate diffs with these markups
from versions of files, including git versions for integration latex
diff, etc.
It does most of what I want well now, but there are still some corners I
don't go into where it doesn't do exactly everything yet, or where I
haven't tested it very fully (e.g. the diffs).
Fraga, Eric <e.fraga@ucl.ac.uk> writes:
> On Monday, 4 Nov 2019 at 15:14, John Kitchin wrote:
>> I have been exploring the use of something I call editmarks for this
>
> Out of curiousity, what do these give you that drawers would not? I use
> :todo: and :note: drawers.
>
> For syntax highlighting, I use hi-lock-mode with, for instance, this
> pattern to highlight todo drawers:
>
> # Hi-lock: (("^:todo:" (0 'hi-yellow prepend)))
>
> 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:[~2019-11-05 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 13:01 How to move from inline tasks to drawers? [was: How to change the width of a latex exported inlinetask?] Alain.Cochard
2019-11-03 13:50 ` Fraga, Eric
2019-11-04 20:14 ` John Kitchin
2019-11-04 20:30 ` Samuel Wales
2019-11-05 8:59 ` Fraga, Eric
2019-11-05 12:49 ` John Kitchin [this message]
2019-11-05 13:07 ` Fraga, Eric
2019-11-05 13:28 ` John Kitchin
2019-11-05 13:45 ` Fraga, Eric
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=m2zhhaxzc1.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=Alain.Cochard@unistra.fr \
--cc=e.fraga@ucl.ac.uk \
--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).