Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]
On Thursday 17 May 2007 13:32, A.J.Mechelynck wrote: A.J.Mechelynck wrote: - What is ncftp? On my openSUSE 10.2 system I have a program called ftp but none called ncftp. Well, AFAICT it has disappeared between SuSE 10.0 and 10.2. I have packages named lftp and lukemftp (which are installed); YaST also i think a lot of software that was installed by default in 10.0 was left off 10.2, but any of it you want is readily available if you get your installation sources correct i've got suse 10.2 and i got curious after seeing this thread a visit to yast, software management, searched for ncftp and it brought ncftp right to the fore, installed it for me, and i've been happily learning features since -- imagine commandline recall that works in ftp! bookmarks! anyway, i've got the plain jane installation sources: http://download.opensuse.org/distribution/10.2/repo/oss http://download.opensuse.org/distribution/10.2/repo/non-oss ncftp should have popped right up for you -- what do you have in Configured Software Catalogs (under installation sources)? sc
Re: WARNING! Don't update your local svn repository now!
On Friday 11 May 2007 16:29, Bram Moolenaar wrote: Nicolas Weber wrote: The directories structure of the Subversion repository has been changed. Please use this command to checkout the latest sources: svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7 If you had checked out a copy of the sources before, please run this command in your source root directory to switch into the current branch: svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 Can someone update http://www.vim.org/subversion.php to reflect these changes? I was still discussing what should actually be there, and making sure that SVN contains that. In my opinion vim7 should get you the latest stable version. So aha! i thought so too! i was *right* to be surprised! sc
Re: surprised by beta
On Tuesday 08 May 2007 21:29, you wrote: On 5/8/07, scott [EMAIL PROTECTED] wrote: i was surpised by the fact that simply running 'svn update' bumped me up to 7.1a -- from previous posts i had thought there was something extra that had to be done to get the beta, like create a new 71a directory or something now i've got the beta i feel committed, and will commence chasing after the errors it spews from /usr/local/share/vim/vim71a/filetype.vim when i run it -- apparently the install created the 71a directory for me i am not asking any questions here, it's more like i'm warning those who may prefer to stay with a stable version Maybe you'll be surprised again today... Don't simply svn up. Take care~ oh don't worry -- i am definitely in wait til the dust settles mode and i'll be reading up on svn switch in the immediate future thank you edward sc
Re: surprised by beta
On Tuesday 08 May 2007 12:04, you wrote: Edward L. Fox wrote: On 5/8/07, scott [EMAIL PROTECTED] wrote: i was surpised by the fact that simply running 'svn update' bumped me up to 7.1a -- from previous posts i had thought there was something extra that had to be done to get the beta, like create a new 71a directory or something now i've got the beta i feel committed, and will commence chasing after the errors it spews from /usr/local/share/vim/vim71a/filetype.vim when i run it -- apparently the install created the 71a directory for me i am not asking any questions here, it's more like i'm warning those who may prefer to stay with a stable version No, there won't be any tags, branches here, every thing is just going linearly, giggling. I just stumbled upon the svn update to disaster myself. Maybe its time to start getting a bit serious about project management? To the svn maintainer: The best practice is for the repository root to look something like this: /trunk (mirror of CVS, as usual) /tags (contains 7.0/ and 7.1a/ folders -- obviously these folders are static) /branches (possibly used for contribs such as patches that didn't make it into trunk (Bram's version) yet) To anyone else afflicted: To downgrade back to 7.0-stable, just do an svn update -r NNN where NNN is the revision you want to downgrade to. Check the logs for the exact revision, I don't know off hand. Cheers, -Robert the last stable one i had was 7.0.236 -- how would you specify that? not sure i need to, the fixes to filetype.vim were trivial -- a couple of patches only partly applied left '' and '' in it sc
Re: surprised by beta
On Tuesday 08 May 2007 15:32, you wrote: Mr Toothpik wrote: i was surpised by the fact that simply running 'svn update' bumped me up to 7.1a -- from previous posts i had thought there was something extra that had to be done to get the beta, like create a new 71a directory or something now i've got the beta i feel committed, and will commence chasing after the errors it spews from /usr/local/share/vim/vim71a/filetype.vim when i run it -- apparently the install created the 71a directory for me What errors? i'm sorry bram, i didn't write them down, i didn't save the buggy 'filetype.vim', i just fixed it -- my bad -- but it was obvious there was an uncommitted patch or something -- there were and in it in two places they were syntax errors, and the comments around the were something to do with mine and r263, as memory serves they were replacing coronary with coronaryRespite or whatever that thread was sc
surprised by beta
i was surpised by the fact that simply running 'svn update' bumped me up to 7.1a -- from previous posts i had thought there was something extra that had to be done to get the beta, like create a new 71a directory or something now i've got the beta i feel committed, and will commence chasing after the errors it spews from /usr/local/share/vim/vim71a/filetype.vim when i run it -- apparently the install created the 71a directory for me i am not asking any questions here, it's more like i'm warning those who may prefer to stay with a stable version
Re: patch 7.0.236
i had to 'rm src/auto/config.cache before i could build with this one sc
Re: lost menu
On Friday 29 December 2006 10:55, A.J.Mechelynck wrote: Charles E Campbell Jr wrote: scott wrote: has anyone else lost the ability to get a menu by entering :set guioptions+=m nothing happens i see 4: /usr/local/share/vim/vim70/menu.vim in :scriptnames... no glaring errors on build (7.0.178) i build with export CONF_OPT_GUI='--enable-gnome-check' in SUSE linux 10.0 I don't have any problems seeing a menu (I'm using Fedora Core 5, vim 7.0.1-178). For build options, I use ./configure --with-features=huge --enable-perlinterp I commented out my usual guioptions setting (set guioptions=abegmr) and put your (set guioptions+=m) in instead. So, it appears likely that there's a permission error associated with your being able to use gnome, since it works for you as root. Hmm, are you sure you're using the same vim as root that you are as a user? What does which vim say as user and as root? Why do you need the enable-gnome-check? In Makefile, there's a note: GNOME means GTK with Gnome support. If using GTK, then GNOME will # automatically be used if it is found. If you have GNOME, but do not want to # use it (e.g., want a GTK-only version), then use --enable-gui=gtk. so normally if you use GTK then GNOME will automatically be used, too. That paragraph is outdated. Gnome is now disabled by default. Use --enable-gnome-check if you want configure to include it in GTK builds if it finds it on your system. Also in the Makefile: # Uncomment one of these lines if you have that GUI but don't want to use it. # The automatic check will use another one that can be found # Gnome is disabled by default, it may cause trouble. ... #CONF_OPT_GUI = --enable-gnome-check which seems to indicate that the --enable-gnome-check is causing GNOME to be disabled, oddly enough. No Gnome, no menu. Regards, Chip Campbell --enable-gnome-check causes Gnome _not_ to be disabled -- provided that you have Gnome and GTK, or Gnome2 and GTK2, installed. Without --enable-gnome-check, configure doesn't check for Gnome and doesn't include it even if you have it installed. Best regards, Tony. 'which vim' shows as /usr/local/bin for both myself and root -- the :ver text indicates the same -- i have no reason to think they are different, and i know they both use the same .vimrc and .gvimrc -- the ones on /root are symbolic links to the ones on my home path -- further, :scriptnames shows the same set of scripts loaded for both myself and root (with menu.vim prominently mentioned) not sure if it's related, but :ver shows a huge version with GTK2-GNOME (not GNOME2) -- i still find it weird that i don't get a menu and root does -- scott
Re: lost menu
On Friday 29 December 2006 22:00, A.J.Mechelynck wrote: scott wrote: On Friday 29 December 2006 10:55, A.J.Mechelynck wrote: Charles E Campbell Jr wrote: scott wrote: has anyone else lost the ability to get a menu by entering :set guioptions+=m nothing happens i see 4: /usr/local/share/vim/vim70/menu.vim in :scriptnames... no glaring errors on build (7.0.178) i build with export CONF_OPT_GUI='--enable-gnome-check' in SUSE linux 10.0 I don't have any problems seeing a menu (I'm using Fedora Core 5, vim 7.0.1-178). For build options, I use ./configure --with-features=huge --enable-perlinterp I commented out my usual guioptions setting (set guioptions=abegmr) and put your (set guioptions+=m) in instead. So, it appears likely that there's a permission error associated with your being able to use gnome, since it works for you as root. Hmm, are you sure you're using the same vim as root that you are as a user? What does which vim say as user and as root? Why do you need the enable-gnome-check? In Makefile, there's a note: GNOME means GTK with Gnome support. If using GTK, then GNOME will # automatically be used if it is found. If you have GNOME, but do not want to # use it (e.g., want a GTK-only version), then use --enable-gui=gtk. so normally if you use GTK then GNOME will automatically be used, too. That paragraph is outdated. Gnome is now disabled by default. Use --enable-gnome-check if you want configure to include it in GTK builds if it finds it on your system. Also in the Makefile: # Uncomment one of these lines if you have that GUI but don't want to use it. # The automatic check will use another one that can be found # Gnome is disabled by default, it may cause trouble. ... #CONF_OPT_GUI = --enable-gnome-check which seems to indicate that the --enable-gnome-check is causing GNOME to be disabled, oddly enough. No Gnome, no menu. Regards, Chip Campbell --enable-gnome-check causes Gnome _not_ to be disabled -- provided that you have Gnome and GTK, or Gnome2 and GTK2, installed. Without --enable-gnome-check, configure doesn't check for Gnome and doesn't include it even if you have it installed. Best regards, Tony. 'which vim' shows as /usr/local/bin for both myself and root -- the :ver text indicates the same -- i have no reason to think they are different, and i know they both use the same .vimrc and .gvimrc -- the ones on /root are symbolic links to the ones on my home path -- further, :scriptnames shows the same set of scripts loaded for both myself and root (with menu.vim prominently mentioned) not sure if it's related, but :ver shows a huge version with GTK2-GNOME (not GNOME2) -- i still find it weird that i don't get a menu and root does Does your non-root login name have read permission on /usr/local/share/vim/vim70/menu.vim ? Or is your vimrc not created with root as owner? (check either file with ls -l ) Best regards, Tony. menu.vim is owned by root -- i 'su' before performing the 'make install' -- but both group and other have read permission -- i verified by, as me, starting a gvim session on that very module, no problem the real .vimrc, on my home path, is owned by me -- the sybolic link to it on /root is owned by root -- i have no evidence that either root or myself is having problems reading .vimrc -- the app is coming up fine i did notice the font of the menu that root does see is quite small -- i would change it to a larger font if the menus were working for both accounts and if i had any intention of really using the menu system i occasionally turn the menu on when i want to see a list of available color schemes for choosing from, which is what i was doing when i found out i'm not getting the menu -- can't say how many versions/patches i've gone through before finding this out -- i use it *very* seldom -- it just bothers me that i can't get a menu when i ask for one now -- scott
Re: lost menu
On Tuesday 26 December 2006 11:36, scott wrote: has anyone else lost the ability to get a menu by entering :set guioptions+=m nothing happens i see 4: /usr/local/share/vim/vim70/menu.vim in :scriptnames... no glaring errors on build (7.0.178) i build with export CONF_OPT_GUI='--enable-gnome-check' in SUSE linux 10.0 i just noticed when running gvim as root i see the menu root has a symbolic link to my .vimrc and .gvimrc, so the sessions should be the same -- as me, there's no menu -- as root, the menu's fine -- what am i overlooking? -- scott
lost menu
has anyone else lost the ability to get a menu by entering :set guioptions+=m nothing happens i see 4: /usr/local/share/vim/vim70/menu.vim in :scriptnames... no glaring errors on build (7.0.178) i build with export CONF_OPT_GUI='--enable-gnome-check' in SUSE linux 10.0 -- scott
Re: v107m of netrw available -- needs testing!
charles-- i may have horked it up getting it extracted from the vimball and put in place -- i'm not happy with the paths vimball chooses to place it on -- i want it available both to myself and root, to which end i am copying all the modules to /usr/local/shr/vim/vim70/whatever i am running SUSE linux 10.0, my current vim is 7.0.178 i've tried this before in an attempt to get away from the way all these latest netrws reset my formatoptions for me -- i've noticed they also replace the latest search argument, another annoyance, so every time i see another announcement of a new netrw, i struggle to get it installed and try it out this one gives numerous errors: Error detected while processing function netrw#Explore: line2: E121: Undefined variable: b:netrw_curdir E15: Invalid expression: b:netrw_curdir line 68: E121: Undefined variable: curfile E116: Invalid arguments for function substitute(curfile,'^.*/','','e').'\','cW') E116: Invalid arguments for function search then it comes up without syntax highlighting when i clear the errors -- also it changes my formatoptions, still, so i haven't gained anything over and above all these new error messages i will be reverting to my previous version (v98) -- i've got a :so ~/.vimrc mapped so i can get my formatoptions and whatever else it resets back (but not the last search arg!) easily sorry to be such a pest, scott On Friday 15 December 2006 11:08, you wrote: Hello! I've put a copy of netrw v107m on my website: http://mysite.verizon.net/astronaut/vim/index.html#NETRW . It needs testing! There's been a lot of changes, mostly involving more code sharing between local and remote browsing (and which more simply allows both modes to support the new tree listing liststyle). Windows types -- I haven't tested it near enough on that platform yet, so please let me know any problems with it you may have. I mention Windows users specifically because apparently I had none trying out netrw back when vim 7.0 was still in beta release. The new version of netrw also has support (thanks to Peter Bengtsson) for the Amiga; he gave me code based on a not-yet-released version of 107l which I tried to merge, so there's a need for testing with it there, too. Thank you, Chip Campbell -- scott
Re: text is gone
On Thu, 2006-09-07 at 08:13 +0200, A.J.Mechelynck wrote: scott wrote: ok, so help me out here i've looked at filetype vim, and i see nothing that associates _.txt modules with ft=txt whether i enter my 'ai' modules with the script or by navigating to where they are and, with my bloody fingers typing 'gvim ai_200609.txt', still, inside the module, filetype is undefined are we only supposed to use vim for exotic languages? is 'text' deprecated? i thought it used to suffice to have an extension of .txt now the ground is shifting under my feet... sc As far as I rember checking, *.txt was associated with nothing so it was edited as, basically, free text with just a single BW set of fg/bg colors, no auto-linebreak etc. There is an autocommand in the vimrc_example.vim which sets 'textwidth' to 78 (causing auto-linebreak at column 78) for any files with text filetypes. If you want to detect *.txt, you can: 8 ~/.vimrc ... runtime vimrc_example.vim au! vimrcEx FileType ...etc. 8 8 ~/.vim/filetype.vim augroup filetypedetect ... etc ... au BufRead,BufNewFile *.txt setf text ... etc ... augroup END 8 then write your own scripts: ~/.vim/ftplugin/text.vim (for local options using :setlocal and/or mappings/abbreviations using :map buffer, :abbr buffer etc.), ~/.vim/syntax/text.vim (for syntax colouring if any: :syntax and :hi default commands) ~/.vim/indent/text.vim (for special indenting if any: probably :setlocal indentexpr to a function defined there). (on Windows, replace /.vim/ by /vimfiles/ and .vimrc by _vimrc) Best regards, Tony. excuse me this transcends ridiculous i am editing text, and i have gone around the bend to tell vim that i am doing so to have to create an entire text syntax, where NOTHING HAPPENS, seems against every premise that vim was built on why do i have to be surprised by 'cindent' when i am editing text? it is, after all, text, and i went out of my way to define these modules with the .txt extension, even here in linux -- specifically so he'd know why would cindent kick in if i'm not editing c? now you say *.txt is associated with nothing -- that goes far to explain why my search in filetype.vim for 'txt' was so fruitless, thank you i don't remember having this problem before -- before what exactly i'm not sure -- but i've been surprised with indenting behavior enough to go out of my way to turn every indenting feature off i can find, but still i get surprises now cindent is off, maybe i can still work...tab is easy to hit... forgive me, i have no bottom line -- no idea what i'm saying -- i'll shutup now sc
Re: text is gone
On Thu, 2006-09-07 at 10:19 -0400, Charles E Campbell Jr wrote: scott wrote: ok, so help me out here i've looked at filetype vim, and i see nothing that associates _.txt modules with ft=txt whether i enter my 'ai' modules with the script or by navigating to where they are and, with my bloody fingers typing 'gvim ai_200609.txt', still, inside the module, filetype is undefined are we only supposed to use vim for exotic languages? is 'text' deprecated? i thought it used to suffice to have an extension of .txt now the ground is shifting under my feet... - scott wrote again: excuse me this transcends ridiculous i am editing text, and i have gone around the bend to tell vim that i am doing so to have to create an entire text syntax, where NOTHING HAPPENS, seems against every premise that vim was built on why do i have to be surprised by 'cindent' when i am editing text? it is, after all, text, and i went out of my way to define these modules with the .txt extension, even here in linux -- specifically so he'd know why would cindent kick in if i'm not editing c? now you say *.txt is associated with nothing -- that goes far to explain why my search in filetype.vim for 'txt' was so fruitless, thank you i don't remember having this problem before -- before what exactly i'm not sure -- but i've been surprised with indenting behavior enough to go out of my way to turn every indenting feature off i can find, but still i get surprises now cindent is off, maybe i can still work...tab is easy to hit... forgive me, i have no bottom line -- no idea what i'm saying -- i'll shutup now Yep, nothing associates *.txt modules with ft=txt. That's because there is no syntax/txt.vim highlighting, at least as distributed. What highlighting should be done for a non-specific, arbitrary language? Keywords? Regions? Or did you intend to mean that you used a .txt suffix to avoid syntax highlighting, filetype plugins, etc? To answer your question about cindent -- are you sure you're not setting it yourself in your .vimrc? To find out where it was last set: :verbose set cin? There's also autoindent (short form: ai). If that's on, to find out where it was last set: :verbose set ai? Perhaps you can either remove these settings from your .vimrc if that's where they're set or remove any plugins that are setting them. What do you mean by entering your ai modules with the script? Chip Campbell it is irrelevant to my rant, but i'm glad to share -- it's a simple one line bash executable on my bin path that gets me into the current 'ai' module (think action items): #!/bin/bash gvim -S ~/bin/ai.vim and then ai.vim sets up the name: let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name since i was editing ai_200609.txt having used this process, i felt obliged, in the interest of full disclosure, to mention it in the context of why filetype might not be set my 'ai' modules and vim's autoindent feature are related only in that they share a name for homework i am assigning myself the research of as many flavors of indenting as i can find -- my first objective will be to find out exactly how many options are being set with the command :set filtype plugin indent
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott
indenting weirdness
help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 05:58 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott IIUC it's the version of ctags that came with SuSE 9.3 rpm -qa |grep ctags ctags-2004.11.15-3 which -a ctags /usr/bin/ctags ls -l `which ctags` -rwxr-xr-x 1 root root 128852 Mar 19 2005 /usr/bin/ctags ctags --version Exuberant Ctags 5.5.4, Copyright (C) 1996-2003 Darren Hiebert Compiled: Mar 19 2005, 19:18:40 Addresses: [EMAIL PROTECTED], http://ctags.sourceforge.net Optional compiled features: +wildcards, +regex The wierdness appeared after installing the manpageview plugin from vim-online, and disappeared after removing it as well as versions of the netrw and vimball plugins which had become older than the default ones due to a runtime rsync. Don't know what _any_ of those had to do with not finding the help; and (I checked) my doc/tags files were OK -- anyway, regenerating them all using (internal) helptags changed nothing. Best regards, Tony. hmmm what jumped out at me in your error messages was the '@en' -- makes me think whatever happened to you relates to something to do with the english language -- did manpageview have a lot of klunky language weirdness? sc
Re: indenting weirdness
peter-- that was the clue i needed -- after turning 'cindent' off i was able to type an optimistic man might be tempted to celebrate -- we have proven, after all, that life goes on after microsoft -- macros can be created in OOo basic, however bloody without the indenting weirdness as much java and C# as i work on, i hope i can live without cindent, but between you and me, i'm betting off is better thanx! sc On Thu, 2006-09-07 at 14:08 +1000, Peter Hodge wrote: Hello scott, The 'filetype=' message is what happens when you use ':set filetype=' and don't specify any filetype. If you have 'cindent' turned on, Vim will add an indent after a line ending in a comma (,) and your sample sentence does. Use ':set cindent?' to check if it is turned on. regards, Peter --- scott [EMAIL PROTECTED] wrote: help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com
text is gone
ok, so help me out here i've looked at filetype vim, and i see nothing that associates _.txt modules with ft=txt whether i enter my 'ai' modules with the script or by navigating to where they are and, with my bloody fingers typing 'gvim ai_200609.txt', still, inside the module, filetype is undefined are we only supposed to use vim for exotic languages? is 'text' deprecated? i thought it used to suffice to have an extension of .txt now the ground is shifting under my feet... sc
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 06:55 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 05:58 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott IIUC it's the version of ctags that came with SuSE 9.3 rpm -qa |grep ctags ctags-2004.11.15-3 which -a ctags /usr/bin/ctags ls -l `which ctags` -rwxr-xr-x 1 root root 128852 Mar 19 2005 /usr/bin/ctags ctags --version Exuberant Ctags 5.5.4, Copyright (C) 1996-2003 Darren Hiebert Compiled: Mar 19 2005, 19:18:40 Addresses: [EMAIL PROTECTED], http://ctags.sourceforge.net Optional compiled features: +wildcards, +regex The wierdness appeared after installing the manpageview plugin from vim-online, and disappeared after removing it as well as versions of the netrw and vimball plugins which had become older than the default ones due to a runtime rsync. Don't know what _any_ of those had to do with not finding the help; and (I checked) my doc/tags files were OK -- anyway, regenerating them all using (internal) helptags changed nothing. Best regards, Tony. hmmm what jumped out at me in your error messages was the '@en' -- makes me think whatever happened to you relates to something to do with the english language -- did manpageview have a lot of klunky language weirdness? sc I didn't check (and now it's gone thanks to rm -vf); but after recompiling (make reconfig but not make install) with (a) a define commented-out: /* # define FEAT_MULTI_LANG */ (b) an additional configure setting: export CONF_OPT_NLS='--disable-nls', and (c) renaming $VIMRUNTIME/lang to lanx (probably overkill but you never know...), I got the same error without the @en IIUC that @xx postfix is characteristic of multi-language help. My vimrc sets :language messages to C (on Unix) or en (on Windows) before sourcing the vimrc_example, to avoid French or Dutch menus and error messages regardless of the locale. Now I have undone all those changes, removed, as I said, the dubious plugins, re-made reconfig, and my 7.0.091 again shows any help with no noticeable lag. The only global plugins which I still have outside $VIMRUNTIME/plugin are matchit (runtime macros/matchit.vim) and a small plugin I wrote myself to display the splash screen (:intro) at the VimEnter event, even when Vim is started with one or more editfiles named on the command-line. Best regards, Tony. IIUC, your problem has been solved? no more goofy :help errors?
Re: scrolloff enhancement wish
On Fri, 2006-07-21 at 09:23 +0100, Matthew Winn wrote: On Fri, Jul 21, 2006 at 10:02:10AM +0200, Bram Moolenaar wrote: Yakov Lerner wrote: I suppose there might be some way to map all the movement commands to reposition the current line to a certain place on the screen, but at the time I was doing all this it was quicker to scroll the text each time than it would have been to write all the necessary mappings. :nmap n nzz see if you like that
Re: Gvim for KDE
stefan-- i don't get it vim compiles for me just fine -- suse linux 10.0, using KDE, vim 7.0.35 -- am i missing something here? are you asking for a binary? if you want one that excludes arabic, farsi, and righleft, and includes python 2.4.3, i can probably find a way to get you one... scott On Wed, 2006-07-12 at 22:23 +0200, Stefan Karlsson wrote: These two sections in the documentation seems contradictory: *gui-kde* *kde* *KDE* *KVim* There is no KDE version of Vim. There has been some work on a port using the Qt toolkit, but it never worked properly and it has been abandoned. Work continues on Yzis: www.yzis.org. *gui-x11-kde* For Vim-KDE, you need at least Qt(=2.x) and the corresponding kdelibs. To compile, you must use the --with-qt-dir configure flag because QTDIR is not automatically detected yet. Giving KDE's directories to the configure script may also help in some cases. By the way, is there anyone out there that is working on a KDE version? I have tried Kyzis a bit, but didn't really like it ...
question for charles (or anyone): netrw whacking t
charles-- i have formatoptions set in my .vimrc to tcroqn i have a script i call gvime that starts 'vim -g -c Explore' (i tried 'gvim -c Explore' with the same result) if i run gvime, and select a file to edit, i find formatoptions is now croqn -- the t has been whacked, and even with a modeline setting textwidth, i am manually formatting paragraphs, running scriptnames, and generally having a bad day i have a python enabled gvim, version 7.0.35, on linux (rel 2.6.13-15.10-smp) kde version 3.4.2 level b in other words i just installed suse linux 10.0 and i'm a linux newbie any help will be appreciated, scott
