From: Ihor Radchenko <yantar92@posteo.net>
To: James Thomas <jimjoe@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] tchanges.el: Collaborate with word processor (docx) users using 'track changes'
Date: Mon, 15 Jul 2024 19:35:08 +0000 [thread overview]
Message-ID: <87bk2yih3n.fsf@localhost> (raw)
In-Reply-To: <86frsaxxut.fsf@gmx.net>
James Thomas <jimjoe@gmx.net> writes:
>> Well. My dream is to have native Org markup for comments. With
>> appropriate UI to view/edit them.
>>
>> Maybe something based on footnotes.
>
> Footnotes are, at least technically, for a point and not a region. Any
> thoughts about how to extend that?
For example, re-using the idea of inline special blocks we discussed in
https://list.orgmode.org/875xwqj4tl.fsf@localhost/
Something like
@note{short inline comment}{<text the comment talks about>}
@note{[cn:X: another inline comment]}{<text the comment talks about>}
Text that has nothing to do with comment. @note{[cn:X]}{another part of
text related to the same comment X}
@note{[cn:Y]}{<text commented with a long remote comment>}
...
...
...
[cn:Y] Long comment, maybe even a discussion
- (by John) Involving different parties
- (by Mark) with replies, etc.
The idea is to use, say [cn:X] (comment note), instead of [fn:X].
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-07-15 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 11:39 [ANN] tchanges.el: Collaborate with word processor (docx) users using 'track changes' James Thomas
2024-07-09 14:23 ` Ihor Radchenko
2024-07-09 20:36 ` James Thomas
2024-07-11 14:23 ` Ihor Radchenko
2024-07-11 21:10 ` James Thomas
2024-07-13 14:18 ` Ihor Radchenko
2024-07-13 23:56 ` James Thomas
2024-07-15 14:40 ` Ihor Radchenko
2024-07-15 19:24 ` James Thomas
2024-07-15 19:35 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk2yih3n.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jimjoe@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.