emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Thomas <jimjoe@gmx.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] tchanges.el: Collaborate with word processor (docx) users using 'track changes'
Date: Sun, 14 Jul 2024 05:26:40 +0530	[thread overview]
Message-ID: <86a5ikals7.fsf@gmx.net> (raw)
In-Reply-To: <87o771pe8m.fsf@localhost> (Ihor Radchenko's message of "Sat, 13 Jul 2024 14:18:17 +0000")

Ihor Radchenko wrote:

> James Thomas writes:
>
>>> What about comments? Are they stored into Org mode file or separately?
>>
>> 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.

(If you're talking about markup within the comment text, that's
obviously orthogonal to this)

I'd put up an updated the demo animation with this, if you want to see.

Regards,
James


  reply	other threads:[~2024-07-13 23:57 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 [this message]
2024-07-15 14:40             ` Ihor Radchenko
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

  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=86a5ikals7.fsf@gmx.net \
    --to=jimjoe@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.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).