From: Carsten Dominik <carsten.dominik@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: OrgmodeWiki Support
Date: Fri, 18 Dec 2009 16:59:22 +0100 [thread overview]
Message-ID: <B0021057-F22D-47F7-9262-A02076A54792@gmail.com> (raw)
In-Reply-To: <20091218141926.GA23267@atlantic.linksys.moosehall>
On Dec 18, 2009, at 3:19 PM, Adam Spiers wrote:
> On Fri, Dec 18, 2009 at 01:15:59PM +0100, Carsten Dominik wrote:
>> On Dec 18, 2009, at 12:28 PM, Adam Spiers wrote:
>>> I would *love* to see auto-linking of WikiWords as a customisable
>>> option. I'm not sure if anyone's looked at supporting WikiWords
>>> yet.
>>
>> Where should the link go? To a file WikiWord.org? Or doing an
>> etags search?
>
> To a file WikiWord.org would cater for the majority of my needs.
> Would be even cooler if you could specify a list of directories as a
> search path, where each directory was either absolute or relative to
> the current file!
>
> Maybe others could make use of an etags option too; I'm not sure. I
> guess you might then need a custom function to translate the WikiWord
> into a tag to lookup, since a lot of tags are not CamelCase.
I think it would be useful to discuss this proposal first in a broader
sense.
Let me try to make a start.
A few days ago, Paul Sexton submitted his proposal for simple
file-to-file links based on etags.
He wanted to make [[sometext]] be a link to <<sometext>> where
the target definition <<sometext>> can be in a different file.
Furthermore, his proposal uses an external program to do the
indexing of the tags, and following the links uses the etags
code shipped with Emacs.
Finally, Paul's proposal also contains a way to automatically
create new topics when a link is called that does not yet have
a target.
Now we are talking about WikiWords, or CamelCase links. Here the
idea is that any such mixed-case word automatically is treated as a
link.
Traditionally these links to a separate file with name given by the
link text directly. But I suppose it could also got to a <<target>>
somewhere in a file?
For a couple of reasons it seems to me that it would be useful
to look at these proposals together. For one thing, I am not
a huge fan of the zillions of files that will be created when using
the one-file-per-word approach. Since Org-mode is outline based, it
seem to make a lot of sense to have many topics per file.
One way to move into this direction would be to still use etags
to index the possible targets, and then to turn specific words
(like CamelCase words) directly into links without the need to
surround them with [[...]].
But of course, we could also have an implementation as Adam
proposes it, with CamelCase words linking to files, and
then [[target]] linking to targets.
Can we discuss this for a bit?
- Carsten
next prev parent reply other threads:[~2009-12-18 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 22:23 Wiki Support Marc
2009-12-09 17:38 ` OrgmodeWiki Support Wes Hardaker
2009-12-18 11:28 ` Adam Spiers
2009-12-18 12:15 ` Carsten Dominik
2009-12-18 14:19 ` Adam Spiers
2009-12-18 15:59 ` Carsten Dominik [this message]
2009-12-18 20:35 ` Paul Sexton
2009-12-24 8:01 ` Carsten Dominik
2009-12-20 15:48 ` Darlan Cavalcante Moreira
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=B0021057-F22D-47F7-9262-A02076A54792@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.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).