From: Michael Gilbert <mcg@gilbert.org>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: camel.el, for CamelCase links
Date: Wed, 4 Aug 2010 15:28:09 -0700 [thread overview]
Message-ID: <59E9801E-4A60-47A9-B374-0D4492729F70@gilbert.org> (raw)
In-Reply-To: <87sk2v3blh.fsf@gnu.org>
On Aug 3,2010, at 9:27 AM, Bastien wrote:
> "David O'Toole" <dto1138@gmail.com> writes:
>
>> http://github.com/dto/folio/blob/master/camel.el
>> Someone asked about this recently, i have some partially working code.
>
> I'm not a big fan of CamelCase links because it encourages the habit of
> creating many files -- but that may be useful for some.
I'm on the fence about that one. I would definitely love an easier way to create remote files and headings. This might help with the file end of that.
A question for people people on the list: I'm not sure of the conventions with CamelCase and wikis (and a quick search didn't reveal the answer), but I'm wondering what might work to complete the model — that is to say include creation of remote headings as well as remote files. For example, perhaps using the # sign convention, we would write 'CamelCase#usage' and the first part would act as has been described. The second part (after the # sign) would reference a (top level?) heading in that file. If the heading existed, then great. If not, then it's created as part of the same trigger.
Perhaps this is all old hat, but I couldn't dig up answers for myself, so I thought I would run it by you all.
— Michael
next prev parent reply other threads:[~2010-08-04 22:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:36 camel.el, for CamelCase links David O'Toole
2010-08-03 16:27 ` Bastien
2010-08-04 20:50 ` Olivier Berger
2010-08-04 22:28 ` Michael Gilbert [this message]
2010-08-05 5:36 ` Olivier Berger
2010-08-05 10:02 ` Sebastian Rose
2010-08-06 9:06 ` Syntax to trigger org-capture (Re: camel.el, for CamelCase links) Bastien
2010-08-07 6:31 ` Carsten Dominik
2010-08-07 6:47 ` camel.el, for CamelCase links Carsten Dominik
2010-09-13 17:45 ` Marcelo de Moraes Serpa
2010-09-15 18:56 ` Marcelo de Moraes Serpa
2010-09-19 21:40 ` Bastien
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=59E9801E-4A60-47A9-B374-0D4492729F70@gilbert.org \
--to=mcg@gilbert.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 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).