Please allow disabling 'floats' from configure
There is no configure option I can see to disable the 'floats'. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On 21 июл, 09:58, James Vega james...@jamessan.com wrote: This is due to the new conceal feature. The tags in Vim's help files are surrounded by ||. When your cursor is on a line with tags, the || are displayed but highlighted using the Ignore group so they blend in with the background. When your cursor moves off of the line, the || are concealed, which completely removes them from display. See :help new-conceal for more information. But as I pointed in PS block there is no 'shrink and widen' behaviour if I run vim with -u NORC. And I do not move cursor out of that line -- I do move it left and right. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On Tue, 20 Jul 2010, Maxim Kim wrote: On 21 июл, 09:58, James Vega james...@jamessan.com wrote: See :help new-conceal for more information. But as I pointed in PS block there is no 'shrink and widen' behaviour if I run vim with -u NORC. And I do not move cursor out of that line -- I do move it left and right. Because you don't have syntax highlight enabled in your example, which turns off the conceal feature as well, since it uses the highlighting engine. Moving the cursor back and forth over the concealed text to cause it to appear is the original behavior of the conceal feature in the development branch of Vim, but it has been changed to having the cursor anywhere within the line causes all concealed text to be shown within that line. This was to solve a problem with another new feature. In other words, to answer your question: It's not a bug, it's intentional and a feature. - Christian -- Christian J. Robinson hept...@gmail.com -- http://christianrobinson.name/ -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On 21 июл, 10:32, Christian J. Robinson hept...@gmail.com wrote: On Tue, 20 Jul 2010, Maxim Kim wrote: On 21 июл, 09:58, James Vega james...@jamessan.com wrote: Because you don't have syntax highlight enabled in your example, which turns off the conceal feature as well, since it uses the highlighting engine. 3. :syntax on Moving the cursor back and forth over the concealed text to cause it to appear is the original behavior of the conceal feature in the development branch of Vim, but it has been changed to having the cursor anywhere within the line causes all concealed text to be shown within that line. This was to solve a problem with another new feature. It would look alright if concealed characters become visible as soon as I am on consealed text. But in my example they do not appear when cursor is on strchars(). But when I move cursor left to 'and' word which is not concealed. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Please allow disabling 'floats' from configure
On 21/07/10 08:08, ron wrote: There is no configure option I can see to disable the 'floats'. IIUC, there's no configure argument for that, but you can disable floating-point in feature.h line 390: /* * +evalBuilt-in script language and expression evaluation, * :let, :if, etc. * +float Floating point variables. */ #ifdef FEAT_NORMAL # define FEAT_EVAL # if defined(HAVE_FLOAT_FUNCS) || defined(WIN3264) || defined(MACOS) /* # don't define FEAT_FLOAT No float today, my love is gone away ;-) */ # endif #endif Best regards, Tony. -- The state law of Pennsylvania prohibits singing in the bathtub. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Please allow disabling 'floats' from configure
I understand I can do that; but that means I have to manually fix it on each new release from Bram :( -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Vim 7.3a ready for beta testing
Mikeyao (?) wrote: Why not javascript interface ? The code has developed. http://www.vim.org/scripts/script.php?script_id=2375 I haven't actually heard from someone using it. Also, I have no idea why someone would want to write plugins in Javascript. Perhaps because it's the only language someone knows? -- Vi beats Emacs to death, and then again! http://linuxtoday.com/stories/5764.html /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Please allow disabling 'floats' from configure
On 21/07/10 11:31, ron wrote: I understand I can do that; but that means I have to manually fix it on each new release from Bram :( Now that Bram is using Mercurial, you can clone the Mercurial repo and merge your local changes with that. I have two one-line changes in feature.h myself, to get -tag_old_static and +xterm_save, and that's what I do. There were recently some changes to feature.h but I didn't get any merge conflicts. See http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial for details. Best regards, Tony. -- Good advice is something a man gives when he is too old to set a bad example. -- La Rouchefoucauld -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On 21 июл, 09:41, Maxim Kim haba...@gmail.com wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times to reach strwidth() function and l to go back. The line widens and shrinks. PS If I run gvim with -u NORC and do all above with set nocp first -- everything is ok. Here are 2 screenshots: http://picasaweb.google.com/lh/photo/g7T_toVidI7hbIYJtLl4Uw?feat=directlink after I do one right keypress http://picasaweb.google.com/lh/photo/9mzV-plHx54rcCRoRp0xdA?feat=directlink -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Vim 7.3a ready for beta testing
Vim support many languages interface and I just found new lua interface added in 7.3. I think most programmers know javascript and like it, it's going to mainstream. Many web developers using vim, they know javascript well. On Jul 21, 5:38 pm, Bram Moolenaar b...@moolenaar.net wrote: Mikeyao (?) wrote: Why not javascript interface ? The code has developed. http://www.vim.org/scripts/script.php?script_id=2375 I haven't actually heard from someone using it. Also, I have no idea why someone would want to write plugins in Javascript. Perhaps because it's the only language someone knows? -- Vi beats Emacs to death, and then again! http://linuxtoday.com/stories/5764.html /// Bram Moolenaar -- b...@moolenaar.net --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 /// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On 21 июл, 13:59, Maxim Kim haba...@gmail.com wrote: On 21 июл, 09:41, Maxim Kim haba...@gmail.com wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times to reach strwidth() function and l to go back. The line widens and shrinks. PS If I run gvim with -u NORC and do all above with set nocp first -- everything is ok. Here are 2 screenshots: http://picasaweb.google.com/lh/photo/g7T_toVidI7hbIYJtLl4Uw?feat=dire... after I do one right keypress :s/right/left -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Please allow disabling 'floats' from configure
Ron Aaron wrote: I understand I can do that; but that means I have to manually fix it on each new release from Bram :( Is there some specific reason you want to disable float support? -- TALL KNIGHT: When you have found the shrubbery, then you must cut down the mightiest tree in the forest ... with a herring. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: py3file command doesn't work
Nico Raffo wrote: The :py3file command appears not to work as expected, specifically it seems like when you type :py3file foo.py Vim is running :py3 file foo.py Which gives the obvious syntax error File string, line 1 file foo.py ^ SyntaxError: invalid syntax Vim 7.3b from fresh pull from hg repository. Built with --with- features=huge --enable-pythoninterp --enable-python3interp That's my fault. I'll fix it. Let me also add :python3 as an alias for :py3. I think that's better than supporting :py3thon. -- Q: How do you tell the difference between a female cat and a male cat? A: You ask it a question and if HE answers, it's a male but, if SHE answers, it's a female. /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
Maxim Kim wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times to reach strwidth() function and l to go back. The line widens and shrinks. PS If I run gvim with -u NORC and do all above with set nocp first -- everything is ok. I can't reproduce it. There were a few recent changes in this area. Do you still see the problem if you build from the current Mercurial version? -- [Autumn changed into Winter ... Winter changed into Spring ... Spring changed back into Autumn and Autumn gave Winter and Spring a miss and went straight on into Summer ... Until one day ...] Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Color code my Vi Editor
Hi, I tried to look up information online on this but wasn't able to find anything that worked. I used Vi at my old job and loved the editing features it provided. I've moved to a new place now and I am the only developer here. I logged into a SunOS Unix box (bash shell) and while things work my vi editor looks very bland (no colors schemes and bw) which makes reading and writing code difficult. When I looked up info I found that I have to put the color coding information into my .vimrc file in my home directory. I am in a corporation and under my home /home/myName I don't have a .vimrc file. I found a sample one online that I copied but it didn't have any effect on my vi editor. I also tried syntax on commands by vi said it wasn't recognized by vi. Can anyone please help make my vi editor colorful? Many thanks! -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Vim 7.3a ready for beta testing
Please bottom post on this list... I'm reformatting... On Wed, Jul 21, 2010 at 6:05 AM, mikeyao yaoweiz...@gmail.com wrote: On Jul 21, 5:38 pm, Bram Moolenaar b...@moolenaar.net wrote: Mikeyao (?) wrote: Why not javascript interface ? The code has developed. http://www.vim.org/scripts/script.php?script_id=2375 I haven't actually heard from someone using it. Also, I have no idea why someone would want to write plugins in Javascript. Perhaps because it's the only language someone knows? Vim support many languages interface and I just found new lua interface added in 7.3. I think most programmers know javascript and like it, it's going to mainstream. Many web developers using vim, they know javascript well. I haven't tried the JS interface patch, but I definitely would like to see a javascript interface. I don't know Lua, TCL or Ruby (though I intend to learn the latter one day), I don't like to use Perl or Python for anything more than a few dozen lines, and I hate Scheme almost as much as Lisp. Javascript is a powerful, easy to learn, multi-paradigm language that was designed for embedding, so I think it's a perfect fit for a Vim interface - and I personally would be more likely to use it than any of the other interfaces. ~Matt -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Color code my Vi Editor
Can anyone please help make my vi editor colorful? Hi, it is a big difference between 'vi' and 'vim'. You work with plain 'vi' as being on solaris, probably. So the right answer should be 'install vim'. Try http://sunfreeware.com/ After vim installation, I recommend: :help coloring And if it did not help your problem, you may ask at v...@vim.org Regards, Milan Vancura -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Color code my Vi Editor
On Wed, Jul 21, 2010 at 10:11 AM, duffman wrote: Hi, I tried to look up information online on this but wasn't able to find anything that worked. I used Vi at my old job and loved the editing features it provided. I've moved to a new place now and I am the only developer here. I logged into a SunOS Unix box (bash shell) and while things work my vi editor looks very bland (no colors schemes and bw) which makes reading and writing code difficult. When I looked up info I found that I have to put the color coding information into my .vimrc file in my home directory. I am in a corporation and under my home /home/myName I don't have a .vimrc file. I found a sample one online that I copied but it didn't have any effect on my vi editor. I also tried syntax on commands by vi said it wasn't recognized by vi. Can anyone please help make my vi editor colorful? Many thanks! On a Solaris box, it's relatively unlikely that `vi' runs vim. You can check by doing :version - that will either fail entirely (meaning you're not running vim) or show a bunch of information including -syntax (meaning you are using a vim binary, but that syntax highlighting support wasn't compiled in). Either way, the solution will be to find a better package or compile vim from source. ~Matt -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Color code my Vi Editor
On 2010-07-21, duffman wrote: Hi, I tried to look up information online on this but wasn't able to find anything that worked. I used Vi at my old job and loved the editing features it provided. I've moved to a new place now and I am the only developer here. I logged into a SunOS Unix box (bash shell) and while things work my vi editor looks very bland (no colors schemes and bw) which makes reading and writing code difficult. When I looked up info I found that I have to put the color coding information into my .vimrc file in my home directory. I am in a corporation and under my home /home/myName I don't have a .vimrc file. I found a sample one online that I copied but it didn't have any effect on my vi editor. I also tried syntax on commands by vi said it wasn't recognized by vi. Can anyone please help make my vi editor colorful? The SunOS vi is not Vim, so it does not read ~/.vimrc. Instead, it looks for configuration information in ~/.exrc. I don't think the SunOS vi supports color. (I'll have access to a SunOS machine later today but I don't at the moment.) If you want a colorful vi, you'll have to install some other vi, such as Vim. You can either ask your system administrator to do this for you, or you can build your own Vim, install it in ~/bin, and add ~/bin to your PATH. The best way to get the Vim source these days is to use Mercurial, but you probably don't have Mercurial on that SunOS system, either, so you would have to install that as well. Installing programs such as Mercurial and Vim is not difficult. Let us know if it is feasible for you to do that and we can give you whatever further instructions you might need. Regards, Gary -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Please allow disabling 'floats' from configure
On Wednesday 21 July 2010 17:13:33 Bram Moolenaar wrote: Is there some specific reason you want to disable float support? Yes; I can't imagine any reason I would ever want floating-point support in my vimscripts, so as far as I'm concerned it's just a waste of space. -- Sending me something private? Use my GPG public key: AD29415D -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Patch for bug in undo.c
I found a bug in undo.c while trying to build Vim 7.3 for the first time on my Cygwin 1.5 system. The problem is that the condition of an 'if' contains a pair of parentheses, but only the closing parenthesis is contained within an #ifdef. I didn't see any reason for the parentheses, so I removed them both. The problem exists at changeset 7a57fe6a5157. The output of hg diff is included below. Regards, Gary diff -r 7a57fe6a5157 src/undo.c --- a/src/undo.cWed Jul 21 16:00:43 2010 +0200 +++ b/src/undo.cWed Jul 21 09:01:14 2010 -0700 @@ -1437,10 +1437,10 @@ * this fails, set the protection bits for the group same as the * protection bits for others. */ -if (st_old_valid (mch_stat((char *)file_name, st_new) = 0 +if (st_old_valid mch_stat((char *)file_name, st_new) = 0 st_new.st_gid != st_old.st_gid # ifdef HAVE_FCHOWN /* sequent-ptx lacks fchown() */ -fchown(fd, (uid_t)-1, st_old.st_gid) != 0) +fchown(fd, (uid_t)-1, st_old.st_gid) != 0 # endif ) mch_setperm(file_name, (perm 0707) | ((perm 07) 3)); -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Vim 7.3a ready for beta testing
On 2010年07月22日 00:03, Matt Wozniski wrote: Please bottom post on this list... I'm reformatting... On Wed, Jul 21, 2010 at 6:05 AM, mikeyaoyaoweiz...@gmail.com wrote: On Jul 21, 5:38 pm, Bram Moolenaarb...@moolenaar.net wrote: Mikeyao (?) wrote: Why not javascript interface ? The code has developed. http://www.vim.org/scripts/script.php?script_id=2375 I haven't actually heard from someone using it. Also, I have no idea why someone would want to write plugins in Javascript. Perhaps because it's the only language someone knows? Vim support many languages interface and I just found new lua interface added in 7.3. I think most programmers know javascript and like it, it's going to mainstream. Many web developers using vim, they know javascript well. I haven't tried the JS interface patch, but I definitely would like to see a javascript interface. I don't know Lua, TCL or Ruby (though I intend to learn the latter one day), I don't like to use Perl or Python for anything more than a few dozen lines, and I hate Scheme almost as much as Lisp. Javascript is a powerful, easy to learn, multi-paradigm language that was designed for embedding, so I think it's a perfect fit for a Vim interface - and I personally would be more likely to use it than any of the other interfaces. if_v8 is a bit different from other if_*. It is not written as patch for mainline. My main goal of if_v8 plugin is to create a pluggable extension and to find what is required and what is good way for it. -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
patch for doc/editing.txt
Attached patch is for a fix to doc/editing.txt, under :help :X, regarding the file magic lines. At least some versions of the file command allow you to add personal, custom magic lines to ~/.magic as well, but I didn't add that to help file. - Christian -- Christian J. Robinson hept...@gmail.com -- http://christianrobinson.name/ -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php editing.txt-diff Description: Binary data
[patch] Support parallel make for html docs
Bram, The runtime/doc makefile doesn't express the required tags.ref pre-requisite for building the html files using makehtml.awk. When doing a parallel make, this can result in some of the html files not containing all the links that they should since tags.ref may not be generated yet. Attached patch adds the pre-requisite. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@jamessan.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php html-doc.diff Description: Binary data
Re: Color code my Vi Editor
Many thanks for your replies! I am working at a big corporation and the IT-powers that be have access to most root level modifications. I have read/write permissions on my home directory (/home/myName). Could I install the vim editor under my directory? If so, any pointers on what to do? Once downloaded is there a script I can run that'd perform the installation? Is this what I should download? http://www.vim.org/download.php#unix Thanks again for your help. On Jul 21, 11:25 am, Gary Johnson garyj...@spocom.com wrote: On 2010-07-21, duffman wrote: Hi, I tried to look up information online on this but wasn't able to find anything that worked. I used Vi at my old job and loved the editing features it provided. I've moved to a new place now and I am the only developer here. I logged into a SunOS Unix box (bash shell) and while things work my vi editor looks very bland (no colors schemes and bw) which makes reading and writing code difficult. When I looked up info I found that I have to put the color coding information into my .vimrc file in my home directory. I am in a corporation and under my home /home/myName I don't have a .vimrc file. I found a sample one online that I copied but it didn't have any effect on my vi editor. I also tried syntax on commands by vi said it wasn't recognized by vi. Can anyone please help make my vi editor colorful? The SunOS vi is not Vim, so it does not read ~/.vimrc. Instead, it looks for configuration information in ~/.exrc. I don't think the SunOS vi supports color. (I'll have access to a SunOS machine later today but I don't at the moment.) If you want a colorful vi, you'll have to install some other vi, such as Vim. You can either ask your system administrator to do this for you, or you can build your own Vim, install it in ~/bin, and add ~/bin to your PATH. The best way to get the Vim source these days is to use Mercurial, but you probably don't have Mercurial on that SunOS system, either, so you would have to install that as well. Installing programs such as Mercurial and Vim is not difficult. Let us know if it is feasible for you to do that and we can give you whatever further instructions you might need. Regards, Gary -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: patch for doc/editing.txt
Christian J. Robinson wrote: Attached patch is for a fix to doc/editing.txt, under :help :X, regarding the file magic lines. Thanks! At least some versions of the file command allow you to add personal, custom magic lines to ~/.magic as well, but I didn't add that to help file. Too much information can take the attention away from what the user was looking for. -- TIM:Too late. ARTHUR: What? TIM:There he is! [They all turn,, and see a large white RABBIT lollop a few yards out of the cave. Accompanied by terrifying chord and jarring metallic monster noise.] Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Patch to allow ctermfg or bg values as #rrggbb
On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote: Matt Wozniski wrote: [about a patch to support #rrggbb in a terminal] Where can I find the latest version of this patch? I only see one that is two years old. As Benjamin Haskell noted, I decided to shoot for a vimscript implementation instead of a patch implementation, and wound up with CSApprox instead. You've already committed 9cf38f, which was the last thing that was really missing in making CSApprox perfect, and it turns out it's much easier to do all of the nasty magic that needs to be done in a script than in code, and the result is much more flexible. The down side is that it's a bit slow (as Dominique pointed out), but I have a version in my sandbox that should hopefully help a bit with that. Thanks! -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Vim 7.3a ready for beta testing
Mikeyao wrote: Vim support many languages interface and I just found new lua interface added in 7.3. I think most programmers know javascript and like it, it's going to mainstream. Many web developers using vim, they know javascript well. The reason people write Javascript is because it's the only choice for making applications run in a browser. Otherwise it's not a very good language. I can't think of any good reason to write Vim plugins in Javascript instead of a decent language, such as Python. -- The Law of VIM: For each member b of the possible behaviour space B of program P, there exists a finite time t before which at least one user u in the total user space U of program P will request b becomes a member of the allowed behaviour space B' (B' = B). In other words: Sooner or later everyone wants everything as an option. -- Vince Negri /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Patch to allow ctermfg or bg values as #rrggbb
Matt Wozniski wrote: On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote: Matt Wozniski wrote: [about a patch to support #rrggbb in a terminal] Where can I find the latest version of this patch? Â I only see one that is two years old. As Benjamin Haskell noted, I decided to shoot for a vimscript implementation instead of a patch implementation, and wound up with CSApprox instead. You've already committed 9cf38f, which was the last thing that was really missing in making CSApprox perfect, and it turns out it's much easier to do all of the nasty magic that needs to be done in a script than in code, and the result is much more flexible. The down side is that it's a bit slow (as Dominique pointed out), but I have a version in my sandbox that should hopefully help a bit with that. OK, I'll remove the todo item then. -- Why isn't there mouse-flavored cat food? /// Bram Moolenaar -- b...@moolenaar.net -- 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/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Patch to support horizontal mouse wheel
Björn wrote:
Ok, here is the updated patch. I've renamed the keys as follows:
ScrollWheelUp
ScrollWheelDown
ScrollWheelLeft
ScrollWheelRight
These all scroll the _window_ in the direction indicated. So if I
push UP on my scroll wheel, the window moves up but the lines are
actually scrolled down (this is the most intuitive way of thinking
about scrolling in my opinion). Similarly, dragging my finger to the
LEFT on a laptop's trackpad scrolls the window to the left but the
columns are actually scrolled right.
Looks good to me. With the Ctrl+scrollwheel changes, I was able to test
this by mapping C-ScrollWheel{Up|Down} to ScrollWheel{Left|Right}
and it seems to work fine in both term and GTK2.
The only thing I might change would be the symmetry of using 3 for the
default increment. Maybe 5 or 10 would be better for horizontal
scrolling? (With the default, horizontal scrolling seems much slower
than vertical scrolling.)
I increased the default number of lines to scroll to 6 -- any higher
and it was difficult to just scroll a little (with my track pad).
The docs have also been updated to reflect this.
It is still possible to use MouseUp as a synonym for
ScrollWheelDown, and to use MouseDown as a synonym for
ScrollWheelUp. I've updated all the help docs to reflect these
changes.
The new list of the default keys seems very cluttered with the tags
listed all on one line. The old layout also had the benefit of ':help
S-MouseUp', etc. jumping to exactly the right line.
Sure, I tried changing it back and it seems a bit more readable that way.
The attached patch contains these minor updates.
Bram: could you indicate if there is any chance this is making it for
7.3 (or at all)? It seems this feature would mostly be used by Mac
users (since all Macs have horizontal scrolling abilities) and a few
users have asked for this feature. If you'd rather hold off merging
this patch I'll merge it with the MacVim source code so that it gets
tested properly and then you can take a look at it later.
It looks fairly good. It's a bit big to include at the last moment,
but we still have some time for testing.
Can you change the argument for the direction to use an enum or #defined
value? Using 0, 1, -1 and -2 is a bit confusing.
For style, instead of:
if (val 0) val = 0;
use:
if (val 0)
val = 0;
gui_find_longest_lnum() is missing a prototype.
--
If cars evolved at the same rate as computers have, they'd cost five euro,
run for a year on a couple of liters of petrol, and explode once a day.
/// Bram Moolenaar -- b...@moolenaar.net -- 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///
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
2010/7/21 Bram Moolenaar b...@moolenaar.net: Maxim Kim wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times to reach strwidth() function and l to go back. The line widens and shrinks. PS If I run gvim with -u NORC and do all above with set nocp first -- everything is ok. I can't reproduce it. There were a few recent changes in this area. Do you still see the problem if you build from the current Mercurial version? I have just compiled vim -- there is no such problem in the current Mercurial version. Maxim. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Compilation issues with revision 2368:435b5c6a5191
GVim fails to compile with revision 2368:435b5c6a5191 under MinGW: if_ole.cpp: In static member function 'static CVim* CVim::Create(int*)': if_ole.cpp:144:19: error: cannot allocate an object of abstract type 'CVim' if_ole.cpp:97:1: note: because the following virtual functions are pure within 'CVim': c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/oaidl.h:484:2: note: virtual HRESULT IDispatch::GetIDsOfNames(IID*, WCHAR**, UINT, LCID, DISPID*) c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/oaidl.h:485:2: note: virtual HRESULT IDispatch::Invoke(DISPID, IID*, LCID, WORD, DISPPARAMS*, VARIANT*, EXCEPINFO*, UINT*) if_ole.cpp:152:54: error: cannot convert 'const IID' to '_GUID*' for argument '1' to 'HRESULT LoadRegTypeLib(_GUID*, WORD, WORD, LCID, ITypeLib**)' if_ole.cpp:177:51: error: cannot convert 'const IID' to '_GUID*' for argument '1' to 'HRESULT LoadRegTypeLib(_GUID*, WORD, WORD, LCID, ITypeLib**)' if_ole.cpp:189:53: error: no matching function for call to 'ITypeLib::GetTypeInfoOfGuid(const IID, ITypeInfo**)' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/oaidl.h:628:2: note: candidate is: virtual HRESULT ITypeLib::GetTypeInfoOfGuid(_GUID*, ITypeInfo**) if_ole.cpp: In member function 'virtual HRESULT CVim::QueryInterface(IID*, void**)': if_ole.cpp:215:9: error: cannot convert 'const IID' to '_GUID*' for argument '2' to 'BOOL IsEqualGUID(_GUID*, _GUID*)' if_ole.cpp:215:43: error: cannot convert 'const IID' to '_GUID*' for argument '2' to 'BOOL IsEqualGUID(_GUID*, _GUID*)' if_ole.cpp:215:78: error: cannot convert 'const IID' to '_GUID*' for argument '2' to 'BOOL IsEqualGUID(_GUID*, _GUID*)' if_ole.cpp: In member function 'virtual HRESULT CVimCF::QueryInterface(IID*, void**)': if_ole.cpp:466:9: error: cannot convert 'const IID' to '_GUID*' for argument '2' to 'BOOL IsEqualGUID(_GUID*, _GUID*)' if_ole.cpp:466:43: error: cannot convert 'const IID' to '_GUID*' for argument '2' to 'BOOL IsEqualGUID(_GUID*, _GUID*)' if_ole.cpp: In function 'void UnregisterMe(int)': if_ole.cpp:597:9: error: cannot convert 'const IID' to '_GUID*' for argument '1' to 'HRESULT LoadRegTypeLib(_GUID*, WORD, WORD, LCID, ITypeLib**)' if_ole.cpp:603:33: error: cannot convert 'GUID' to '_GUID*' for argument '1' to 'HRESULT UnRegisterTypeLib(_GUID*, WORD, WORD, LCID, SYSKIND)' if_ole.cpp: In function 'void GUIDtochar(const GUID, char*, int)': if_ole.cpp:638:33: error: cannot convert 'const GUID' to 'CLSID*' for argument '1' to 'HRESULT StringFromCLSID(CLSID*, WCHAR**)' if_ole.cpp: In function 'void InitOLE(int*)': if_ole.cpp:741:8: error: cannot convert 'const IID' to 'CLSID*' for argument '1' to 'HRESULT CoRegisterClassObject(CLSID*, IUnknown*, DWORD, DWORD, DWORD*)' if_ole.cpp:754:9: error: cannot convert 'const IID' to 'CLSID*' for argument '2' to 'HRESULT RegisterActiveObject(IUnknown*, CLSID*, DWORD, DWORD*)' make: *** [gobj/if_ole.o] Error 1 Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim73a help -- bug of feature?
On Wed, 21 Jul 2010, Maxim Kim wrote: Christian J. Robinson wrote: Maxim Kim wrote: 3. :syntax on Sorry, I missed that somehow. But you'd also need to turn filetype plugins on (:filetype plugin on). The help ftplugin sets 'concellevel'. Cut from the top post: 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times to reach strwidth() function and l to go Looks like I'm in fine form today. :( I guess I'll just bow out of this conversation now. - Christian -- Christian J. Robinson hept...@gmail.com -- http://christianrobinson.name/ -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Patch to support horizontal mouse wheel
On 21 July 2010 21:36, Bram Moolenaar wrote: Björn wrote: Bram: could you indicate if there is any chance this is making it for 7.3 (or at all)? It seems this feature would mostly be used by Mac users (since all Macs have horizontal scrolling abilities) and a few users have asked for this feature. If you'd rather hold off merging this patch I'll merge it with the MacVim source code so that it gets tested properly and then you can take a look at it later. It looks fairly good. It's a bit big to include at the last moment, but we still have some time for testing. Can you change the argument for the direction to use an enum or #defined value? Using 0, 1, -1 and -2 is a bit confusing. Agreed. I did this since I wasn't sure where to add the #define's. They are at the end of vim.h now, hope that makes sense (it seemed standard to use a shortened version of the function where the #define is used as a prefix so I called them MSCR_*). For style, instead of: if (val 0) val = 0; use: if (val 0) val = 0; gui_find_longest_lnum() is missing a prototype. Ok, I have addressed these two issues as well. The attached patch should be applied after the other three. I sent it as a separate patch instead of merging it with the others to make it easier to see what changes I made this time around. Björn -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php 0001-Address-Bram-s-comments.patch Description: Binary data
Re: Dynamic loading for Perl
On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar b...@moolenaar.net wrote: We could wait for people to test this, but on the other hand if we want to do the same for ruby/tcl/mzscheme we need to do it now, next week I won't include patches like this. It broke compiling using Make_cyg.mak for me. (Just to be sure I did an hg update -C.) % hg summary parent: 2369:454f314d0e61 tip Make it possible to load Perl dynamically on Unix. (James Vega) branch: vim73 commit: 4 modified, 9 unknown update: (current) % make -f Make_cyg.mak PERL=/cygdrive/c/strawberry/perl DYNAMIC_PERL=yes OLE=yes FEATURES=BIG gcc-3 -c -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl512.dll\ -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto -I/cygdrive/c/strawberry/perl/lib/CORE -s -mno-cygwin if_perl.c -o gobj/if_perl.o if_perl.xs:101:19: dlfcn.h: No such file or directory if_perl.xs: In function `perl_runtime_link_init': if_perl.xs:450: error: `RTLD_LAZY' undeclared (first use in this function) if_perl.xs:450: error: (Each undeclared identifier is reported only once if_perl.xs:450: error: for each function it appears in.) if_perl.xs:450: error: `RTLD_GLOBAL' undeclared (first use in this function) if_perl.xs:450: warning: assignment makes pointer from integer without a cast if_perl.xs:459: warning: assignment makes pointer from integer without a cast make: *** [gobj/if_perl.o] Error 1 - Christian -- Christian J. Robinson hept...@gmail.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Dynamic loading for Perl
On 21/07/10 22:08, Bram Moolenaar wrote: James Vega wrote: On Mon, Jul 19, 2010 at 3:17 PM, Bram Moolenaarb...@moolenaar.net wrote: If you can make this work with a configure argument, it's fine to include these changes and leave them disabled by default. For your distribution, with a known environment, you could enable them. Attached patch enables dynamic loading for Perl if --enable-perlinterp=dynamic is used. I also moved the use of PERL_CFLAGS in src/Makefile so they're only used when compiling if_perl.c and if_perlsfio.c. Looks good. I tried it and it works fine for me. I had to move some unused variables inside an #ifdef. I suppose it will now be easy to support --enable-pythoninterp=dynamic and --enable-python3interp=dynamic We could wait for people to test this, but on the other hand if we want to do the same for ruby/tcl/mzscheme we need to do it now, next week I won't include patches like this. Hm, just for my edification, what will happen if an older version of configure encounters --enable-pythoninterp=dynamic ? treat as =yes (or empty) treat as =no (or --disable-pythoninterp) throw an error and stop the make at that point (or if not run by make, exit with nonzero exitcode) ? Best regards, Tony. -- If you can count your money, you don't have a billion dollars. -- J. Paul Getty -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Color code my Vi Editor
On Jul 21, 1:17 pm, duffman samarthsangh...@gmail.com wrote: Many thanks for your replies! I am working at a big corporation and the IT-powers that be have access to most root level modifications. I have read/write permissions on my home directory (/home/myName). Could I install the vim editor under my directory? If so, any pointers on what to do? Once downloaded is there a script I can run that'd perform the installation? Is this what I should download?http://www.vim.org/download.php#unix Thanks again for your help. Please bottom-post to this list. Yes, it is perfectly possible to compile and run Vim from your home directory, if you have the space available for it (you probably do). The link you give will work, but it can be easier to get a fully up-to- date version, with all bugfixes, using the Mercurial repository. See http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial You will then need to compile the source code which you have downloaded. See http://vim.wikia.com/wiki/Building_Vim After compiling the source code, you should be able to just run Vim from the location in which it resides. Setting up aliases will probably be helpful for this. Before trying any of this, it may behoove you to see if 'vim' is already installed. Instead of 'vi file.blah' type 'vim file.blah' and see if it works. Or just type 'which vim' to see if it finds anything. Of course, another option is to as the IT-powers to upgrade your Vim version. Or, install Vim on your normal workstation...it runs great on most operating systems out there. You can even get a GUI-enabled Vim (gvim) that way. See http://vim.wikia.com/wiki/Download You did not specify, did you log onto this SunOS station directly, or via a remote terminal like PuTTY? There are some tricks you may need to do to get color working properly in this situation, even after you get a real Vim running. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Dynamic loading for Perl
On Wed, Jul 21, 2010 at 4:58 PM, Christian J. Robinson hept...@gmail.com wrote: On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar b...@moolenaar.net wrote: We could wait for people to test this, but on the other hand if we want to do the same for ruby/tcl/mzscheme we need to do it now, next week I won't include patches like this. It broke compiling using Make_cyg.mak for me. (Just to be sure I did an hg update -C.) Oops. Looks like I was using the wrong building on Windows check. The attached patch should fix it, as that's what the Python modules are using. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@jamessan.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php win-perl.diff Description: Binary data
Re: Dynamic loading for Perl
On Wed, Jul 21, 2010 at 5:05 PM, Tony Mechelynck antoine.mechely...@gmail.com wrote: On 21/07/10 22:08, Bram Moolenaar wrote: James Vega wrote: On Mon, Jul 19, 2010 at 3:17 PM, Bram Moolenaarb...@moolenaar.net wrote: If you can make this work with a configure argument, it's fine to include these changes and leave them disabled by default. For your distribution, with a known environment, you could enable them. Attached patch enables dynamic loading for Perl if --enable-perlinterp=dynamic is used. I also moved the use of PERL_CFLAGS in src/Makefile so they're only used when compiling if_perl.c and if_perlsfio.c. Looks good. I tried it and it works fine for me. I had to move some unused variables inside an #ifdef. I suppose it will now be easy to support --enable-pythoninterp=dynamic and --enable-python3interp=dynamic We could wait for people to test this, but on the other hand if we want to do the same for ruby/tcl/mzscheme we need to do it now, next week I won't include patches like this. Hm, just for my edification, what will happen if an older version of configure encounters --enable-pythoninterp=dynamic ? treat as =yes (or empty) treat as =no (or --disable-pythoninterp) throw an error and stop the make at that point (or if not run by make, exit with nonzero exitcode) The configure script currently only tries to build the python/python3 interfaces if --enable-pythoninterp=yes is given (--enable-pythoninterp with no arguments is the same as specifying =yes). Anything else is treated as =no. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@jamessan.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Dynamic loading for Perl
On Wed, Jul 21, 2010 at 3:41 PM, James Vega james...@jamessan.com wrote: On Wed, Jul 21, 2010 at 4:58 PM, Christian J. Robinson hept...@gmail.com wrote: On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar b...@moolenaar.net wrote: We could wait for people to test this, but on the other hand if we want to do the same for ruby/tcl/mzscheme we need to do it now, next week I won't include patches like this. It broke compiling using Make_cyg.mak for me. (Just to be sure I did an hg update -C.) Oops. Looks like I was using the wrong building on Windows check. The attached patch should fix it, as that's what the Python modules are using. Yes, this fixed it. Thank you. -- Christian J. Robinson hept...@gmail.com -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Color code my Vi Editor
On 21/07/10 20:35, Dominique Pellé wrote: duffman wrote: Many thanks for your replies! I am working at a big corporation and the IT-powers that be have access to most root level modifications. I have read/write permissions on my home directory (/home/myName). Could I install the vim editor under my directory? If so, any pointers on what to do? Once downloaded is there a script I can run that'd perform the installation? Is this what I should download? http://www.vim.org/download.php#unix Thanks again for your help. Hi You can certainly install vim without root access. I'm in the same exact same situation at work. Here is how you can install Vim from sources: # Create a directory where to put your installed software $ mkdir ~/opt # Create a directory where to put source codes which you download $ mkdir ~/sb $ cd ~/sb # Download sources. I recommend using Mercurial, which you may # have to install if not available, again, no need to be root. $ hg clone https://vim.googlecode.com/hg/ vim $ cd vim # Configure Vim. You need to pass the --prefix option since # you don't have root access (or else it would try to install Vim # in /usr/local/... where you don't have permission) $ ./configure --with-features=huge --prefix=$HOME/opt # Compile Vim $ make # Install Vim (this will install Vim files into $HOME/opt/...) $ make install Then edit your ~/.bashrc (or ~/.cshrc, depending on your shell) to add $HOME/opt/bin into your PATH. That's it. You may try ./configure --help to see what other options are available when running the configure script. The way to install Vim from sources is the same as for most other softwares on Unix: Another solution is to ask root to install Vim. A good Unix administrator should always install Vim :-) PS1: please bottom post when posting to this mailing list PS2: this question was more suitable for the vim_use mailing list (vim_dev is for the development of Vim). -- Dominique See also: http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial http://users.skynet.be/antoine.mechelynck/vim/compunix.htm and in order to install Vim into subdirectories of $HOME/opt/ as above by using the method described in compunix.htm you'll need to include the following as part of the configuration-setting script to be sourced: export CONF_ARGS=--prefix=$HOME/opt and make sure (with this example) that $HOME/opt/bin exists and is in your $PATH. If Dominique hadn't recommended something else, I might have just suggested --prefix=$HOME which would have put: the Vim executable at $HOME/bin/vim the runtime files at $HOME/share/vim/vim72 (Vim 7.2) or at $HOME/share/vim/vim73b (Vim 7.3b) and searched user scripts under $HOME/share/vim/vimfiles/ and under $HOME/.vim/ With $HOME/opt intead, $HOME/.vim stays there and all the rest move to $HOME/opt/bin/ and to subdirs of $HOME/opt/share/. Note that you can only set one $CONF_ARGS variable of course; if you have several arguments to set by means of it, put them space-separated into a single value. (For some arguments, as shown in my conpunix.htm HowTo page, there are separate environment variables). Best regards, Tony. -- When a Banker jumps out of a window, jump after him -- that's where the money is. -- Robespierre -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Wrong reference to netrw.vim in autocmd.txt
I just noticed that autocmd.txt references $VIMRUNTIME/plugin/netrw.vim which doesn't exist. This is with the latest Vim 7.3 from the mercurial repository (I upgraded to check this, the upgrade from 7.2 - 7.3 went flawless BTW thanks to http://www.vim.org/mercurial.php). I guess the filename should be netrwPlugin.vim instead? Attached is a patch that fixes this. - Peter Odding -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php diff -r e95106e347f6 runtime/doc/autocmd.txt --- a/runtime/doc/autocmd.txt Wed Jul 21 22:27:37 2010 +0200 +++ b/runtime/doc/autocmd.txt Thu Jul 22 02:31:46 2010 +0200 @@ -1280,7 +1280,7 @@ that reads/writes the file. The |v:cmdbang| variable is one when ! was used, zero otherwise. -See the $VIMRUNTIME/plugin/netrw.vim for examples. +See the $VIMRUNTIME/plugin/netrwPlugin.vim for examples. == 11. Disabling autocommands*autocmd-disable*
Compiling vim7.3b failed on Win XP with MinGW
I'm getting the following error: ... gcc ... if_perl.c -o gobjZ/if_perl.o if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory compilation terminated. make: *** [gobjZ/if_perl.o] Error 1 Many thanks in advance, -- Cesar -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Compiling vim7.3b failed on Win XP with MinGW
On 22/07/10 02:50, Cesar Romani wrote: I'm getting the following error: ... gcc ... if_perl.c -o gobjZ/if_perl.o if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory compilation terminated. make: *** [gobjZ/if_perl.o] Error 1 Many thanks in advance, IIRC, you're the third one mentioning this today (well, or yesterday depending on timezone). A fix has been posted on the list and I expect it soon on the Mercurial server. Bet regards, Tony. -- BRIDGEKEEPER: What is your favorite colour? LAUNCELOT:Blue. BRIDGEKEEPER: Right. Off you go. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Compiling vim7.3b failed on Win XP with MinGW
On 22/07/10 02:50, Cesar Romani wrote: I'm getting the following error: ... gcc ... if_perl.c -o gobjZ/if_perl.o if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory compilation terminated. make: *** [gobjZ/if_perl.o] Error 1 Many thanks in advance, P.S. Dynamic loading for Perl by James Vega, Wed, 21 Jul 2010 17:41:07 -0400. Best regards, Tony. -- The State of California has no business subsidizing intellectual curiosity. -- Ronald Reagan -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
syntax/vim.vim sources syntax/perl.vim which may set fdm=syntax
I just noticed that my 'foldmethod' is getting set to syntax when editing Vim script files, but the syntax/vim.vim file doesn't set that option even if you've enabled syntax folding for Vim code. Since I have let perl_fold=1 in my vimrc, I get this when I do :verbose set fdm? while in a Vim script buffer: foldmethod=syntax Last set from [...]/vim/vim73b/syntax/perl.vim It's not really a problem for me, considering it has taken what has probably been years to notice I hadn't set this in my ~/.vim/ftplugin/vim.vim file. I probably would have done so if it hadn't been done for me, but I'd definitely call this an unintended consequence of having the vim.vim syntax file include the perl.vim syntax file. - Christian -- Christian J. Robinson hept...@gmail.com -- http://christianrobinson.name/ -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: syntax/vim.vim sources syntax/perl.vim which may set fdm=syntax
On 22/07/10 04:35, Christian J. Robinson wrote: I just noticed that my 'foldmethod' is getting set to syntax when editing Vim script files, but the syntax/vim.vim file doesn't set that option even if you've enabled syntax folding for Vim code. Since I have let perl_fold=1 in my vimrc, I get this when I do :verbose set fdm? while in a Vim script buffer: foldmethod=syntax Last set from [...]/vim/vim73b/syntax/perl.vim It's not really a problem for me, considering it has taken what has probably been years to notice I hadn't set this in my ~/.vim/ftplugin/vim.vim file. I probably would have done so if it hadn't been done for me, but I'd definitely call this an unintended consequence of having the vim.vim syntax file include the perl.vim syntax file. - Christian I'm not sure it's unintended: if your vim script includes a Perl here-document, I suppose that _that_ will be syntax-folded thanks to this statement. OTOH maybe (I'm not sure) setting 'foldmethod' belongs in an ftplugin, not a syntax script, in which case (since neither syntax/vim.vim nor ftplugin/vim.vim sources ftplugin/perl.vim) you wouldn't see it anymore. Note that syntax/perl.vim is well-behaved: what it does at line 57 is :setlocal foldmethod=syntax (not plain :set) so it will only apply to Perl sources and to filetypes which (like Vim scripts) may contain embedded Perl source code. Best rgards, Tony. -- In Tennessee, it is illegal to shoot any game other than whales from a moving automobile. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: syntax/vim.vim sources syntax/perl.vim which may set fdm=syntax
On Thu, Jul 22, 2010 at 04:57:57AM +0200, Tony Mechelynck wrote: Note that syntax/perl.vim is well-behaved: what it does at line 57 is :setlocal foldmethod=syntax (not plain :set) so it will only apply to Perl sources and to filetypes which (like Vim scripts) may contain embedded Perl source code. Almost. The fold options are all either local to window or global, so it will affect any buffer displayed in that window. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@jamessan.com signature.asc Description: Digital signature
Markdown syntax script using the new conceal feature
Hi list, Last night I switched to Vim 7.3 and one of the first things I wanted to try was the new conceal feature. A perfect test subject for me was Markdown text formatting because its goal is to be very readable but its syntax rules kind of get in the way of readability :-) (IMHO). After some late night hacking I now have a ~/.vim/syntax/mkd.vim script which can conceal most of the extra syntax in Markdown texts and I really like it so far. Thanks to everyone who made this possible! I don't know how far the conceal feature is supposed to be pushed (e.g. my syntax script hides full URLs which can more or less span a whole screen line...) but during testing I found that it's not really compatible with the 'wrap' option, at least not unless you like very jagged paragraphs :-( I've attached the syntax script and a test case (a README from one of my Vim plug-ins with a lot of inline hyper links that make the text hard to follow without the conceal feature) for anyone who's interested. These two files could make a good test case for the line wrapping bug, if indeed it is considered a bug and can be fixed with reasonable effort (I suppose if concealing can make full screen lines disappear that might complicate Vim's drawing code significantly...) - Peter Odding syntax spell toplevel setlocal conceallevel=2 runtime! syntax/html.vim # Headings syntax match mkdHeading /^#.*/ contains=mkdCode,mkdInlineLink,mkdRefLink syntax match mkdHeadingMarker /^#\+\s*/ conceal contained containedin=mkdHeading Italic text. syntax region mkdItalic matchgroup=mkdMarker start=/\\\@!\*/ end=/\\\@!\*/ concealends Bold text. syntax region mkdBold matchgroup=mkdMarker start=/\\\@!\*\*/ end=/\\\@!\*\*/ concealends Inline `code` fragments. syntax region mkdCode matchgroup=mkdMarker start=/\\\@!`/ end=/\\\@!`/ concealends Pre-formatted code blocks. syntax match mkdCodeBlock /\(\_^.*\)\+/ contai...@nospell literal-link-syntax syntax match mkdLiteralLink !\(\w\+://[^]\+\|[^ \t\n@]...@[^ \t\n]\+\)! contai...@nospell syntax match mkdLiteralLinkMarker /[]/ conceal contained containedin=mkdLiteralLink [inline](link://syntax) syntax match mkdInlineLink /\[\_[^\]]\+]([^)]\+)/ syntax match mkdInlineLinkLabel /\[\@=\_[^\]]\...@=/ contained containedin=mkdInlineLink contai...@nospell syntax match mkdInlineLinkTarget /(\@=[^)]\+)\...@=/ contained containedin=mkdInlineLinkEnd contai...@nospell syntax match mkdInlineLinkStart /\[/ conceal contained containedin=mkdInlineLink syntax match mkdInlineLinkEnd /]([^)]\+)/ conceal contained containedin=mkdInlineLink [reference][link-syntax] syntax match mkdRefLink /\[\_[^\]]\+]\s*\[[^\]]\+]/ syntax match mkdRefLinkLabel /\[\@=\_[^\]]\+\%(]\s*\[\)\...@=/ contained containedin=mkdRefLink contai...@nospell syntax match mkdRefLinkName /\%(]\s*\[\)\@=[^\]]\...@=/ contained containedin=mkdRefLinkEnd contai...@nospell syntax match mkdRefLinkStart /\[/ conceal contained containedin=mkdRefLink syntax match mkdRefLinkEnd /]\s*\[[^\]]\+]/ conceal contained containedin=mkdRefLink [reference]: definitions syntax match mkdRefDef /^\[[^\]]\+]:\s\+.*/ syntax match mkdRefDefName /\(^\[\)\@=[^\]]\...@=/ contained containedin=mkdRefDef contai...@nospell syntax match mkdRefDefTarget /\(]:\s*\)\@=.*/ contained containedin=mkdRefDef contai...@nospell syntax match mkdRefDefStart /^\[/ conceal contained containedin=mkdRefDef syntax match mkdRefDefDelim /]:\...@=/ conceal contained containedin=mkdRefDef The ability to do this is awesome :-) syntax match mkdLessThan /lt;/ conceal cchar= syntax match mkdGreaterThan /gt;/ conceal cchar= syntax match mkdAmpersand /amp;/ conceal cchar= syntax match mkdBullet /\(^\s*\)\@=[-*+]/ conceal cchar=⢠highlight link mkdBullet Comment Default highlighting styles. highlight link mkdBold htmlBold highlight link mkdCode String highlight link mkdCodeBlock String highlight link mkdHeading Title highlight link mkdHeadingMarker Comment highlight link mkdInlineLinkLabel Underlined highlight link mkdInlineLinkTarget String highlight link mkdItalic htmlItalic highlight link mkdLiteralLink Underlined highlight link mkdMarker Comment highlight link mkdRefDefName String highlight link mkdRefDefTarget Underlined highlight link mkdRefLinkLabel Underlined highlight link mkdRefLinkName String I know this is a hack but I *really* don't like the default highlighting of concealed text, which isn't gui=standout but it sure does stand out! highlight Conceal guifg=fg guibg=bg let b:current_syntax = mkd # Automatic reloading of Vim scripts The [reload.vim][reload] plug-in automatically reloads various types of [Vim][vim] scripts as they're being edited in Vim to give you instant feedback on the changes you make. For example while writing a Vim syntax script you can open a split window of the relevant file type and every time you [:update][update] your syntax script, [reload.vim][reload] will refresh the syntax highlighting in the split window.
