emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Frings <peter.frings@agfa.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: [WISH] Org Importers
Date: Thu, 28 Oct 2010 12:16:51 +0200	[thread overview]
Message-ID: <5CC72533-4B9C-429C-B042-A2F970C24F5C@agfa.com> (raw)
In-Reply-To: <AANLkTinut4dyMruJPSwvKyXDZGWAGmfeEVU+zAAxJLtu@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]


On 28 Oct 2010, at 11:15, Scot Becker wrote:

> Jambunathan,
> 
> (2) could be useful but a bit far-fetched at the
> moment.
>  
> Really?  Lots of us track changes with git, sometimes by means of one of the Emacs interfaces for it like Magit.  You may be thinking of some interface-level features which aren't available by this method, like the ability to annotate changes in the same place you make them, I suppose.  But working this way has a lot of 'features' that "track changes" doesn't.

We once thought of having some markup in our LaTeX files to track changes, offering annotations. If I recall correctly, we had a command \changed{old}{new}{comment}.
You could leave out the new or old text part: newly added  text would be \changed{}{bla bla}{this is new text!}, deleted text would be \changed{completely wrong}{}{what an idiot}. The command would render the old/new text differently (gray, strikethrough, blue, whatever) and add the comment as a margin note.

Maybe something like this would be useful/feasible in Org? (not that I have a need for this -- we never implemented that command, either).

Cheers,
Peter.

[-- Attachment #1.2: Type: text/html, Size: 1669 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-10-28 10:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 16:49 General question on dealing with Latex to word conversion Marvin Doyley
2010-10-26 17:13 ` Graham Smith
2010-10-26 17:46   ` Marvin Doyley
2010-10-26 18:12     ` Graham Smith
2010-10-26 22:40     ` Tomas Hlavaty
2010-10-27 14:15       ` Graham Smith
2010-10-26 18:42 ` Jambunathan K
2010-10-26 20:45   ` Marvin Doyley
2010-10-26 19:48 ` Russell Adams
2010-10-26 20:47   ` Marvin Doyley
2010-10-26 22:46     ` Russell Adams
2010-10-27  3:31 ` Richard Lawrence
2010-10-27 11:24   ` Jeff Horn
2010-10-27 14:57     ` Richard Lawrence
2010-10-27 15:02       ` Jeff Horn
2010-10-27 18:41         ` Marvin Doyley
2010-10-28  7:21           ` Eric S Fraga
2010-10-28  8:37             ` [WISH] Org Importers Jambunathan K
2010-10-28  9:15               ` Scot Becker
2010-10-28 10:16                 ` Peter Frings [this message]
2010-10-28 17:23                   ` Eric S Fraga
2010-10-28 10:15               ` Eric S Fraga
2010-10-28 11:33                 ` Jambunathan K
2010-10-28 11:38                   ` Eric S Fraga
2010-10-29  0:00               ` Matt Lundin
2010-10-29  2:18                 ` Jeff Horn
2010-10-29 17:06                   ` Matt Lundin
2010-10-29 10:17                 ` Eric S Fraga
2011-02-02 22:35                 ` Bastien
2010-10-29  0:23 ` General question on dealing with Latex to word conversion Matt Lundin
2010-10-30 11:18   ` Marvin Doyley
2010-10-30 11:53     ` Jambunathan K
2010-10-30 11:45   ` Marvin Doyley
2010-11-01  0:30     ` Matt Lundin

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=5CC72533-4B9C-429C-B042-A2F970C24F5C@agfa.com \
    --to=peter.frings@agfa.com \
    --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).