From: Bernt Hansen <bernt@norang.ca>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [OT] How do you keep your reference data?
Date: Mon, 09 Nov 2009 11:13:13 -0500 [thread overview]
Message-ID: <87zl6v8yna.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <1e5bcefd0911090808h4d545be9x3d56131ef826092@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Mon\, 9 Nov 2009 10\:08\:13 -0600")
Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> I liked your self-contained approach, and I will try implementing it
> in my workflow. Org does not stop amazing me on how flexible it is :)
>
> However, the value of having a wiki is also great IMO. It has a
> workflow similar to tomboy (each new org file acts as a new tomboy
> note) I don't have to think too much when creating a wiki page (just
> type TheNameOfTheSubject.org, save it and begin typing, they are in a
> central location (a wiki folder) and they are a great place to
> register knowledge data.
>
> I don't know, that might be because I used WikiDPad for a long time on
> my Windows days and loved its approach (Two things that org lacks as a
> wiki-system, which is a way to view the wiki in a tree format and
> automatically create links based on files in the filesystem or
> camelcase. Not big deal features, but something that could be
> contributed as a org extension - I would do it if I had the elisp
> knowledge to do so :))
I used to use a wiki ... but I personally prefer the org->HTML export
sequence to a wiki. All of my documents are available in org-mode
source.
I don't have the need to have multiple users edit the same source (which
is the whole point of a wiki IMO). Wiki's have other issues if they are
world editable - like spam bots and other things which I just didn't
want to deal with.
I found the org-mode format with export at least as powerful as the
wiki's I've used. If you community of people working on the same
content where some of them don't use org-mode then a wiki probably makes
sense.
I just don't need it for my workflow.
-Bernt
next prev parent reply other threads:[~2009-11-09 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 22:24 [OT] How do you keep your reference data? Marcelo de Moraes Serpa
2009-11-09 12:54 ` jemarch
2009-11-09 14:09 ` Bernt Hansen
2009-11-09 16:08 ` Marcelo de Moraes Serpa
2009-11-09 16:10 ` Marcelo de Moraes Serpa
2009-11-09 16:13 ` Bernt Hansen [this message]
2009-11-09 16:50 ` Marcelo de Moraes Serpa
2009-11-09 16:51 ` Marcelo de Moraes Serpa
2009-11-25 16:15 ` tycho garen
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=87zl6v8yna.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=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).