emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: OrgmodeWiki Support
Date: Sun, 20 Dec 2009 12:48:58 -0300	[thread overview]
Message-ID: <4b2e4776.c501be0a.3822.0a34@mx.google.com> (raw)
In-Reply-To: <B0021057-F22D-47F7-9262-A02076A54792@gmail.com>


One of the main reasons that made me move from planner to org after using
planner mode for more than one year is exactly the "one file per day" approach
that is used by planner. Don't get me wrong, planner-mode is very good but I
think that the powerful outline capabilities of org-mode works better with my
brain than several files.

Today I use a remember template for notes that asks me for a title and puts the
note in a notes.org file. Maybe a good approach for camel case words for
org-mode could be similar to this.

Suppose that camel case support is active in org-mode and the user tries to
visit the link CamelCaseWord which does not exist yet. Org-mode could then
create a headline in a wiki.org file like this
,----
| * CamelCaseWord
| <<CamelCaseWord>>
`----
and visit that file.

This would allow the user to change the title if desired and the link would
still be valid even from other files (using the proposed etags functionality).

At last, in order to tell org-mode in which file (in this case wiki.org) and in
which section the new headlines should be created the user could define a
template similar to the remember templates (maybe it is even possible to use
remember-mode for this with the already available functionality).

- Darlan Cavalcante Moreira


At Fri, 18 Dec 2009 16:59:22 +0100,
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> 
> 
> 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
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      parent reply	other threads:[~2009-12-20 15:49 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
2009-12-18 20:35           ` Paul Sexton
2009-12-24  8:01             ` Carsten Dominik
2009-12-20 15:48           ` Darlan Cavalcante Moreira [this message]

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=4b2e4776.c501be0a.3822.0a34@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --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).