emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Florian Beck <abstraktion@t-online.de>
To: emacs-orgmode@gnu.org
Subject: Using org-mode for Research and Notetaking
Date: Mon, 11 Jul 2011 21:55:23 +0200	[thread overview]
Message-ID: <87zkkktwwk.fsf_-_@sophokles.streitblatt.de> (raw)
In-Reply-To: <87liw582jg.fsf@gnu.org> (Bastien's message of "Mon, 11 Jul 2011 13:44:35 +0200")

[My main goal is to take research notes and write texts. I have little
interest in the todo/agenda part of org-mode, which I understand is its
main focus, so bear this in mind.]

Previously I have been using muse-mode for publishing and a home brew
system for organising my notes. Now I thought, I would give org-mode a
try. I had some 3500 short notes which I converted into a 8.5M org-file
with said 3500 heavily tagged entries. Also created a 500k org file from
my bibtex file. These two plus a couple of shorter files are my

Speed is quite ok, surprisingly. `org-columns' in the big file is a
no-go, of course (overlays!). The agenda commands work fine (I have few
entries with todo-keywords, but they are in every file.)

So far so good. Tables, integration of latex fragments: great stuff. I
like the outlining capabilities but used most of them via
`org-struct-mode' already. Especially impressed with babel. Wow!

A couple of questions and observations, first impressions really:

 1. Publishing (I have only tested pdf) works pretty well. Obviously, or
 so I would have thought, I don't want to see todo-keywords and TAGs in
 the output. How do I get rid of them?

 2. Tags are SLOW (no doubt due to my 8.5M file). Completion takes
 minutes. I fixed that by adding all my (hundreds of) tags to
 `org-tag-alist' and restricting capture to »%g«, checking only the
 current file. `org-id-find' is slow as well and so will be property
 completions, I guess. How about caching the data and update on saving
 an org-agenda file?

 3. By default, tags cannot contain spaces or commas. I rectified that
 with an ugly hack in `org-set-tags-to', which replaces spaces with
 ?\x2008 (punctuation space), and setting it to word syntax. Also, many
 long tags display ugly. How about showing only the first twenty
 characters and show the rest via help echo?

 4. muse-mode has this nice feature that it easily allows you to define
 your own <tags> like
 <i-am-learning-kanji-so-better-display-this-big>…</…> or
 <a-citation-the-way-i-like-it>…</…>; not only for export but also for
 fontification. Can I do something similar in org-mode?

 5. According to the manual »TODO items are an integral part of the
 notes file«. I like that, but I do not find it so. TODO items are
 headings which I find somewhat confusing: My files are either articles
 to be (with the appropriate headlines) or notes where headlines usually
 formulate the topic the note is about. Todo items, on the other hand,
 would be »clarify the paragraph«, »check what X says about Y«, »add
 more sources«, etc. As it is TODOs are not integrated but stand out,
 breaking the structure of the file. How about allowing TODO items in
 comments? This would seem much more natural to me: a TODO item should
 not be part of your text but disappear when it is done.

Florian Beck

  reply	other threads:[~2011-07-11 19:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10 11:09 RFC: Revisit org-export-content-div (in the context of org-s5) Jambunathan K
2011-07-10 11:28 ` Jambunathan K
2011-07-11 11:44   ` Bastien
2011-07-11 19:55     ` Florian Beck [this message]
2011-07-12 14:23       ` Using org-mode for Research and Notetaking John Hendy
2011-07-14 18:09         ` Florian Beck
2011-07-12 14:28       ` Giovanni Ridolfi
2011-07-13  8:55       ` Bastien
2011-07-13  9:59         ` Sebastien Vauban
2011-07-13 11:20           ` Bastien
2011-07-13 12:20             ` Sebastien Vauban
2011-07-13 13:43             ` Nicolas Goaziou
2011-07-16 11:40               ` Bastien
2011-07-18 12:42             ` Matt Lundin
2011-07-18 13:21               ` Sebastien Vauban
2011-07-18 14:53                 ` Matt Lundin
2011-07-18 14:03               ` Sebastien Vauban
2011-07-18 14:58                 ` Bastien
2011-07-14 18:40         ` Florian Beck
2011-07-14 18:59           ` Thomas S. Dye
2011-07-18 22:54           ` Bastien
2011-07-18 23:59             ` Thomas S. Dye
2011-07-19  1:34               ` Florian Beck
2011-07-26 11:27               ` Bastien
2011-07-26 14:17                 ` Florian Beck
2011-07-26 15:15                 ` Thomas S. Dye
2011-07-26 17:41                   ` Christian Moe
2011-07-11 11:44 ` RFC: Revisit org-export-content-div (in the context of org-s5) 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:

  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=87zkkktwwk.fsf_-_@sophokles.streitblatt.de \
    --to=abstraktion@t-online.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).