A.J.Mechelynck wrote:
mwoehlke wrote:
Well, that was exciting... I recently tried to build vim 7 on OSS
(Tandem / HP Nonstop S-Series). I finally got it to work by diff'ing
the ITUG Floss sources (link below) against vim-6.1 and applying the
diffs to vim-7.0 (and by first building/installing ncurses-5.5). I
would like to submit my efforts to be included upstream. Are there any
objections if I post the .patch here?
This is the ITUG vim:
https://www.itug.org/secure/ituglib/shared/act_download.cfm/vim.tar.Z?lib_file_id=666
NOTE: I also had to configure ncurses and vim as follows:
ncurses5-5$ CFLAGS=-WIEEE_float ./configure
vim-7.0$ LDFLAGS=-lfloss CFLAGS=-WIEEE_float ./configure
(I am not sure if 'floss' is necessary, but it was used in ITUG vim61.)
Well, IMHO you ought to send them to Bram < [EMAIL PROTECTED] >,
preferably in the form of context or unified diffs against the most
recent sources (i.e., 7.0 as seen after applying the 39 "official"
patches already published). If your patches are bulky, they might
perhaps not be worth publishing on the list; but that's only my private
opinion.
Well, I'll hope for a reply from Bram. I'm used to projects that don't
appreciate people shooting e-mail off to any particular individual when
there is a designated list/forum. :-)
So nice to have the keys behave, though. :-)
(While we're on the subject, can someone remind me how to *make* a
.patch? Is it just 'diff -u' or is there something special in getting
the multiple-files-in-one-output-block right?)
--
Matthew
Now where did I put my hippo?
