From: Bastien <email@example.com>
To: Marcelo de Moraes Serpa <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: org-wikinodes - is there a limit of processable files/nodes
Date: Sat, 22 Sep 2012 18:35:48 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CACHMzOECD8hJkc6RRhMACe68dkG5W1Uh03DVUY9seCt8ZT0EFA@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Sat, 22 Sep 2012 09:19:22 -0500")
Marcelo de Moraes Serpa <email@example.com> writes:
> How can I have a wikilink in a headline?
I think you cannot, as the goal of a wikilink is to jump to a headline.
> When I write a CamelCased
> link in an org headline, it doesn't get converted to a link
> automatically, probably because headlines are the nodes and that
> might cause a deadlock loop?
> Is there a way to force a wikilink (to
> another wikinode) in a headline? (I've tried enclosing in [] but it
> doesn't seem to create a wikinode link, only a regular org link).
I don't know if Carsten is using org-wikinodes.el (?) but I'm pretty
sure you can start hacking it. A nice playground for discovering both
lisp and Org!
> Also, a suggestion: I think an additional value for the scope setting
> could be created called "list of directories", where you could force
> a specific directory(ies) where you keep your wiki org files. Right
> now, I'm doing that by modifying the function as I stated in the
> previous message. I might do that if I have the time, but I fear
> breaking something else, as my elisp skills are still quite basic.
A nice little feature to add, it should not be difficult.
Let us know how it goes!
prev parent reply other threads:[~2012-09-22 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 22:54 org-wikinodes - is there a limit of processable files/nodes Marcelo de Moraes Serpa
2012-09-21 8:44 ` Bastien
2012-09-21 16:58 ` Marcelo de Moraes Serpa
2012-09-22 7:21 ` Bastien
2012-09-22 14:19 ` Marcelo de Moraes Serpa
2012-09-22 16:35 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).