bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#13160: 24.3.50; [PATCH] man page completion support beyond man-db


From: Wolfgang Jenkner
Subject: bug#13160: 24.3.50; [PATCH] man page completion support beyond man-db
Date: Sat, 22 Dec 2012 18:58:43 +0100
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (berkeley-unix)

On Sat, Dec 22 2012, Stefan Monnier wrote:

> I don't consciously avoid it, but I just never hit TAB to complete
> a manpage name without first typing a few chars.  I doubt I'm the
> only one.
>
> On  my system "make -k ^" returns about 9K commands of average length
> 14chars, so that's about 9K * (16B (chars) + 16B (string object) + 2*8B
> (cons cells)) or more than 400KB (on a 32bit system) or 700KB (on
> a 64bit system) for that cache.  I'm not sure it's such a good idea.

Worrying about this is the main reason why I posted this, but:

On an old system with not much memory you probably won't have much room
for man pages either (unless you mount a NFS share).  I actually tested
this with a slax image under qemu emulating a i486 system with 64M
(without hardware supported virtualization) and I saw no problem with
it.  Of course, qemu can't really emulate processor or memory-access
speed, I think, and there were only 1000 man entries or so.  I'd love to
test this on my old thinkpad 350 with 20M, but it's difficult to install
a recent emacs on a 120M hard disk ;-)

That said, my main system is reasonable 2009 vintage, has

man -k ^ | wc -l
    8702

(with the actual entries being roughly the double of that)
and the delay is not noticeably longer when caching all entries at the
first completion attempt instead of just part of them.

> Does it fix an actual bug? [ Sorry if it does fix a real bug and this
> was mentioned somewhere in this thread, but I haven't found the time to
> read all threads as thoroughly as I'd like.  ]

My proposed change log entry indicates that the cache handling is rather
bogus (complete for "foo" then for "bar" and then for "foo" again and
"man -k ^foo" will be run again and the result prepended to the cache).

The main reason, however, is that it eliminates any dependency on the
particular flavour of `man -k' output, so everything can be done in
elisp by the new Man-parse-apropos (I indicated that in the change log
entry, too).

Wolfgang





reply via email to

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