From: Phil Jackson <phil@shellarchive.co.uk>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Announcing Worg (Web-Org)
Date: Wed, 16 Jan 2008 15:12:11 +0000 [thread overview]
Message-ID: <873asxiz3o.fsf@shellarchive.co.uk> (raw)
In-Reply-To: <64bfe3d50801160636q6fed26bcg173f5a64844edddb@mail.gmail.com> (David O'Toole's message of "Wed\, 16 Jan 2008 09\:36\:57 -0500")
"David O'Toole" <dto@gnu.org> writes:
>> Happy to swap/lend/steal/merge anything you think we should or we
>> could go into a bitter competition involving spies, bribery and
>> litigation.
> http://dto.mamalala.org/eon/radio.el
>
> I haven't worked on it in a little while, as I've been hacking on Eon
> and org-publish.el. But, some people may find it of interest. I do
> intend to use it for audio, because it allows you to annotate binaries
> as well (by making a separate little note file.)
It's amazing how similar they are. An important difference, for me, is
that org-annotate-file doesn't modify its target file (my fellow team
members wouldn't be happy with me putting UUIDs in our code base
:)). Having said that org-annotate-file uses the 'file:name::search'
syntax which means potentially matching the wrong line if there are
identical ones.
Swings and roundabouts I suppose.
Cheers,
Phil
--
Phil Jackson
http://www.shellarchive.co.uk
next prev parent reply other threads:[~2008-01-16 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 7:49 Announcing Worg (Web-Org) Bastien
[not found] ` <87r6guar14.fsf@shellarchive.co.uk>
2008-01-07 10:31 ` Bastien
2008-01-08 0:18 ` cezar
2008-01-13 16:09 ` David O'Toole
2008-01-14 11:47 ` Piotr Zielinski
2008-01-16 2:03 ` Bastien
2008-01-16 9:48 ` Phil Jackson
2008-01-16 14:36 ` David O'Toole
2008-01-16 14:48 ` David O'Toole
2008-01-16 15:12 ` Phil Jackson [this message]
2017-08-07 11:17 ` Nicolas Goaziou
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=873asxiz3o.fsf@shellarchive.co.uk \
--to=phil@shellarchive.co.uk \
--cc=dto@gnu.org \
--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 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.