From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Simple wiki system like VIMWiki
Date: Thu, 6 Jan 2011 09:07:57 -0600 [thread overview]
Message-ID: <AANLkTi=S=Aw6SSn9Wq1LKA7eejNhkgdMrHL2tMsApM-r@mail.gmail.com> (raw)
Hi list,
I've started using vim lately for my programming needs and I love it,
mostly because the motion and shortcuts are much more efficient. That
aside, I still think emacs is a great platform and text-editor and I
still use it for other stuff, mainly organizing myself (thanks to
orgmode).
Most of the todo/GTD stuff is well handled by org, but I do find that
for reference and brainstorming, a real-time (and straightforward)
wiki is the best solution. I have been managing to keep things simple
by keeping all my reference org files under a (/wiki) folder and
setting peepopen (an OSX cocoa fuzzy-finder
(http://peepcode.com/products/peepopen)) to index specifically this
folder and bound this to Command-w, and it works great for getting a
quick index of the wiki and quickly open a file from it.
However, linking and creating new files is far from optimal. Org-mode
still tries to keep things at the headline-level, instead of at file
level. This works, but for me, not so well. Why? The simple fact that
org asks me if I want to create a target in the current file or in a
another file already gets me out of the zone. I prefer some convetion
over configuration.
It'd be nice if org had, for example, a more org-like wiki (like
wikinodes) and a more traditional one (like VIMwiki). Not sure if
there's another mode I could combo with org that would give the
functionality I want, I'm open to suggestions :)
Marcelo.
next reply other threads:[~2011-01-06 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 15:07 Marcelo de Moraes Serpa [this message]
2011-01-06 16:22 ` Simple wiki system like VIMWiki Marcelo de Moraes Serpa
2011-01-07 15:03 ` Marcelo de Moraes Serpa
2011-01-07 15:37 ` Nick Dokos
2011-01-07 15:44 ` Nick Dokos
2011-01-07 15:32 ` 노정태
2011-01-07 18:38 ` Matt Lundin
2011-01-07 19:24 ` Samuel Wales
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='AANLkTi=S=Aw6SSn9Wq1LKA7eejNhkgdMrHL2tMsApM-r@mail.gmail.com' \
--to=celoserpa@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).