ruby unstable in ftplugin
Hi vim-dev folks, There appears to be an instability in the ruby interface when making any ruby declaration in an ftplugin file. The following steps result in a SysStackError returned from the interpreter. - no custom .vimrc - ~/.vim/ftplugin/myft.vim minimally contains either ruby EOF EOF or even just ruby $x=1 - edit a new file and :set filetype=myft - repeatedly execute a ruby statement from the vim command line :ruby puts Hello The 7th execution produces the stack error and then every 84th execution following. John
Re: vim on cygwin using win32 clipboard
Hello, Here is the patch for cygwin win32 clipboard support. I had to manually do the following to get it to compile: 1) run ./configure 2) Add the following line to auto/config.h #define FEAT_CYGWIN_WIN32_CLIPBOARD 1 3) auto/config.mk +OS_EXTRA_SRC= os_mswin.c +OS_EXTRA_OBJ= objects/os_mswin.o I was having troubles with the autoconf stuff. I have never used it before, but am working on it. Also there are issues with compiling as TINY with the clipboard support that I'm looking into. Thanks, Frodak Baksik Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html patchset.vim Description: Binary data
Re: vim on cygwin using win32 clipboard
Here is the patch for cygwin win32 clipboard support. I had to manually do the following to get it to compile: 1) run ./configure 2) Add the following line to auto/config.h #define FEAT_CYGWIN_WIN32_CLIPBOARD 1 3) auto/config.mk +OS_EXTRA_SRC= os_mswin.c +OS_EXTRA_OBJ= objects/os_mswin.o I was having troubles with the autoconf stuff. I have never used it before, but am working on it. Also there are issues with compiling as TINY with the clipboard support that I'm looking into. Building a binary with both os_unix.c and os_mswin.c sounds like a bad idea. The big #ifdefs are quite a hack. On the other hand, moving this to a generic file, such as ui.c, also doesn't seem a good plan. How about moving this code to a new file, e.g., winclip.c? Including windows.h in os_unix.c looks like a mistake. There should not be windows code in a Unix-specific file. You probably have to move some code elsewhere. Probably the same winclip.c file. Instead of: #if defined (WIN3264) Please use: #if defined(WIN3264) Perhaps FEAT_CYGWIN_WIN32_CLIPBOARD can be defined automatically when building a non-GUI version with Cygwin? About calling clip_init(FALSE): see the call in os_win32.c. The one in term.c is for xterm. Instead of copying this code with the magic names it should be in a common place. Hmm, it appears it has already been duplicated... -- I'm not familiar with this proof, but I'm aware of a significant following of toddlers who believe that peanut butter is the solution to all of life's problems...-- Tim Hammerquist /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
latin1 vs utf8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I think that question was asked many time before but with differed direction but maybe there is someone having a answer. (I found some for the other direction not for mine.) I have a latin1 setup and like to be able to read utf8 as well. So far so good. I can use set fileencodings=ucs-bom,utf-8,latin1 But what if I have a file with only 7bit characters, reading it, inserting some german umlauts and save? I will have a file holding utf-8 coded german umlauts. Is there any way to only use utf8 if there are utf8 characters in the file (or explicite set)? Like the unix command file -i can choose? Regards Klaus Ethgen Ps. Please add me to the Cc as I cannot read the mailinglist that often. - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen [EMAIL PROTECTED] Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRauCyJ+OKpjRpO3lAQKJewf9Esp0cKaFF4dFOHPONi2ePmmn+pwNY8VI 0j0AHHiwdVl8jmsfsac6o5HbqX6eGeLLFyfg+1yoZ9awDvHitx4ODYU89KxivQ30 cYuv1+U2F5hlUwL3C1pNsH2cNtMEkIIHT16HfwO0LNSFcMXPbia57GI0wTEyQGY5 cBLE5h8Tvqn2uP2ljnMBmyzJUpq76bLcSvU7yBLGgQxax3lK4Nj2tz/G1dti1lG+ hXd87nLydAW9rX8ovob/zap3P+hyX889hnhMg4qHVBC10E80Pa199Y9c+pSBsMTL wn+zBBOM+Td/1U0dH1WIwaJGBpYXjMpQe0ILU48mlMYpMN7zgEX0wQ== =k5cy -END PGP SIGNATURE-
Re: latin1 vs utf8
Hi Klaus :) * Klaus Ethgen [EMAIL PROTECTED] dixit: I think that question was asked many time before but with differed direction but maybe there is someone having a answer. (I found some for the other direction not for mine.) I asked more or less the same a few days ago, you can see the thread in the mailing list archive. Is there any way to only use utf8 if there are utf8 characters in the file (or explicite set)? Like the unix command file -i can choose? You can use 'file -i' in a BufReadPost autocommand and set the appropriate variables from it, but that won't work for empty files, so if you edit a new file and put latin1 characters on it, they will be encoded as utf8 if you set fileencodings=ucs-bom,utf8,latin1. So, I've chosen a different approach. Since 99% of the files I work with are latin1, I've set my vimrc like this: set encoding=default set fileencoding= set fileencodings= You can set the last one to ucs-bom,latin1 if you want, that makes no difference for me because I don't use files with 'bom'. After that, I've set up this mappings to switch manually from one encoding to other: noremap silent Leader+ :setlocal fenc=utf8 enc=utf8CR noremap silent Leader- :setlocal fenc=latin1 enc=latin1CR OK, this is not a perfect solution, and it's a bit crappy and can be automated (for example, using file -i) but it works for me and I find it very comfortable to use. Raúl Núñez de Arenas Coronado -- Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen!
/ and / problem
Hello, When I try to search for a word with the following command :/\word\/ the vim program stops at the :/\ and replaces the with a and then errors: E486: Pattern not found. I haven't found anything on google that speaks to this problem. Can someone help me? Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: / and / problem
(Pardon, this may not have gone out in the correct format.) Russell Bateman wrote: Why are you typing : ? Unless I have misunderstood your notation here, search is simply: /\word\ Russ Bateman Matthew Karas wrote: Hello, When I try to search for a word with the following command :/\word\/ the vim program stops at the :/\ and replaces the with a and then errors: E486: Pattern not found. I haven't found anything on google that speaks to this problem. Can someone help me? Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: / and / problem
When I try to search for a word with the following command :/\word\/ the vim program stops at the :/\ and replaces the with a and then errors: E486: Pattern not found. I haven't found anything on google that speaks to this problem. Can someone help me? sounds like you have a command-line mapping bunging with your setup. Does it happen if you start vim with vim -u NONE If so, there may be a real issue (though I can't duplicate it here). You might want to check the output of :map :cmap to see what sorts of mappings you have in place that could be causing problems. You can then use scriptnames and verbose to try and track down where the offender was established. Whatever mapping you have, it appears to be quite an odd one...perhaps something like cnoremap leader ltcr which is odd in my book. :-/ -tim
Re: / and / problem
I tried the command without the : and still got the same response from Vim. I still can't use the \ and \ expressions. Thanks, Matthew --- Russell Bateman [EMAIL PROTECTED] wrote: (Pardon, this may not have gone out in the correct format.) Russell Bateman wrote: Why are you typing : ? Unless I have misunderstood your notation here, search is simply: /\word\ Russ Bateman Matthew Karas wrote: Hello, When I try to search for a word with the following command :/\word\/ the vim program stops at the :/\ and replaces the with a and then errors: E486: Pattern not found. I haven't found anything on google that speaks to this problem. Can someone help me? Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097
Re: / and / problem
Why are you typing : ? Unless I have misunderstood your notation here, search is simply: /\word\ Both work, and are slightly different: /\word\ just searches in vim. If all you're doing is searching, you're correct that this is likely the easier way to go. :/\word\/ is an ex search/positioning. That means the latter can be used in a range, such as :1,/\word\/d which will delete from the first line through the first match of the regexp. In ex (at the command prompt), a stand-alone search as Matthew did without an action will simply put the cursor on that line number. Same as ed (which still sees disturbingly regular use in my life :) :help :/ :help :range has more info on this. HTH, -tim
Re: Mac Questions
On Mon, Jan 08, 2007 at 06:35:18PM +1100, Brett Calcott wrote: I thought the same thing. But it does not appear to source my .bash_profile or .bashrc. Why would it? Vim is not bash. The shell in which you run a console vim should have already sourced bash startup files as appropriate (see the INVOCATION section of the bash manpage), and the GUI vim couldn't care less about what you might put in some random shell startup file. -- Marc Wilson | Why do we have two eyes? To watch 3-D movies with. [EMAIL PROTECTED] |
Re: C++ Syntax highlighting for Identifier, Statement
This might be possible using a tags file, which already gathers all the class, variable, function, etc names (and their locations). Maybe a command (or autocommand) to create syntax objects based on a tags file would do the trick? I don't know how to do this, but maybe someone else on the list can suggest a way. -Dmitriy On 1/14/07, Andy Wokula [EMAIL PROTECTED] wrote: Matt England schrieb: I'm trying to get function names, class names, objects, variables and similar things to appear as non-white text with 'syntax on'. Had the same question after editing with Visual Studio. This is difficult, I haven't seen that before in any syntax file. I think there are no means to do that in an easy way. The file (and included files) needs to be parsed to collect all the user defined names. I think with some energy it should be possible, because syntax definitions can be added and removed at any time. Hopefully some of the gurus will answer? Andy -- EOF ___ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Upgrading or enabling features in vim
On Mon, 2007-01-15 at 15:43 -0500, Erin Spiceland wrote: I just got a new server and vim wasn't installed. I installed 7.0 from scratch, but there are some problems with missing features or features not working: Just as a reminder, if you use :version you can find out what options vim was compiled with. This should help you enable features that you have on your existing servers, but might not have been compiled in on your new server. -- Evan Klitzke
vim turns xterm blinking cursor off
Hello, Before a vim session, my xterm prompt cursor blinks nicely :), as noted via the vt100 menu (ctrl-middleMouse-Enable Blinking Cursor) - checked. As soon as vim in an xterm starts, the blinking stops. After exiting the edit session, prompt cursor blinking is off, confirmed by the vt100 menu item above, now unchecked. Rechecking the item restores blinking. In vim, :set t_mb? gives t_mb=^[[5m Tried uncommenting all lines in my .vimrc, no luck. root's vi 6.3.82 kills xterm's blinking as well. Problem does not occur in either console or Konsole. lynx (text base web browser) preserves blink in xterm, mutt does not. I am running Red Hat linux 2.6.9-42.0.3.ELsmp, xterm X.Org 6.8.2(192), and vim 7.0 with the following compile time options: VIM - Vi IMproved 7.0 (2006 May 7, compiled Aug 11 2006 16:54:11) Compiled by snipped Normal version with X11-Athena GUI. Features included (+) or not (-): -arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +folding -footer +fork() +gdb -gettext -hangul_input -iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape -mouse_dec +mouse_gpm -mouse_jsbterm -mouse_netterm +mouse_xterm -multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl +postscript +printer -profile -python +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 +xfontset +xim +xsmp_interact +xterm_clipboard +xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc system gvimrc file: $VIM/gvimrc user gvimrc file: $HOME/.gvimrc system menu file: $VIMRUNTIME/menu.vim fall-back for $VIM: snipped Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA -DFUNCPROTO=15 -DNARROWPROTO-g - O2 -I/usr/X11R6/include Linking: gcc -L/usr/X11R6/lib -L/usr/local/lib -o vim -lXaw -lXext -lncurses -lacl -lgpm Any hints, anyone? Thanks in advance, Craig Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com
Re: Upgrading or enabling features in vim
On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote: I just got a new server and vim wasn't installed. I installed 7.0 from scratch, but there are some problems with missing features or features not working: 1. syntax highlighting doesn't work. It is turned on in vimrc but I haven't checked anything else. 2. using the arrows on the keyboard in insert mode puts A, B, C, or D and newline into the file instead of moving up, down, left, or right. 3. doesn't remember my command history 4. doesn't remember where I was in the file when I closed it. 5. only remembers 1 change, so I can't use the u command to undo more than 1 change. What can I do to fix these problems or enable these features? #5 indicates that, as Tim said, you have 'cp' set. But vim sets 'nocp' automatically when it detects and sources an initialization file named .vimrc or _vimrc. Therefore, it appears that your vimrc file is not being sourced, which would explain #1. Executing :version will show you where your vim is looking for its initialization files and :scriptnames will show you the initialization files vim actually sourced. Reading :help initialization will also help you understand what should be happening when you start vim and may help you track down the root problem. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
how to NOT save history
Pals, How I avoid certain commands and/or substitutions NOT to be saved into the history list? For example, I have a sequence of VIM commands that executes on every email quote to properly format it, and I don't want these to appear in the registries and history. Thanks! L.
Re: Upgrading or enabling features in vim
On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote: On Mon, 2007-01-15 at 14:55 -0800, Gary Johnson wrote: On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote: I just got a new server and vim wasn't installed. I installed 7.0 from scratch, but there are some problems with missing features or features not working: 1. syntax highlighting doesn't work. It is turned on in vimrc but I haven't checked anything else. 2. using the arrows on the keyboard in insert mode puts A, B, C, or D and newline into the file instead of moving up, down, left, or right. 3. doesn't remember my command history 4. doesn't remember where I was in the file when I closed it. 5. only remembers 1 change, so I can't use the u command to undo more than 1 change. What can I do to fix these problems or enable these features? #5 indicates that, as Tim said, you have 'cp' set. But vim sets 'nocp' automatically when it detects and sources an initialization file named .vimrc or _vimrc. Therefore, it appears that your vimrc file is not being sourced, which would explain #1. Executing :version will show you where your vim is looking for its initialization files and :scriptnames will show you the initialization files vim actually sourced. Reading :help initialization will also help you understand what should be happening when you start vim and may help you track down the root problem. system vimrc file: $VIM/vimrc $VIM is set to /usr/local/share/vim but /usr/local/share/vim/vimrc doesn't exist, and a vimrc does exist in /etc. How can I change it to use /etc? There is something wrong with your installation. If vim had never before been installed on that server, then the only way for /etc/vimrc to have appeared was for your installation process to have created it. But if you configured vim to look for vimrc in /usr/local/share/vim, then that's where your installation process should have put it. The right place to put it depends on your system and where you want to put stuff and, if you are not the system administrator, where you are allowed to put stuff. You'll have to give us more details of your system and how you configured vim for us to sort this out properly. You wrote originally that there were some features missing or not working in this installation. That implies that you have used them before where they did work. How did you get them to work then? Did you have your own ~/.vimrc or just a system vimrc? If you had just a system vimrc and that is the file now in /etc, I would just move that file to /usr/local/share/vim. On the Unix systems where I have installed vim, I don't even have a system vimrc--I just use ~/.vimrc. There are also ways to set environment variables to get vim to look in other places for initialization files, but since you built this vim from scratch, it would be better for you to reconfigure and rebuild it to get it right, or at least self-consistent. The preferred replying style in the vim list is to put the quoted text on top and your reply underneath, so I have reformatted your reply to that style. Also, don't forget to reply to the list rather than to just the author of the message to which you are replying, so that everyone in the list can follow the discussion and help in solving the problem, or see that it has been solved. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
Re: Upgrading or enabling features in vim
On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote:
On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote:
On Mon, 2007-01-15 at 14:55 -0800, Gary Johnson wrote:
On 2007-01-15, Erin Spiceland [EMAIL PROTECTED] wrote:
I just got a new server and vim wasn't installed. I installed 7.0 from
scratch, but there are some problems with missing features or features
not working:
1. syntax highlighting doesn't work. It is turned on in vimrc but I
haven't checked anything else.
2. using the arrows on the keyboard in insert mode puts A, B, C, or D
and newline into the file instead of moving up, down, left, or right.
3. doesn't remember my command history
4. doesn't remember where I was in the file when I closed it.
5. only remembers 1 change, so I can't use the u command to undo
more
than 1 change.
What can I do to fix these problems or enable these features?
#5 indicates that, as Tim said, you have 'cp' set. But vim sets
'nocp' automatically when it detects and sources an initialization
file named .vimrc or _vimrc. Therefore, it appears that your vimrc
file is not being sourced, which would explain #1.
Executing :version will show you where your vim is looking for its
initialization files and :scriptnames will show you the
initialization files vim actually sourced. ...
system vimrc file: $VIM/vimrc
$VIM is set to /usr/local/share/vim but /usr/local/share/vim/vimrc
doesn't exist, and a vimrc does exist in /etc. How can I change it to
use /etc?
[...]
Thanks for the tips. This server was supposedly a fresh install of RHE.
I say that vim was not installed only because I tried to use it and got
the bash command not found message. I downloaded the source from
vim.org and did ./configure; make; make install. The machines I have
used vim on before were always preinstalled with vim. I use FC6 at home
and RHE on my other 4 servers. I've never worked with a vimrc
or .viminfo before, except very minimally. The five things I listed in
my original email were things that always just worked. I was very
surprised to find vim was not installed this time. rpm -qa | grep vim
shows that vim 6.3 minimal is also installed, but that isn't the one my
system is using, because vim --version shows 7.0. Are there any
configure options that I can use or is there an enhanced version that I
might be used to? Should I reinstall? from source or rpm?
Thanks for the extra info. I think I understand what's going on a
little better now. I just logged on to a system running Red Hat
Enterprise Linux ES release 3 (Taroon Update 8). It happens to have
vim installed on it in /usr/bin, but it also has /bin/vi. I ran
/bin/vi -u NONE (to keep it from choking on my ~/.vimrc), saw that
it was Vim-6.3.81, and executed :version. There I saw this:
Compiled by [EMAIL PROTECTED]
Tiny version without GUI.
...
system vimrc file: /etc/vimrc
user vimrc file: $HOME/.vimrc
user exrc file: $HOME/.exrc
fall-back for $VIM: /usr/share/vim
I think this is Red Hat's minimal vi that they include so that the
user has something to edit with even if /usr is not mounted. So
that's where your /etc/vimrc came from. I would just leave that one
alone.
I then ran /usr/bin/vim -u NONE, also Vim-6.3.81, and again
executed :version with this result:
Compiled by [EMAIL PROTECTED]
Huge version without GUI.
...
system vimrc file: /etc/vimrc
user vimrc file: $HOME/.vimrc
user exrc file: $HOME/.exrc
fall-back for $VIM: /usr/share/vim
So it appears that Red Hat uses the same initialization file for
both /bin/vi and /usr/bin/vim. I took a look at /etc/vimrc and
found that it contained the commands to set 'nocompatible' ('nocp'),
to restore the last cursor position when editing a file, and to set
the color commands for an xterm, among others.
The features you are used to having are not part of the default
installation of vim from vim.org. They are usually compiled into
the binary by the default configure and make process, but they must
also be configured and enabled in your initialization file(s). Red
Hat's vim rpm includes an initialization file but the default
installation of vim from vim.org does not. You have to provide
those yourself.
So, to get a vim with these features enabled, you could either:
- remove your current vim install and install the Red Hat vim
rpm instead, which knows to look in /etc/vimrc; or
- retain your current vim install and copy /etc/vimrc to
/usr/local/share/vim/vimrc.
HTH,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Wireless Division
| Spokane, Washington, USA
RE: omni complete for php is really slooow
Coud anyone hep me hic hic :( Does omni complete for php it can not be improved speed? Tnx in advanced -Original Message- From: Vu The Cuong Sent: Monday, January 15, 2007 1:04 PM To: vim users list Subject: omni complete for php is really slooow Dear all The mail subject says it all:omni complete for php in vim7 in my PC (P4 D, 1GB Ram) is really slooow. How about omni complete for php in vim7 in in your PC? Fast or Slow??? How can I make it faster? Thanks in advanced.
Sudden Trouble Updating with Aap
Hello, all. I've been using Aap to keep up on all of the latest patches since Vim 7.0 was released, and until patch 183 everything worked splendidly. Now I get this when I attempt 'aap --update' from my Vim build directory: Aap: Updating recipe main.aap Aap: Attempting download of http://www.a-a-p.org/vim/main.aap; Aap: Downloaded http://www.a-a-p.org/vim/main.aap; to /home/marv/programs/vim_aap/main.aap Getting Vim version 7.0 using ftp... Aap: /usr/bin/patch -p0 -f ../patches/7.0.001 21 ../patches/7.0.001.done Aap: Error in recipe /home/marv/programs/vim_aap/main.aap line 173: Shell command returned 256 Aap: All messages are in the logfile: /home/marv/programs/vim_aap/AAPDIR/log The log is rather lengthy, but ends with Error is recipe... as above. Is there any sense in posting the whole log? I'm using the latest version of Aap (1.089, as released January 13). Vim itself still works splendidly, patched to 182. I apologize if this isn't the place for Aap questions; nevertheless, any and all guidance will be greatly appreciated. Many thanks in advance. Marv
