Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#2003 closed task (fixed)

Vim 7.0

Reported by: Ag Hatzimanikas Owned by: bdubbs@…
Priority: high Milestone: 6.2.0
Component: BOOK Version: SVN
Severity: blocker Keywords:


Version increment.

Major new features and as usual very stable release. Saying that there are 17 patches (which updates vim to patchlevel-17) to cover different issues which at the major part doesn't prevent vim from building in most of the cases.

LFS already updated to the new version.

So I will suggest to have a look first to the LFS ticket.

The two needed patches are already in the repo and they can be used as it is from BLFS.

Attachments (1)

vim-update.diff (6.9 KB ) - added by Ag. Hatzimanikas 17 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Randy McMurchy, 18 years ago

Priority: normalhigh
Severity: normalblocker

by Ag. Hatzimanikas, 17 years ago

Attachment: vim-update.diff added

comment:2 by Ag. Hatzimanikas, 17 years ago

This is a miserable attempt to upgrade vim,thanks to a call for help by Dan Nicholson:

So bear with me as this is my first try to create a diff for the Book.

Obviously there are some human errors of all kind in there,so please review first and most probably fix some things before applying the diff.

Some explanations. I am patching vim to reach in the patchlevel 150,because indeed there are things that have to be fixed in the vim initial version. I am also using bzcat to apply the patch because of it's size. Uncompressed patch is almost 670 Kilobytes,while the compessed is 140.

The documentation symbolic link I think is required because of a probably existing symlink created earlier by LFS. The construct however can be changed with an if/fi statement,although I guess the current is also compatible with bash/zsh (I am not sure for ksh).

I also added some more option in the command explanations to include the various interpreters.Again this can be changed if desired.

I also added a note about the spell checker although to be honest my initial intention is to give to the user the chance to see the new features of the 7.0 version.But there is no such section in the BLFS pages for something like: "What's is new in this release and why you have to upgrade"

I didn't touch the changelog,this is I think a work that has to be done from the commiter.

Probably there many mistakes regarding various tags.I see also it as a chance to see by first hand their usage and learn.

I will email the patch to the patches mailing list,so someone I guess can pick it up from there.

Unfortunately I will not have time today to participate in the ticket.

You are free to move on and update to the new version because is a serious mismatch between LFS and BLFS.

comment:3 by bdubbs@…, 17 years ago

Owner: changed from blfs-book@… to bdubbs@…

comment:4 by bdubbs@…, 17 years ago

Resolution: fixed
Status: newclosed

Fixed at revision 6387.

Since there were several changes since Ag submitted his patch, I couldn't use it, but it is much appreciated.

comment:5 by Ag. Hatzimanikas, 17 years ago

Many thanks Bruce for the update,although to be honest I would like to see into the book the part about the various interpreters.

Look at it in this way. Why someone has to rebuild vim after LFS?

a) X

1.gui. 2.X11 selection. 3.Various other reasons,like scripts that are designed (or work better) for the gui,like the tohtml script.

b) Building against the various scripting languages (python,ruby,tcl) which wasn't present in the first build. The problem with this,is that you have to enable the various interpreters *manually*,because vim wisely it doesn't link against these languages no matter if they are present or not. So I believe that is something,that is worth mentioning in the instructions.

Your call.

Note: See TracTickets for help on using tickets.