Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]
On Fri, 2007-05-18 at 07:21 +0200, Stephan Hegel wrote: ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*' fetches all patches to the local directory in one go. And it does it in a smart way, see the second try: ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*' ncftpget /pub/editors/vim/patches/7.1/7.1.*: local file appears to be the same as the remote file, download is not necessary. Hi, A lot of the readers here als prefer lftp as good choice for ftp'ing. Your two lines of getting the patches is indeed nice. Can also be done with wget only. Please allow me to remind the people here on the getvim script that I once wrote. It collect all patches and made one huge patchfile out of it. Quite trivial to use. http://www.akcaagac.com/tools/files/shell/getvim.sh Greetings, Ali Akcaagac
Re: Cannot print in UTF-8?
On 18/05/2007 03:31, A.J.Mechelynck wrote: :set enc? penc? encoding=utf-8 printencoding=utf-8 :%ha not found in runtimepath: print/utf-8.ps Is this last message normal? Yes. I have here a file including an Esperanto-French glossary, which contains both the consonants+circumflex of Esperanto and the French oe ligature. No matter how I try, Vim cannot print it: - penc=utf-8 gives the above error - penc=latin3 prints Esperanto correctly, but oe becomes an inverted question mark - penc=latin9 prints French correctly but not the Esperanto letters. Compiled with +multi_byte +iconv +printer +postscript Looks like the only way to print that file properly is to load it in my browser. Unicode encoding is only supported for CJK fonts at the moment. Of course, if you had such a font with the glyphs you want, then this will work. TTFN Mike -- The Buck stops here; the Doe just visits.
Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]
Hi, Ali Akcaagac wrote: A lot of the readers here als prefer lftp as good choice for ftp'ing. Well, since I do use ncftp anyway on several platforms I've got ncftpget for free and so the posted approach is perfectly fine for me. I don't speak for others, of course, just trying to show and share a neat solution. Your two lines of getting the patches is indeed nice. It is only one line ;). Similar like your wget approach in getvim.sh: ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*' So my fully-automatic build - this has been my goal - looks now like this (snippet from the Makefile): all: tar xfj vim-7.1.tar.bz2 tar xfz vim-7.1-lang.tar.gz tar xfz vim-7.1-extra.tar.gz (cd vim-7.1.patches ; ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*') cat vim-7.1.patches/7.1.* patchfile (cd vim71 ; patch -p0 ../patchfile) (cd vim71 ; ./configure --prefix=$(PREFIX) --with-x --enable-gui=gtk2 --enable-multibyte --enable-xim --enable-fontset --enable-perlinterp --enable-cscope make) Can also be done with wget only. Please allow me to remind the people here on the getvim script that I once wrote. It collect all patches and made one huge patchfile out of it. Quite trivial to use. Using one huge patchfile is also my approach as you can see above and on Unix/Linux systems this can be done with a simple cat 7.1.* patchfile 'cause the right sorting order is already built-in. If somebody has got another experience with, e.g. different locale settings, I would appreciate to know. As Tony has pointed out already, this doesn't work on Dos / Windows as the sorting order seems to be different there, unfortunately. http://www.akcaagac.com/tools/files/shell/getvim.sh I had a look: interesting and new to me is your approach with seq. I'll remember this when I need a sequence of formatted, ascending numbers in a shell script. But for creating the vim patchfile with all patches included it is overdone, IMO. In this case you even need to edit the script with every new patch (see: $SUBLEVELEND). Plus you still need to apply the patch and build manually. Kind regards, Stephan.
Re: Subject: Re: vim on cygwin using win32 clipboard
On 2007-05-17, Gary Johnson [EMAIL PROTECTED] wrote: On 2007-02-15, Frodak Baksik [EMAIL PROTECTED] wrote: On 2/15/07, Chris Sutcliffe wrote: Also, is there anything I can do to help get the original patch accepted? Ask a few people to try it out and report their results here. I'll give it a shot. Is there somewhere I can grab the patch from, or should I go through the list archives to find it? Here are all the changes in a single patch. I'm also posting this to the cygwin-apps mailing list, so if anyone over there could try it out would be nice. I just applied this patch to the 7.1 source. The patch to proto/os_mswin.pro failed, but it was easy to fix manually. The problem was that the extern prefix has been removed from the 7.1 declarations. Hunk #2 of the patch to os_win32.c failed, apparently because that change was already made to the 7.1 source, so I left that file with only hunk #1 applied. It looks like I goofed when applying the patch that way. I just applied the patch to another system, but edited the patch first to get rid of the failures instead of trying to edit the files afterwards. All I had to do to the proto/winclip.pro section was to remove extern from the start of all the lines. While editing the os_win32.c section, I discovered that 'patch' was missing the first hunk in the target and applying the first hunk of the patch to the second hunk in the target, causing the application of the second hunk of the patch to fail. This was cause by the reformatting of a comment from 7.0 to 7.1. I changed the comment in the patch to match the comment in the 7.1 source and the entire patch applied successfully. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
