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: crash due to -fstack-protector false positive
On Fri, 2007-02-23 at 19:58 +0300, Alexey I. Froloff wrote: i586-alt-linux-gcc (GCC) 4.1.1 20070105 (ALT Linux, build 4.1.1-alt11) glibc 2.5 (glibc-2_5-branch snapshot 20070112) I think it's the stuff above where you need to look for bugs. GLIBC snapshot sounds unfinished and contains bugs to me. mfg, Ali Akcaagac
Re: patch 7.0.182
Hi Bram,
may you tell us, when you plan to release VIM 7.1 ?
mfg,
Ali Akcaagac
On Tue, 2007-01-09 at 20:30 +0100, Bram Moolenaar wrote:
Patch 7.0.182
Problem:When using a mix of undo and g- it may no longer be possible to
go to every point in the undo tree. (Andy Wokula)
Solution: Correctly update pointers in the undo tree.
Files:src/undo.c
*** ../vim-7.0.181/src/undo.c Tue Aug 29 17:28:56 2006
--- src/undo.cTue Jan 9 20:18:27 2007
***
*** 341,351
uhp-uh_alt_next = old_curhead;
if (old_curhead != NULL)
{
old_curhead-uh_alt_prev = uhp;
if (curbuf-b_u_oldhead == old_curhead)
curbuf-b_u_oldhead = uhp;
}
! uhp-uh_alt_prev = NULL;
if (curbuf-b_u_newhead != NULL)
curbuf-b_u_newhead-uh_prev = uhp;
--- 341,355
uhp-uh_alt_next = old_curhead;
if (old_curhead != NULL)
{
+ uhp-uh_alt_prev = old_curhead-uh_alt_prev;
+ if (uhp-uh_alt_prev != NULL)
+ uhp-uh_alt_prev-uh_alt_next = uhp;
old_curhead-uh_alt_prev = uhp;
if (curbuf-b_u_oldhead == old_curhead)
curbuf-b_u_oldhead = uhp;
}
! else
! uhp-uh_alt_prev = NULL;
if (curbuf-b_u_newhead != NULL)
curbuf-b_u_newhead-uh_prev = uhp;
***
*** 856,861
--- 860,870
uhp = curbuf-b_u_curhead;
while (uhp != NULL)
{
+ /* Go back to the first branch with a mark. */
+ while (uhp-uh_alt_prev != NULL
+ uhp-uh_alt_prev-uh_walk == mark)
+ uhp = uhp-uh_alt_prev;
+
/* Find the last branch with a mark, that's the one. */
last = uhp;
while (last-uh_alt_next != NULL
***
*** 865,870
--- 874,881
{
/* Make the used branch the first entry in the list of
* alternatives to make u and CTRL-R take this branch. */
+ while (uhp-uh_alt_prev != NULL)
+ uhp = uhp-uh_alt_prev;
if (last-uh_alt_next != NULL)
last-uh_alt_next-uh_alt_prev = last-uh_alt_prev;
last-uh_alt_prev-uh_alt_next = last-uh_alt_next;
*** ../vim-7.0.181/src/version.c Tue Jan 9 15:43:39 2007
--- src/version.c Tue Jan 9 20:26:47 2007
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 182,
/**/
Mailinglist down ?
Hello, anyone happen to know what happened to the VIM Devel Mailinglist ? I am not receiving anything since last wednesday. mfg, Ali Akcaagac
Re: Mailinglist down ?
On Sat, 2006-10-28 at 16:04 +0200, A.J.Mechelynck wrote: I got your mail on the vim-dev list so it isn't down. I also see a mail by ... Nah it seems to be ok now.. I was a bit worried for the moment.. Thanks for feedback.. mfg, Ali Akcaagac
Re: Fwd: Do Not Reply To This Message:Re: Time to remove naming restrictions?
Hello, I received feedback from them today and they said that they recently had a lot of issues with bouncing back and that they finally solved this issue. We therefore should not receive anything from them anymore. greetings, Ali Akcaagac On Tue, 2006-10-03 at 12:13 +0200, A.J.Mechelynck wrote: It's not half a dozen unwanted emails. It's just one email address, i.e., [EMAIL PROTECTED] -- these false bounces all come from the same source. If you feel up to it, write [EMAIL PROTECTED] telling them their mail routers are misconfigured (you can use my mail to Yakov in this thread as a kind of boilerplate). You can also point him to http://www.spamcop.net/fom-serve/cache/329.html . But don't expect quick and accurate action, that postmaster could quite possibly be an arrogant blockhead wo won't do anything you suggest to him for his own good.
Re: gvim segfaulting on Solaris 10
On Sun, 2006-10-01 at 18:00 +0200, A.J.Mechelynck wrote: It's not only on Solaris. On SuSE Linux 9.3, when I build gvim for Gnome2, I get [...] -I/opt/gnome/include/libbonobo-2.0 [...] -I/opt/gnome/include/bonobo-activation-2.0 [...] on the compilation line and [...] -lbonoboui-2 [...] -lbonobo-2 [...] -lbonobo-activation [...] on the link line. I think it's GNOME stuff, seeing where the include files are located. Now gvim does not require GNOME either, it's just one of the compile-time options you can turn on. Actually 'readelf -d gvim' will tell you exactly what libraries are linked against it. I seriously doubt that bonobo is required for gvim, regardless whether it's mentioned or not. This stuff usually is checked trough pkgconfig cross dependencies or through gnome-common. I think the best way linking against GNOME is by providing on the CFLAGS line. -Wl,--export-dynamic greetings, Ali Akcaagac
Re: gvim segfaulting on Solaris 10
On Sun, 2006-10-01 at 19:16 +0200, A.J.Mechelynck wrote: -Wl,--export-dynamic This line tells the linker to link only necessary libraries dynamically. Rather than linking everything. This makes files usually become smaller and loading up much faster. This is no hack it's a valid linker instruction. Seeing that there is a configure option for GNOME (--enable-gnome-check) I tend to use that rather than a CFLAGS hack; and at the end of make, it tries to remove the libs one by one, then re-links with some libraries removed. IIUC, the bonobo libs are kept in. readelf -d `which vim` |grep bonobo gives the following: 0x0001 (NEEDED) Shared library: [libbonoboui-2.so.0] 0x0001 (NEEDED) Shared library: [libbonobo-2.so.0] 0x0001 (NEEDED) Shared library: [libbonobo-activation.so.4] Interesting! After grep'ing through the VIM source I really detected Bonobo Dockitems inside it. Unfortunately that's all soon to be deprecated stuff and should be avoided as much as possible.. Why this ? a) BonoboUI elements are dead stuff and will be removed pretty soon. I only wish this stuff would have happened a few years earlier. b) The recommended way for GNOME and GTK+ GUI's is by using GTK+ (This is not just my idea but a regular advise because of the fact that all GUI elements for GTK+ and GNOME will move inside GTK+- means BonoboUI and hopefully GNOMEUI components are getting removed). c) It only adds a new load of complexity e.g. makes the VIM binary bulkier by depending on a lot of not necessary libraries. greetings, Ali Akcaagac
Re: gvim segfaulting on Solaris 10
On Sun, 2006-10-01 at 23:13 +0200, Bram Moolenaar wrote: The bonobo stuff is only used when compiling for GTK 2 with Gnome support. I generally discourage compiling with Gnome, it has its problems. This is mentioned in the Makefile. If you compile without Gnome, which is the default, no bonobo stuff is used by Vim. If a bonobo library is still linked in then it's because of a dependency. I do understand this. But what I tried explaining was that BonoboUI is deprecated. That means it's dead stuff from within GNOME which should not be used anymore (from what the developers say). So basicly there is no need for extra GNOME GUI components anymore since the encouraged and recommended way to do GNOME GUI is by using GTK+ GUI (from what the developers say). The only interesting part therefore remains is the session management. greetings, Ali Akcaagac
Re: Vim updates
On Sat, 2006-08-12 at 09:48 -0400, Steve Hall wrote: It uses my own configuration of the Nullsoft Installer (NSIS) instead of relying on Vim's NSIS-install.exe combo, but it otherwise contains gvim.exe, vim.exe, gvimext.dll, plus all the standard and runtime files current as of build date. Version output is given in the Notes link at each file. Hmmm, I just downloaded that file and I am not really convinced by it. It's not the same as the releases Bram does. The Menu entries in the Windows Start Menu are not identical, The colorful green icons are missing, even the name convention used gVim 7.x for example is not there. Looking deeper into c:\programs\vim I see the directory populated with plenty other directories while my previous Vim installation has just 2 or 3 iirc. Even the dir name is not Vim it's in lower case letters. I get a dialog all the time starting Vim saying I have to register vim. I therefore decided to go back to plain 7.0 release version of gVim for Windows. mfg, Ali Akcaagac
Re: Vim updates
On Sun, 2006-08-13 at 00:04 +0200, Bram Moolenaar wrote: Previously Tony made patched versions available. He stopped doing that when his computer broke down. Perhaps someone else can volunteer to do this now. Hello Bram, I got a few replies to this request already and what Steve has to offer looks quite interesting to me. I only need to figure out (pretty soon) in how differently his setup stuff works from the one you offered. He mentioned NSIS-Install vs. Nullsoft Installer. What matters for me at the end is that I get the same files, same installation to use VIM at the end. mfg, Ali Akcaagac
Vim updates
Hello Bram, On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? mfg, Ali Akcaagac
VIM 7.0 on WinXP - Strange garbage during editing.
Hello, At work I am using VIM 7.0 on WindowsXP and detected some garbage during editing process. Say I am loading a normal Textfile. I edit it, move around with the arrows, press ESC move around even more, scroll around a bit.. And quite often I find stuff that I previously yanked into the buffers spread all over the file. With other words, it looks like someone has pressed 'p' for pasting what's in the buffer all over the file. I get this quite often when editing code at work and I wonder why I run into errors and reloading the files show me that somehow the content of the buffers got pasted somewhere. The paste somehow happens when scrolling or cursor moving happens. It's quite strange to explain. I also add the vimrc file that I keep using at work (it's basicly the same as I use under my home Linux machine - I never had that problem at home with Linux.) Any ideas are welcome. mfg, Ali Akcaagac .vimrc Description: Binary data
