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 14:40:01 +0000 [thread overview]
Message-ID: <875xt6k9by.fsf@localhost> (raw)
In-Reply-To: <86a5ikals7.fsf@gmx.net>
James Thomas <jimjoe@gmx.net> writes:
>>> They're loaded on import and view/edit/add-able before re-exporting. A
>>> 'Save WIP' feature for writing to disk until then is on the TODO list.
>>
>> Are the comments also using Org markup? Or is it something more ad-hoc?
>
> The comments are separately stored in bookmark.el bookmarks. I'd briefly
> considered also using a fake backend like "@@comment:the annotation
> text@@" inline for it specifically for org, but preferred the former due
> to the easier sorting/browsing etc.; and I also didn't want to maintain
> the state in two places. But if you have better ideas, please tell me.
Well. My dream is to have native Org markup for comments. With
appropriate UI to view/edit them.
Maybe something based on footnotes.
> (If you're talking about markup within the comment text, that's
> obviously orthogonal to this)
I was talking about that too :)
If we have native markup for comments in Org, may as well allow the rest
of Org markup there.
--
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>
next prev parent reply other threads:[~2024-07-15 14:39 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 [this message]
2024-07-15 19:24 ` James Thomas
2024-07-15 19:35 ` Ihor Radchenko
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=875xt6k9by.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.