Re: Info disaster?
Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
Hrvoje Niksic <hniksic(a)iskon.hr> writes:
> > For me the scanning takes a few seconds and surely is worth it.
>
> "A few seconds" is a long time when it repeats all the time.
But it is only once per XEmacs session,
I'm sorry to be a spoil-sport, but no it's not. I get it repeatedly.
The best way to repeat it is by going somewhere deep into Info
hierarchy, and then press `u' repeatedly to return to `dir'. For
some reason, in some cases the top-level dir used to be forgotten and
regenerated.
> it very annoying. (And I also wonder about the memory
footprint,
> but I'm repeating myself here.)
We give the memory of destroyed buffers back don't we?
Only in some cases, when compiling with relocating allocator.
> > Ad 2. I would say this falls under the "Don't do
that then" category.
> > Just make sure your dirfiles are complete.
>
> How do I do that?
Don't use unstable versions of distributions (although I need to see
whether the transition is complete enough, come potato release
time).
You have got to be kidding. Slink is older than bible, and the
versions of some crucial packages are too old to be even useful.
> > Ad 3. Seems like a good idea. Something for under
~/.xemacs?
>
> What's ~/.xemacs?
A convenient directory for XEmacs to write stuff too, such as
precomputed help tables of contents.
I thought the idea was that such a directory was strictly optional.
I, for one, don't have one.