< :the previous in number
^ :the list in numerical order
> :the next in number
P :the previous (in thread)
N :the next (in thread)
|<:the top of this thread
>|:the next thread
^ :the parent (reply-to)
_:the child (an article replying to this)
>:the elder article having the same parent
<:the youger article having the same parent
---:split window and show thread lists
| :split window (vertically) and show thread lists
~ :close the thread frame
.:the index
..:the index of indices
Joel VanderWerf wrote:
>David Corbin wrote:
>
>
>>I've looked through the RAA, but nothing jumped out at me. Google led
>>me to pstore (standard with ruby), but documentation seems to be
>>extremely scare on that.
>>
>>
>
>PStore is fine for what it does, and it's documented in the Pick Axe:
>
> http://www.rubycentral.com/book/lib_standard.html
>
>But it reads and writes the whole file for any transaction, which may
>not be what you want...
>
>
You're right, that's not what I want. What I really want, now that I
thiink about it, is for objects to be loaded "on-demand", and for dirty
objects to be periodically "flushed to disk". I probably need to give
this some more thought, and I'll probably end up simply doing a SQL
database, or XML.