Re: Info disaster?

Hrvoje Niksic <hniksic(a)iskon.hr&gt; writes: Depends on your definition of "just fine". In the pre-autobuilding case it just didn't find all the info files. See below.. That just uses "pick the first dir file we see and assume it is correct". The problem with that is that this assumption is typically incorrect. Dirfiles are rarely well maintained. Modern Linux distributions are improving this a lot (thanks to install-info). In fact Debian was one of the first to do so. You just are caught in the middle of their /usr/share/info transition. The autobuilding is a solution to a real problem (I love finally seeing all the info files in info browser), so just switching it off is a non-option in my view. Important note: If your dirfiles are up to date, their will be no scanning[1]. For me the scanning takes a few seconds and surely is worth it. You have three more or less independent issues 1. Scannings gives some meaningless errors in the minibuffer. 2. In pathological cases, i.e. grossly out of date dirfiles and compresses info files it can take a long time. 3. There needs to be a way to save the results for those without write access. Ad 1. Must be fixable by improving the elisp. Ad 2. I would say this falls under the "Don't do that then" category. Just make sure your dirfiles are complete. maybe it could be helped some by not uncompressing and inserting the complete file but just the header to search for the direntry. Ad 3. Seems like a good idea. Something for under ~/.xemacs? Footnotes: [1] Note that this will never completely be the case because of the package system.