From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darlan Cavalcante Moreira Subject: Re: Re: OrgmodeWiki Support Date: Sun, 20 Dec 2009 12:48:58 -0300 Message-ID: <4b2e4776.c501be0a.3822.0a34@mx.google.com> References: <200912062323.35140.liste@barisch.com> <20091218112849.GH5666@atlantic.linksys.moosehall> <6AB8487A-888D-440D-8A8E-C0BB63050F2C@gmail.com> <20091218141926.GA23267@atlantic.linksys.moosehall> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMO22-00087Y-SK for emacs-orgmode@gnu.org; Sun, 20 Dec 2009 10:49:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMO1x-0007zD-HI for emacs-orgmode@gnu.org; Sun, 20 Dec 2009 10:49:18 -0500 Received: from [199.232.76.173] (port=45273 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMO1x-0007z5-DC for emacs-orgmode@gnu.org; Sun, 20 Dec 2009 10:49:13 -0500 Received: from mail-yx0-f191.google.com ([209.85.210.191]:52576) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMO1w-0002W9-TY for emacs-orgmode@gnu.org; Sun, 20 Dec 2009 10:49:13 -0500 Received: by yxe29 with SMTP id 29so12706587yxe.14 for ; Sun, 20 Dec 2009 07:49:11 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org 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 | <> `---- 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 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 <> where > the target definition <> 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 <> > 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