Re: RFE: support POSIX standard and developing RE's

LCD 47 wrote: On 15 April 2016, Erik Christiansen wrote: On 14.04.16 14:40, Christian Brabandt wrote: Am 2016-04-14 12:14, schrieb Erik Christiansen: So many unix utilities support POSIX "Modern" EREs, that it is the best standard to conform to.

Re: Bug: (was vimscripting problem w/tabs and expanding width w/numbering option)

Christian Brabandt wrote: Hi Linda! Using WinEnter and VimEnter autocommands worked for me: if !exists(g:autocommands_loaded) let g:autocommands_loaded =1 au VimEnter,WinEnter * let ln = line('\) | if search(vim=:SetNumberAndWidth,'n') | call SetNumberAndWidth() | endif endif

Re: Bug: (was vimscripting problem w/tabs and expanding width w/numbering option)

Linda W wrote: You would know, last minute cleanup I introduce a bug. So lame... Sorry, (had taken out a needed flag setting): Here it is again (probably too many times for some)...*sigh*... gvim.shh: #!/bin/bash -u #include stdalias shopt -s expand_aliases alias my=declare string=declare

Re: Bug: (was vimscripting problem w/tabs and expanding width w/numbering option)

Christian Brabandt wrote: That looks strange indeed. I would suggest to postpone the resizing until Vim has started up completely. Since there are some checks in the Code that postpone processing, if Vim is starting. How do I do that in a gvimrc? Also you might want to consider to

Re: Bug? (was vimscripting problem w/tabs and expanding width w/numbering option)

Christian Brabandt wrote: I haven't followed closely. Can you please provide a clear example that exhibits the wrong behaviour when starting from gvim -u myfile -N and also explain what you expect and what you see instead? Best, Christian In myvimrc add: func! SetNumberAndWidth() set number

Re: gvim not showing unicode Devanagari - Hindi text

V S Rawat wrote: My gvim, vim 7.4 on w8 is not showing unicode Devanagari - Hindi text. What to do? Use the Cygwin version. I just tried the Siddhanta font: Info: Siddhanta font by Mihail Bayaryn is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License -

Re: vimscripting problem w/tabs and expanding width w/numbering option

Ben Fritz wrote: On Sunday, February 8, 2015 at 5:59:28 PM UTC-6, L. A. Walsh wrote: It sorta looks like both tabs are being brought up at the same time and a race condition might be happening, but the fact that it is very deterministic, leads me to believe something else is going on.

Re: Trying to tabline in GUI: not working fontchange broken

Jacky Liu wrote: On Monday, February 9, 2015 at 10:36:21 AM UTC+8, Jacky Liu wrote: you can make vim use the terminal style tabline though, by doing 'set guioptions-=e', but the 'TabLine...' hi groups still have no effect, at least not on my computer. They were meant for console vim, not gvim,

Re: Trying to tabline in GUI: not working fontchange broken

toothpik wrote: I'm using version 7.3.831 (because last I tried 7.4, everything was noticeable slowed down due to the new regex engine. So I just stayed at 7.3 for the nonce. are you aware there's an option to use the old engine if you so desire? see :h 'regexpengine' in

Re: 7.4 syntax matching seems noticable slower than 7.3

Павлов Николай Александрович wrote: Check out the 're' option and related documentation. Your problems may be and are likely caused by the new regular expression engine. You may still force Vim to use the old one though. Thanks for the tip!. -- -- You received this message from the

Re: RFE: honor 'eol' setting regardless of 'binary' flag.

Tim Chase wrote: Take Christian's advice: just put set binary in your vimrc and be done with it. Anything more is just trolling the list. --- set binary changes other settings that I don't want changed: The following options will be ignored: textwidth, wrapmargin, modeline, expandtab,

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: It seems like there is too much confusion about the terms. I just want to make it clear with obvious examples because describing it with words seems to only worsen the confusion. `gcc vim.o python33.dll -o vim` is linking `vim` against `python33.dll` at compile time,

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: They are not already there. One still has to do some work to enable all these languages. One needs some of their header files to be built with Vim. So one have to get some version of their distribution and compile their headers (and sometimes some other stuff) with

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: Dear Linda, It feels like Perl is not very trendy these days. Trendy? How _trendy_ is international support? International and perl support were the first things to be provided as optional modules not because they were trendy, but considered essential. Perl is

Re: Vim for Windows (Updated to 7.4.193)

tooth pik wrote: I tried searching for vim plugins and scripts and adjuncts on search.cpan.org. I came up with about 270 hits. Among those are things that provide vim functionality to create IDE's debuggers, packages, use for wiki creation to do LaTex typesetting from vim, website

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: I'm afraid you overextended the topic. Now, let's try to filter what you've presented with a cool head. I've never said Perl is bad or anything like that. I don't think I claimed you said that -- you said it wasn't trendy. I Every language has its own niche.

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: I'm NOT linking shared libraries of side languages to Vim. They are loaded dynamically on demand and if appropriate versions of them are present on your machine. There are no explicit dependencies of my Vim distribution to any of third party shared libraries.

Re: Vim for Windows (Updated to 7.4.193)

Alexander Shukaev wrote: Hey everyone, Vim for Windows [https://bitbucket.org/Haroogan/vim-for-windows] has been updated to 7.4.193. Starting from this release, the support for the latest Lua (5.2) has been included. Um... you seemed to have missed including perl all-together. You

Syntax Coloring seems to not scan Folded sections correctly.

I have seen this in more than one place, where a section of code has a long text literal (150-200 characters) in single quotes. The text after the fold is colored as quoted -- even though it isn't. If the fold is opened, it parses normally. I was unable to get any resync using Control-L.

Re: Building on Windows for both 32 and 64-bit installs

Ben Fritz wrote: But this is Windows. There is no shadow target in either the MinGW makefile, or the Visual Studio; Don't the shadow dirs just create a real dir copy and use hard links for the files (or do they use symlinks). Eitherway, Windows NT supports hard links going back to

Re: vim -d(iff) file1 file2 -- diff args?

On 2013-11-15 21:25, Nikolay Pavlov wrote: On Nov 16, 2013 9:17 AM, Linda W v...@tlinx.org mailto:v...@tlinx.org wrote: in mgdiff, you can specify a mgdiff --args -w... file1 file2 to allow you to pass most args you'd want to mgdiff. :h 'diffopt'. You can use -c 'set diffopt+=iwhite

vim -d(iff) file1 file2 -- diff args?

in mgdiff, you can specify a mgdiff --args -w... file1 file2 to allow you to pass most args you'd want to mgdiff. Is there something similar with vim? Like sometimes I'd like it to ignore differences in whitespace as an example. Thanks or RFE? -- -- You received this message from the

Re: Unix vim running dos files

Tony Mechelynck wrote: On 28/08/13 18:27, Philip Piper wrote: Is it standard behavior that vim on my debian install can not run DOS plugins that I download without me converting said plugins to unix fileformat? The screenshot is after trying open vim after install Unite through pathogen.

Re: Match all characters enclosed in brackets

Tim Chase wrote: On 2013-08-09 00:46, rameo wrote: I have trouble finding the correct regex. I know that a sequence of characters enclosed in brackets means their optional: [xyz] means any 'x' OR 'y' OR 'z' but how can I find them all? any 'x' AND 'y' AND 'z' in whatever sequence and

Re: compiling gvim statically

kamaraju kusumanchi wrote: I am trying to compile a static version of gvim on a machine running a combination of Debian GNU/Linux Squeeze and Wheezy. (.text+0xe12): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc

Re: Official petition for Bram Moolenaar to become a front end developer

Andrew Ray wrote: Bram clearly writes a lot of C code. The only indent Vim has built in by default is cindent (did this come from vi? I don't know). But, times have changed. Developers now write a lot of javascript and html. Vim is not so good at javascript and html. Indenting, for example,

Gvim starting up in C:\temp??

Ben Fritz wrote: I've never seen that problem, and I use shellslash in my config. Does it work with launching Vim as follows? gvim -N -u NONE -U NONE -i NONE --cmd set shellslash fb17X/content/firebug/chrome.js I know that the 'shellslash' option can make shellescape() do bad things on

Re: Gvim starting up in C:\temp??

John Little wrote: On Friday, July 26, 2013 7:48:20 AM UTC+12, Linda W wrote: Why is it in C:\tmp? (when I started in my home dir/profiledir). See :help 'directory' Regards, John Little But normally I see it open the file in the same directory as the file to edit. The problem here

Re: Bug in opening partial path on windows (using '/' instead of '\'

Ben Fritz wrote: I've never seen that problem, and I use shellslash in my config. Does it work with launching Vim as follows? gvim -N -u NONE -U NONE -i NONE --cmd set shellslash fb17X/content/firebug/chrome.js I know that the 'shellslash' option can make shellescape() do bad things on

Bug in opening partial path on windows (using '/' instead of '\'

I set the 'shellslash' option so vim would know I'm using a unix-like shell, but it doesn't help. When I am in a subdirectory ... pwd|tr / \n|wc 10 9 75 10 levels deep, and am editing another file: gvim fb17X/content/firebug/chrome.js I end up with

Bug with (or without) 'Z' in cpoptions writing to read-only file

This used to work, but stopped about 18 months ago, I think. Now, I've both with 'Z' and without in cpoptions, but notice when I write a file with w!, the read-only flag is still being reset to it's initial state. Has anyone else noticed this? It's very annoying. -- -- You received this

Re: Bug with (or without) 'Z' in cpoptions writing to read-only file

Linda W wrote: This used to work, but stopped about 18 months ago, I think. Now, I've both with 'Z' and without in cpoptions, but notice when I write a file with w!, the read-only flag is still being reset to it's initial state. I have figured out at least one place that causes

Re: Bug with (or without) 'Z' in cpoptions writing to read-only file

Linda W wrote: Trouble is, with examples like that in the official Vim code, there's no telling where else it might be a problem. --- Actually, I guess one can tell how many places it is broken: ./autoload/getscript.vim:30:set cpovim ./autoload/getscript.vim:183: set ei=all hlsvim noacd

Anyone know anything about vim debugger?

I am trying the vim debugger for the first time and Tried running it to debug a perl program. My code was in my 'bin' directory and I needed to have it operate in a different directory where the data was. So in vim, I 'cd'd to the data dir ... but when I tried to run the debugger, it said no

variable tabstops on your tty (linux, vt100/102/200?... similar)?

Seeing the conversation on variable tabs in Vim, thought some might find the attached script of use if they use certain text terms... FWIW, the linux type terminal implements a large subset of the VT102 and ECMA-48/ISO ANSI x4.64 terminal controls... Within this feature set, is the abilty to

is vimdir/syntax/fstab maintained anymore?

Maybe it's just my distro not getting the updates, but the last update for the syntax file for /etc/fstab was 2009. A diff of just the filesystem types I added that are on my system (/proc/filesystems) looks like: diff -u /usr/share/vim/vim73/syntax/fstab.vim.orig

Re: using = 15 POST reqs per 4h? - no but why not insert glue?

Marc Weber wrote: Reason: See vim-dev: vim.sf.net was scanned by a bot testing for vulnerabilities. Most vulnerabilities require to store JS code in fields, or creating new users etc. For this reason I assumed that a causual user does only update 5 plugins in one session + logging in.

Re: Running Indent in a Cygwin Shell from GVim

Gary Johnson wrote: On 2013-05-02, Waters, Bill wrote: I think that the root of the problem is that in the shell from GVim the file is getting treated as binary instead of text. Not sure how to fix that. No... I'll be it's in the files he is indenting. His vim -- especially

Re: How can one set tabstops to specific values?

Tony Mechelynck wrote: IMHO using variable *hard* tabs is courting disaster, because most other programs (including printers, and the Python interpreter) always use fixed hard tabs every 8 columns. But my terminal uses '2' for a tabstop (linux console is programmable for tabstops

How can one set tabstops to specific values?

I'd like to be able to set tabstops in various files to useful values like in /etc/fstab set ts=17,17,8,24,3 With the last tabstop repeated for the width of the line... I've seen this in other editors and even the linux-console has this ability -- so how can I setvim to produce tabstops for

clicking to open folds in Gui?

Is there an option or .vim addon that would allow me to click on the plus of a folded section and have it expand it? Closing might not be as intuitive -- if using fold method marker (#{{{1), maybe clicking on that marker would close it? It's just that I saw the + there on a fold and it

Re: clicking to open folds in Gui?

Ben Fritz wrote: I think you're looking for the 'foldcolumn' option. Clicking the + or - in the column displayed when this option is set to non-zero will expand or collapse folds. Christian Brabandt wrote: You can, if you set the foldcolumn option to some value larger than zero. A

vim split window editing = separate window editing?

If vim can split a window and edit the same file in multiple places, shouldn't it be possible to have those windows be disconnected and really be separate windows -- and still edit the same file? I don't think there's is a way to currently do that in vim (???)... but would it be that hard to

Re: vim split window editing = separate window editing?

Benjamin R. Haskell wrote: On Sat, 2 Feb 2013, Marc Weber wrote: Excerpts from Linda W's message of Sat Feb 02 20:11:33 +0100 2013: a) making a copy is cheap :enew then copy paste buf contents If I change contents in one file, it doesn't update in the other. I don't want to have to

Re: Shelling out to cygwin bash from Windows vim

AndyHancock wrote: This problem dogged me for many years, and I finally hunkered down to chase it down. Here is the solution that I found works for me: set shell=c:\cygwin\bin\bash.exe\ -i Won't always find ~/.bashrc cuz depending on how vim is launched, ~ doesn't always resolve to

Re: Vim perl highlighting doesn't understand UTF-8? (vimRE needs perlRE enhancing)

Benjamin R. Haskell wrote: While I've found Vim's RE difficult to memorize all of it's special cases, I didn't know it was also incompatible with it's default text mode. That is what I am stating. you point out \w \h below, but the character classes [:alpha:] and all of them

Re: Vim perl highlighting doesn't understand UTF-8? (vimRE needs perlRE enhancing)

Benjamin R. Haskell wrote: Possibly. Another possibility is that Perl-syntax gurus use the Perl-specific Vim group: https://groups.google.com/group/vim-perl --- Possibly, but I doubt it -- since the only posts there since Apr are a month old relating to a build problem in vim 7.3 when

Re: Vim perl highlighting doesn't understand UTF-8?

Ben Fritz wrote: On Monday, August 20, 2012 3:20:00 PM UTC-5, Linda W wrote: Linda W wrote: Sorta weird -- vim supposed to be in UTF-8, perl as well, but UTF-8 source gets complicated... Ya gotta wonder about claims of UTF-8 compat when it's so hard to get basic parts of the UTF-8

Re: Vim perl highlighting doesn't understand UTF-8?

Just Shoot me now (corrections below) Linda W wrote: RE's are very efficient ways to work with character set encodings. ^^-NOT My problem is that... ^-*one of* ^-(s) (obviously, attention to detail is in there along with dropping out letters and complete words while I am

Re: Vim perl highlighting doesn't understand UTF-8?

Linda W wrote: 920 sub ƒshow_progress($) { 921 #my $p = shift if ref $_[0]; 922 my $paths = $_[0]; But the 'ƒ' in ƒshow_progress ends up being highlighted in red [ as meaning incorrect syntax]. Is there a way to tell the vim syntax checker to allow UTF-8. Does the lack of response

Vim perl highlighting doesn't understand UTF-8?

I have a routine in Perl that I wanted to ensure I marked for my self as a function (vs. an object method that would expect an extra param, first, that would refer to the object -- changing how the function is called and how the function expects to get parameters when it is called). So I

wording ambiguity in help for 'Z' option in cpoptions.

In the help on cpoptions, I find this line confusing: ZWhen using w! while the 'readonly' option is set, don't reset 'readonly'. --- What does 'reset' mean? If you wrote to the file, that implicitly means you had to unset the file's readonly value, so I can read the above to

notice bug in new version of gvim windows.......

When I start gvim with a file name Gvim h:\bin\pcalc.pl, if I edit another file by name, it references the same directory... However, if I use UNC name, Gvim \\ishtar\home\linda\bin\pcalc.pl to edit the same file, my current directory isn't set correctly. I know I used to have my own script

Re: Building Win 7 vim with support for 64 bit perl

Sergey Khorev wrote: Has anyone successfully built Vim for Windows 7 with support for 64 bit perl? �It would be nice if VIM were 64 bit, but 32 bit VIM is OK; �embedded perl must be 5.12 64 bit. 32bit application cannot use 64bit dll. Here is x64 Vim built with ActivePerl 5.12.4.1205:

Re: vimdiff: ignore linebreaks

Bram Moolenaar wrote: I would love to include a better diff library in Vim, but still haven't found a good one that could be included with Vim. --- When it comes to diff improvements, how does one simply 'ignore all white space' ala, diff -w (which should, IMO, work for the original writer,

Re: Request for search/replace upgrade, not wholesale replacement!

AK wrote: On 01/12/2012 04:53 PM, Erik Falor wrote: On Thu, Jan 12, 2012 at 08:17:06PM +0100, Marc Weber wrote: I don't want to offend anybody. Just trying to understand whether having JS support would change anything. So please consider this thread as being a test whether such a change would

Re: Bug: After turning off 'Z'' (cpoptions-=Z') in my .vimrc, vim turns it back on in the gui version in menu.vim.

/* vim: ts=1 sw=1 et sc fo=cqwa1 tw=78 syntax=css */ Jürgen Krämer wrote: if I read :help cpo-Z correctly you should *add* 'Z' to 'cpoptions' to stop Vim from resetting the 'readonly' option, not *remove* it. But apart from that are you sure that menu.vim is the culprit? When I added set

Re: Request for feature upgrade/enhancement.....

Ben Fritz wrote: Nope, she specifically mentioned \v in her post. She doesn't want to simplify Vim's regex, or even learn how to use it (because it [sic]can do most of the stuff Perl can) I'm not the only one: Original Message Subject:Re: More auto-indent

Re: More auto-indent problems

Gary Johnson wrote: I found the problem. There is a bug in $VIMRUNTIME/indent/perl.vim. The author tried to match braces with this: [(){}\[\]] The trouble is, \[ is not an escaped [ because there is no need to escape a [ within []. Thanks for the clear description of the problem.

Bug: After turning off 'Z'' (cpoptions-=Z') in my .vimrc, vim turns it back on in the gui version in menu.vim.

Another special case...how to get vim to stop resetting the read only flag with each write!? can't put it in .vimrc, as it is read before menu.vim, also tried it in .gvim, but apparently it isn't allowed at that point... So looks like the only way is to modify the source? Or am I

Re: Bug: After turning off 'Z'' (cpoptions-=Z') in my .vimrc, vim turns it back on in the gui version in menu.vim.

Linda W wrote: Another special case...how to get vim to stop resetting the read only flag with each write!? can't put it in .vimrc, as it is read before menu.vim, also tried it in .gvim, but apparently it isn't allowed at that point... --- It doesn't seem to matter which way

Re: Request for feature upgrade/enhancement.....

Michael Ludwig wrote: Marc Weber schrieb am 12.01.2012 um 02:38 (+0100): Would take me 30secs to one minute to write. If you don't know VimL much.. Why not just write your own perl script and pipe the buffer? :%! perl myscript_adding_prefixes.pl But this in a Windows batch file,

More auto-indent problems

This may have something to do with my settings, or is some endemic problem in language based indenting. For my indent settings, I have 'si' set, but not 'ai', However, in 2 different languages, perl and javascript, having a backslash in a line will automatically cause indenting on the

Re: Request for feature upgrade/enhancement.....

Ben Fritz wrote: On Jan 9, 4:41 am, Christian Brabandt cbli...@256bit.org wrote: The atom \v does not help you? Nope, she specifically mentioned \v in her post. She doesn't want to simplify Vim's regex, I'd love to simplify it... but it wouldn't be vim's-regex -- it'd be perl's

Re: Request for feature upgrade/enhancement.....

Marc Weber wrote: Vim syntax has far too many inconsistencies for me to remember. Just the fact that \ doesn't always quote the next char -- trying to remember all of it's exceptions is not possible for me. You could write a substitute command once makeing it little bit more consistent

Request for feature upgrade/enhancement.....

Could you please add a '\p' operand to regex's (cf. '\v'), to invoke standard perl pattern matching. I've tried vi's syntax, but it has too many gotcha's and not as much power, whereas, perl's pattern matching is considered 'best of breed' -- check references on wikipedia (or other

Re: bash highlighting problem...

Charles Campbell wrote: I think deprecated syntax should be flagged. --- I would agree -- could you find where/when it was deprecated? I remember seeing more commonly back maybe 10-15 years ago, but I don't recall seeing any specific deprecation notice. The (()), I think was new and

Re: bash highlighting problem...

Taylor Hedberg wrote: Linda W, Fri 2011-12-09 @ 02:46:15-0800: As for the red flagging... I thought it was for syntax errors? since it isn't a syntax error, but merely an older standard, shouldn't it not be flagged as illegal? Yeah, it should probably be accepted as valid

Re: bash highlighting problem...

Taylor Hedberg wrote: You are using some unusual bash syntax that I've personally never seen before, and doesn't appear to be documented in the bash(1) man page. echo $[offset+${diffs[$[MaxLevel-level]]}] You are using `$[...]` to do arithmetic expansion, but this is not the

bash highlighting problem...

In the code below, two of the right brackets , a square ']' bracket on line 15 (2nd one from right) , and a curly one on line 34 (only bracket on line) are hilighted in red indicating no match... but putting your cursor over them shows its matching pair (and the program works fine as it

how to get append to command option to append as literal, than as new option?

When I type in a command with the += operator, it seems to appended the new text separated by a comma -- which is probably what is normally wanted, but in this one case, wasn'tI wanted to append the new text to the existing string -- literally, not as a new 'list value'... (since for

Moving toward a unified Vim...

Linda W wrote: Tony Mechelynck wrote: On 28/10/11 22:26, Linda W wrote: [...] If you put a symlink on linux, windows will see it as a hardlink. That means any file copies will go through it. [...] If you set a symlink on a Linux (ext2, ext3, ext4, reiser, etc.) filesystem, Windows

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

Tony Mechelynck wrote: On 28/10/11 22:26, Linda W wrote: [...] If you put a symlink on linux, windows will see it as a hardlink. That means any file copies will go through it. [...] If you set a symlink on a Linux (ext2, ext3, ext4, reiser, etc.) filesystem, Windows won't see it at all

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

` Ben Fritz wrote: Linda, you cannot expect anyone to listen to you if you keep insulting us. Take you anger and personal attacks to a blog or something if you want to insist on being so confrontational. Insulting...I used a word 'ignoramus' once, That's the only insult I

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

Ben Fritz wrote: On Oct 26, 6:57 pm, Linda W v...@tlinx.org wrote: pansz wrote:On Wed, Oct 26, 2011 at 9:23 AM, Linda Wv...@tlinx.orgwrote:But I asked how it would be incompat if it looked for .vim, if found, then don't look for vimfiles.?You always have multiple runtimepath, at least you

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

Tony Mechelynck wrote: On 13/10/11 01:47, Linda W wrote: Jürgen Krämer wrote: (at least when I launch from explorer...)...so if it finds my .vim and .gvim, why doesn't it find .vim/colors/.vim? did you change the 'runtimepath' option? On Windows the directory for user-specific

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

pansz wrote: On Wed, Oct 26, 2011 at 9:23 AM, Linda W v...@tlinx.org wrote: But I asked how it would be incompat if it looked for .vim, if found, then don't look for vimfiles.? You always have multiple runtimepath, at least you have ~/.vim and /usr/share/vim/vim73

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

` Ben Fritz wrote: On Oct 12, 6:47 pm, Linda W v...@tlinx.org wrote: Jürgen Krämer wrote:(at least when I launch from explorer...)...so if it finds my .vim and .gvim, why doesn't it find .vim/colors/.vim?did you change the 'runtimepath' option? On Windows the directory for user

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

Ben Fritz wrote: On Oct 25, 2:52 am, Linda W v...@tlinx.org wrote: Comments: 1) that .vim isn't searched for in the same way with 'vimfiles', is a rather glaring BUG, given the above.   It's incompatible with the documented procedures for checking the names of .vimrc, .gvimrc

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

George V. Reilly wrote: On Fri, Oct 14, 2011 at 2:50 PM, Alessandro Antonello wrote: On Fri, Oct 14, 2011, at 9:41 AM, Ben Fritz wrote: The default Windows setting, to hide the extension for known file types, will probably make matters worse. I expect, though I have not

Re: Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

` Ben Fritz wrote: On Oct 25, 11:39 am, Linda W v...@tlinx.org wrote: Ben Fritz wrote:On Oct 25, 2:52 am, Linda Wv...@tlinx.orgwrote:Comments: 1) that .vim isn't searched for in the same way with 'vimfiles', is a rather glaring BUG, given the above.   It's incompatible

Re: gvim64/win7 claims error on unzip, but unzip get no error, why?

I typed in exactly what I saw on the screen. (I try to use / whenever I can) It used to work in in XP and before, but they disallowed compat in Win7 (dunno about vista). I searched my machine, there is only 1 unzip on my machine in C:\bin. (Cygwin). It works from shell -- They both

gvim64/win7 claims error on unzip, but unzip get no error, why?

I tried to open a .jar file in gvim (7.3). and got an error (which one has to type in manually, as vim won't let you cut/paste -- a much maligned user-hindrance, when it was first widely used by Microsoft): unzip: cannot find or open C:/Users/lindaw/AppData/Roaming/ So I open up a

Please fix: make Windows Vim use same files as unix. No reason not to and it's confusing in mixed envirionments.

  Jürgen Krämer wrote: (at least when I launch from explorer...)...so if it finds my .vim and .gvim, why doesn't it find .vim/colors/.vim? did you change the 'runtimepath' option? On Windows the directory for user-specific scripts is ~/vimfiles by default, not

group.vim syntax update

To be consistent with passwd.vim (as well as allowing modern group syntax, please apply the following diff to syntax/group.vim.) Bugs me everytime I reinstall to have to fix this... --- syntax/group.vim Wed Oct 27 08:42:54 2010 +++ syntax/group.vim Tue Oct 04 15:06:26 2011 @@

Re: about Vim's builtin color names -- seeing a dff on X11 ver, vs. Win ver in 1 color

Benjamin R. Haskell wrote: Even under X11, those colors are configurable. But apparently not under Vim...on Windows... So, it's got the correct 0xADD8E6 that you want. But it's not used. --- Yup -- I knew there was a problem. Wouldn't have suspected a hard-coded one... Is there

about Vim's builtin color names -- seeing a dff on X11 ver, vs. Win ver in 1 color

I was noticing the difference in colors when I edited on Windows vs. Editing over X. Most of the problem was they were using 2 very different version of a color scheme. After getting them 'on the same page', so to speak, most of the colors look pretty close if not the same, One color

better bash syntax hilighting?

I've been working in a bash script for a while, and the limitations of the current parser are getting annoying. Thinks like it getting out of sync if sees a single or double quote in a comment line! Doesn't hilight many keywords 'notably' function, doesn't color variables the same color

Warning (HTML included to show prog shipped w/syntax highlighting).

When I have the construct, in 4.1: 1 #!/bin/bash 2 30 31 # trace control for subs 32 declare -ix Allow_Trace=$((( 33 _D_LowLevel | 34 _D_Provides | 35 _D_ 36 ))) 37 38 declare -ix

Re: where does Win7's VIM read my .vimrc files from?

Tony Mechelynck wrote: On 14/07/11 22:20, Charles Campbell wrote: Try using set fencs=^=utf-16le (see :help :set^= ) and see if that solves your difficulty. I'm ready to stand corrected whenever TonyM gets around to it! Chip Thanks for the compliment, but most has already been said.

where does Win7's VIM read my .vimrc files from?

I've been trying to add the following -- and added to about 3 separate places and non have work: set fileencodings+=utf-16le First I set it in the .vimrc in my $HOME dir (=//Bliss/username (no work) Note: $HOMESHARE=$HOME, so it was set there too I also tried under my USERPROFILE:

Re: where does Win7's VIM read my .vimrc files from?

stuff is needed. But it's easy to figure out where Vim things it should look for your .vimrc. Go into Vim, and run command, :echo $HOME /Users/linda w.BLISS echo $HOME //Bliss/linda w Ben Fritz wrote: :verbose set fileencodings? BINGO! !)$(!)$*(%!(#( _vimrc !!! Why

Looking at indent problem in perl lang in vim

A problem noted by many (including in the perl.vim indent file) is incorrect functioning of indentation when using a widely used (e.g. from 'perltidy') formatting. Example: my @foobar = ( 1, 2, ); my $nextstatement=1; The above isn't indented properly, but is

How to update perl.vim for UTF-8 chars in identifiers? (RFE?)

I'm using a perl script that has use utf8; at the top that enables use of UTF-8 in variable names. So in one place, instead of my @deltaio; ... $total_io += $deltaio[$Tbytes]; I have: my @Δio; ... $total_io += $Δio[$Tbytes]; (note: 'Δ' = U+0394: GREEK CAPITAL LETTER DELTA) ---

Re: Installing ttf fonts in gvim in windows

Alexander Stepanov wrote: How to use non-monospace in gVim? Only monospace fonts are displayed in font list. --- If you use the cygwin version of 'gvim', and use the 'X11' display, you'll be able to use variable spaced fonts. That's not to say that they look 'great' A slightly better

Re: Installing ttf fonts in gvim in windows

Tony Mechelynck wrote: On 19/04/11 09:36, Alexander Stepanov wrote: Monospace fonts... That's very said. Thank you for explanation. If you mean very sad, this is due to the fixed size of the character cell in gvim, something so fundamental to Vim's mode of operation that it is not going to

Re: why not remove www? Currently http://vim.org/ doesn't work

realfun wrote: But type vim.org in the url of google chrome simply opens nothing - it's required to input www.vim.org instead. I 2nd the motion... It's a pain to have vim.org be non-standard, as I never type in 'www.' in front of sitenames (RSI, less typing...)

Re: why not remove www? Currently http://vim.org/ doesn't work

Tony Mechelynck wrote: Maybe because Chrome doesn't act like most other browsers? When SeaMonkey doesn't find a URL, it will try www. before and/or .com after; this behaviour is configurable but this is the default. Firefox does the same and so does Konqueror. I think IE does too but I could

Re: why not remove www? Currently http://vim.org/ doesn't work

Tony Mechelynck wrote: To make it work, there may or may not be something in Firefox's Preferences (or, on Windows, Options) but you can make it work in any case as follows: ... instructions follow... --- I wish there was a way to post a screen shot. I typed in 'about:config', and typed in

Re: Request for Win Gvim to match *nix re: .vimrc/.gvimrc/.vim

On 7/23/2010 6:49 PM, Tony Mechelynck wrote: When I was on dual-boot I used the converse (notice the use of the 8.3 name for Documents and Settings in order to avoid troublesome spaces in the path): cd $HOME ln -sv /mnt/dos/c/DOCUME~1/tony/vimfiles .vim ln -sv

  1   2   >