From: Carsten Dominik <dominik@science.uva.nl>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Any performance loss with radio targets?
Date: Wed, 10 Dec 2008 23:46:49 +0100 [thread overview]
Message-ID: <59B10B5A-AF4D-4085-9846-0C19EE1D272B@uva.nl> (raw)
In-Reply-To: <87myf3kbvz.fsf@fastmail.fm>
Hi Matt,
Hundreds or thousands of radio links would be disastrous, direct links
will work fine.
- Carsten
On Dec 10, 2008, at 9:34 PM, Matthew Lundin wrote:
>
> Hello everyone,
>
> I very much like the convenience of radio targets but was wondering
> whether an inordinate number of radio targets/links can slow down
> org-mode as it opens files.
>
> I'd like to use internal links to connect notes with their sources.
>
> For instance:
>
> ----
>
> * Auther, Title, Year.
> <<<AuthorYear>>>
>
> [...]
>
> * Note
>
> "Here is a quote."
> AuthorYear
>
> ----
>
> If I plan on having hundreds such links in a file (and perhaps
> thousands in all my org files), would there be any performance gained
> by using explicit internal links instead of the radio targets? I.e.,
>
> <<AuthorYear>>
>
> [[AuthorYear]]
>
> I'm assuming the difference would be minimal but would like to confirm
> this before committing to the first method. Needless to say, it would
> be easier to convert the second type of links to the first with
> search/replace than the first to the second.
>
> Thanks,
>
> Matt
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2008-12-10 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 20:34 Any performance loss with radio targets? Matthew Lundin
2008-12-10 22:46 ` Carsten Dominik [this message]
2008-12-11 12:44 ` Matthew 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59B10B5A-AF4D-4085-9846-0C19EE1D272B@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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.