bstern

[Log in to get rid of this advertisement]

I upgraded from 12.1 to 12.2 on one system, and have not yet on another. On the system where I upgraded to 12.2, pressing K in vim while the cursor is on a function name in C source code no longer works properly.

On the 12.1 system, it grabs the function name properly and presents the man page. On a 12.2 system, it grabs from the start of the keyword to the end of line and therefore doesn't give me the right man page.

Example:

Pressing 'K' while the cursor is under the atol in the line

h = atol(argv[1]);

on 12.1 gives me the man page for atol.

On 12.2, man tells me:

No manual entry for atol(argv[1]);

How do I fix this?

druuna

Hi,

The problem is not the K in vi, it works fine and tells you: No manual entry for atol(argv[1]);
It seems that the manpage for atol is not installed, did you install everything that was installed on your previous version (12.1)?

The manpage package should be installed. Check your own medium first before using the link I provided.

Hope this helps.

bstern

Yes, I did install the new version of the manpages. The problem is not that man can't find the page for atol. "man atol" works on the command line.

The problem is that when I type K, vim is trying to get the manpage for "atol(argv[1]);" - which certainly doesn't exist, and shouldn't.

Does anyone know what changed with the Slackware package for vim between 12.1 and 12.2 that made the "inkeyword" function break?

Thanks!

bstern

Does pressing K in vim over a C function name work for anyone in Slackware 12.2?

For example, if you move the cursor over the word "printf" in the attachment, does anyone who is running Slackware 12.2 actually get a man page for printf?

This worked in Slackware 12.1.

Thanks!

Attached Files

argc.c.txt (219 Bytes, 3 views)

sinic

This was a bug in vim that has been fixed with patch 7.2.026 and should work in Slackware 13.

bgeddy

This is fixed in Slackware current so yes it will work in Slackware 13.

bstern

Great news! Thanks for letting me know.

Will the fix be be backported to Slackware 12.2, or do I need to rebuild vim myself?

bgeddy

Well I can't speak for the Slackware team but I think you may be better building it yourself on 12.2. You could just get the sources and Slackbuild from the current version available here and build it on Slackware 12.2 then upgradepkg the newly built package. Either that or wait for Slackware 13. Don't forget that you'll need the patches directory and contents from the sources.