Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
04-22-2009, 10:29 AM
|
#1
|
|
LQ Newbie
Registered: Apr 2009
Posts: 5
Rep:
|
vim: K (iskeyword) doesn't work in Slackware 12.2
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?
|
|
|
|
04-22-2009, 11:12 AM
|
#2
|
|
LQ Veteran
Registered: Sep 2003
Location: the Netherlands
Distribution: lfs, debian, rhel
Posts: 8,713
|
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.
|
|
|
|
04-22-2009, 01:39 PM
|
#3
|
|
LQ Newbie
Registered: Apr 2009
Posts: 5
Original Poster
Rep:
|
Quote:
Originally Posted by 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)?
|
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!
|
|
|
|
06-29-2009, 01:28 PM
|
#4
|
|
LQ Newbie
Registered: Apr 2009
Posts: 5
Original Poster
Rep:
|
bump
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!
|
|
|
|
06-29-2009, 02:37 PM
|
#5
|
|
LQ Newbie
Registered: Jun 2009
Posts: 9
Rep:
|
This was a bug in vim that has been fixed with patch 7.2.026 and should work in Slackware 13.
|
|
|
|
06-29-2009, 04:13 PM
|
#6
|
|
Senior Member
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
|
This is fixed in Slackware current so yes it will work in Slackware 13.
|
|
|
|
06-29-2009, 07:26 PM
|
#7
|
|
LQ Newbie
Registered: Apr 2009
Posts: 5
Original Poster
Rep:
|
Quote:
Originally Posted by bgeddy
This is fixed in Slackware current so yes it will work in Slackware 13.
|
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?
|
|
|
|
06-29-2009, 07:46 PM
|
#8
|
|
Senior Member
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
|
Quote:
|
Will the fix be be backported to Slackware 12.2, or do I need to rebuild vim myself?
|
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.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:02 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|