[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Using org-mode for Research and Notetaking

From: Thomas S. Dye
Subject: Re: [O] Using org-mode for Research and Notetaking
Date: Thu, 14 Jul 2011 08:59:47 -1000

Florian Beck <address@hidden> writes:

> Bastien <address@hidden> writes:
>>>  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?
>> We might consider this.  
>> I doubt updating on saving is the right thing to do -- people tend to
>> save very often, and for solving problems like yours, it will be as slow
>> as the current interface.
>> We need to be more clever in defining the update cycle for caches, and
>> this depends on _what_ the cache is containing.
> I agree, updating on saving would not work for large files. Maybe you
> could use a cache on a per file basis, creating it when org first
> happens to collect the data and updating it on demand. Of course, it
> might be out of date, which in my case would be no problem.
>> You will need to live with it for now.
>>>  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?
>> What do you mean?
>> What I can think of are "tag aliases": for example, the tag ":code:"
>> would be an alias for ":code python lisp:".
>> The buffer would display the alias.
>> Tag search would match the expanded version.
>> This adds a semantic layer for tags, so maybe there are complexities
>> I cannot think of right now, but I think it might be interesting.
>> What do you think?
> Actually, I meant »tags« in the HTML sense. For <boxed>example</boxed>
> would call a function during export, which returns, say, its LaTeX
> interpretation, another function would be called by font lock (or
> whatever you use) to determine its on screen display. That is, the user
> has to provide two functions and org mode has to call them at the
> appropriate place.

Aloha Florian,

This is partially implemented with Org-mode's link syntax.  See
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-3 for
an example that defines LaTeX and HTML exports for arbitrary tags.

AFAIK, the link syntax lacks an easy way to change the function for
screen display, but this would be a useful addition to Org-mode.  Then,
it would be a relatively simple matter to provide functions that
differentiate on-screen between links used for different purposes.

There was a discussion along these lines on list some time ago under the
heading "text color + highlight".


>>>  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.
>> As suggested, you want to check inline tasks.
> I'll look into it. Thanks for your comments!
>> I really don't like the current syntax for inline tasks, I would much
>> prefer something like special TODO keywords:
>> * !TODO This would be an inline task, not a headline
>> But perhaps I'm missing something about why the current inline task
>> syntax is useful.  I'd be interested in hearing more by people who are
>> actually using them...
>> Thanks for your input!

Thomas S. Dye

reply via email to

[Prev in Thread] Current Thread [Next in Thread]