Re: Patch 7.3.050

Bram Moolenaar wrote: Patch 7.3.050 Problem:The link script is clumsy. Solution: Use the --as-needed linker option if available. (Kirill A. Shutemov) Files: src/Makefile, src/auto/configure, src/config.mk.in, src/configure.in, src/link.sh On a Centos 5.2

Re: saveas - loads ft plugin - changes dir - wrong filename problem

frabjous wrote: Hi all, I'm here to report what looks like a bug to me. Hopefully I'm not wasting your time. Here are the conditions. 1. Edit a blank file with no ft set (and hence no filetype plugins loaded). 2. Attempt to save the file with an extension which causes a filetype plugin to be

Re: editing DCL

Samuel Ferencik wrote: Hi, DCL is a scripting language for OpenVMS, whose lines of code must all start with a $. Here is a code excerpt (from http://www.eight-cubed.com/articles/dcl_standards.html): |||$ on warning then goto nopriv $ set on $ set

Re: Color Support for :! and :Shell system command execution

Will Gray (graywh) wrote: On Mar 22, 1:27 pm, Charles Campbellcharles.e.campb...@nasa.gov wrote: Perhaps the AnsiEsc plugin which colorizes text according to ansi escape sequences does what you want; you can get the plugin from:

Re: [patch] match does not Conceal items

Christian Brabandt wrote: Hi Bram! On So, 10 Apr 2011, Bram Moolenaar wrote: Can you explain what the effect is? Basically, I wanted to create a plugin that uses concealing for something like vertical folding. Perhaps you could look into foldcol.vim and see if that does what

Re: [bug][w32][netrw] doesn't autochange to the current working dir in netrw buffer

Yue Wu wrote: How to reproduce: :e c:/ then enter any subdirectory in netrw buffer withenter, then :pwd print current working directory, vim still says c:/ it is. gvim is got from vim offical site, OS is windows 2000. Hello, See if :he netrw_keepdir helps. (the default

Re: [bug][w32][netrw] doesn't autochange to the current working dir in netrw buffer

Yue Wu wrote: Thanks, that's it. I think it should be on by default for convenience, what do you think? I do, too, and that option is used in my own .vimrc. While developing netrw's browser capability, that's how I had it. However, I caught grief about it from those wedded to 6.x's

Re: Syntax highlighting unreasonable lags

Дмитрий Франк wrote: Hi. I very like Vim, thank you, but there's one thing in Vim that i really hate. I often use rather old notebook with processor Pentium M 1.6 GHz, and when i use Vim on it, i can't normally edit files *.vim and *.php : syntax highlighting for these filetypes is VERY

Re: a problem with syntax highlighting in regexp.c

Ben Schmidt wrote: I extracted a couple of lines from regexp.c (143,144): (vim 7.3.244) #define BRANCH 3 /* node Match this alternative, or the * next... */ and put them in a file junk.c. Then vim -u NONE -N --noplugin junk.c :syn on shows the comment-ending pair of characters, */, in error

Re: manpageview rating dive

Benjamin R. Haskell wrote: On Wed, 31 Aug 2011, Charles Campbell wrote: Charles Campbell wrote: Hello! I recently checked my plugins' ratings: 08/09/11 script 677/279/10776: Manpageview.vim 08/31/11 script -133/1094/10866: Manpageview.vim This seems like an odd thing -- is this

Re: Create vimballs from the command-line

Matt Wozniski wrote: But let's not forget that they have significant disadvantages, too... Vimballs made with new versions of the plugin don't work on older vims. There's been one problem with that -- 7.0 vimball doesn't handle the later vimball versions. 7.1 and has been compatible; newer

Re: Create vimballs from the command-line

Gary Johnson wrote: On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote: And then there are people like me who can un- .zip files if they have to, but prefer to gunzip them (un- .gz), which is the Unix standard (as opposed to the Microsoft Megabucks LoseDough standard).

Re: Patch 7.2.121

Bram Moolenaar wrote: Patch 7.2.121 Problem:In gvim !grep a *.c spews out a lot of text that can't be stopped with CTRL-C. Solution: When looping to read and show text, do check for typed characters every two seconds. Files: src/os_unix.c snip

Re: Concel and Ownsyntax patch FINALLY updated...

John Beckett wrote: Vince Negri wrote: The page on google groups needs a small update to fix the reference to 7.0.35. Good point, but please tell me exactly what text would be appropriate. It currently reads: Status: works, but only in Vim 6.4.10 and 7.0.35 Will we just

getting dropped from the mailing list

Hello! This is the second time I've stopped receiving emails from vim_dev (its happened to me once on vim_use) this past week, unless there's actually been no activity on this group for two days. The last time I unsubscribed (successfully) from both vim_use and vim_dev and then

building vim with perl support

Hello! I recently got a 64-bit computer; it has perl supported. However, the configure script doesn't appear to be picking up on the location of the header files: (there were about 100 error messages) /usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi/CORE/EXTERN.h

Re: scim_bridge_client_imcontext_set_cursor_location -- an annoying error message

Tony Mechelynck wrote: On 10/06/09 21:31, Charles Campbell wrote: Hello! In running a not too trivial script I've written, I keep getting messages of the following sort (even when the script is quiescent, ie. after its opened its 8 windows): (Centos 5.2/Linux/gtk) CALC/ xorn? An

Re: BUG: Vimball: Extra \ in folder names with space under Windows in .VimballRecord

KF Leong wrote: I am testing to use Vimball to package a plugin and when trying the RmVimball command, the installed plugin files are not removed. Looking through the .VimballRecord file, the delete() entries added extra backslash (\) to the folder names, thus making the delete() command to

Re: copy a map (in order to restore it later)

Hari Krishna Dara wrote: I need to be able to create an imap for Tab when my plugin is toggled on, and unmap it when it is toggled off. What I would prefer is to restore the previous map of Tab rather than simply unmap it, but there is no straight-forward way to capture the existing map such

Re: mail from new wiki pages

John Beckett wrote: John Beckett wrote: You can actually watch pages before they are created, however, that's a bit exotic, so I would recommend creating each relevant Script:xxx page then watching it. On second thoughts, it should be pretty easy to watch the pages that are NOT yet

Re: Unsubscrible vim_dev

John Beckett wrote: Simson Liu wrote: I have subscrible the list with new gmail box. But I can't unsubscrible the list with my current work mail box. I have sent the vim-dev-unsubscr...@vim.org the empty mail message many times, but have no any effect. So other managers don't have to

Re: odd character drawing problem

Bram Moolenaar wrote: Charles Campbell wrote: The following line, when in a buffer that vim is displaying: m=⎣ℜ(b-a)⎦=1~1026 has the script R displayed correctly when the cursor is swept over it from right to left, but the script R is displayed incorrectly when the cursor is swept over

Re: small sh.vim patch

Will Fiveash wrote: Attached is a tiny patch to update sh.vim to support ksh93's ${!var[*]} associative array index key list dereference syntax. Basically, if foo is an associative array, print ${!foo[*]} would output all the index keys associated with foo. Thanks! I've put an updated

Re: small sh.vim patch

Gary Johnson wrote: set -o ignoreeof# Don't let Ctrl-D exit the shell. Hello, Gary: Are you actually using the old Bourne shell? This problem does not appear when using the Korn/Posix shell or the Bash shell. Try reading a bit of :help sh.vim . Regards, Chip Campbell -- --

Re: small sh.vim patch

Gary Johnson wrote: On 2014-08-11, Gary Johnson wrote: On 2014-08-11, Charles Campbell wrote: Gary Johnson wrote: On 2014-08-09, Charles E Campbell wrote: Gary Johnson wrote: set -o ignoreeof# Don't let Ctrl-D exit the shell. Hello, Gary: Are you actually using the old Bourne

getting an up-to-date runtime

Hello: I don't have mercurial on this machine -- we use cvs. Consequently, what I'd used in the past to update runtime was: rsync -avzcP --delete --exclude=dos --exclude=spell ftp.nluug.nl::Vim/runtime/ . but, having tried it this morning, I get: rsync: failed to connect to

Re: improved folding legibility [patch included]

Bram Moolenaar wrote: Charles Campbell wrote: I find reading the folded lines to be less than ideal, as the extra spacing required of the +---s varies and so lines: doesn't line up. This patch makes all the +---... prefixes take up 5 spaces (using %-5s, so it uses padding). By itself, this

Re: netrw mis-handle windows local paths.

mattn wrote: Hi list. When open scp protocol URLs, netrw call scp command like below. scp -q host:path C:\path\to\temp\dir\file.txt But scp.exe (not pscp) command handle the path as: * C is hostname * \path\to\temp\dir\file.txt is a remote path. Below is a patch to fix this issue. This

Re: [bug] sh syntax hl: only 1st \ escaped if dq string to eval with assignement inside constructs

G.raud wrote: Rather complex case appearing only inside if, for, while constructs but not outside any constructs nor in a case construct. A minimal case to test (a string of \\ is problematic too; an assignement of varname= instead of $varname= is not problematic): $ cat test.sh EOF

Re: [bug] sh syntax hl: only 1st \ escaped if dq string to eval with assignement inside constructs

G.raud wrote: Rather complex case appearing only inside if, for, while constructs but not outside any constructs nor in a case construct. A minimal case to test (a string of \\ is problematic too; an assignement of varname= instead of $varname= is not problematic): $ cat test.sh EOF

Re: Make closed folds line up by Charles Campbell, rare crashes in case relativenumber nonumber

Roland Eggner wrote: On 2014-12-12 Friday at 09:46 +0200 Marius Gedminas wrote: On Fri, Dec 12, 2014 at 12:57:39AM +0100, Roland Eggner wrote: Patch Make closed folds line up by Charles Campbell is already on Brams todo list. http://www.drchip.org/astronaut/vim/patch/folding.ptch It works

Re: [bug] glob won't list symbolic links that point to non-existing files

Bram Moolenaar wrote: Charles Campbell wrote: Please try the following on a linux system: mkdir PROBLEM cd PROBLEM ln -s file1 file2 Doing ls shows file2 exists (but it points to a non-existing file). Fire up vim: vim -u NONE -N :echo string(glob(*)) shows that glob()

Re: Netrw shows directory structure wrong: always shows directory inside itself

Yuri Vic wrote: These two situations are both correct. I think when people open a directory, they normally expect to see what is inside, like 'ls' would show. It doesn't matter how this is implemented, but the expected result is the list of what is inside, plus '..' item. I should mention

[bug] a problem with an autocmd event and a server

Hello! I've attached a script which illustrates the problem. vim -u NONE -N prblm.vim :so % :q (in the gvim that's showing prblm.vim, NOT the remote gvim) Behavior: * a remote server gvim shows up (this happens) * a message verify its working shows up in the server's message line

Re: Proposal: fixing Todo highlighting chaos

Ben Fritz wrote: Well, sure it's easy to override one file. But you would need to do that for literally every filetype you edit in Vim! That's a much taller order! I'm not so sure about that. * option 1: wait for approval of idea, then wait for many maintainers to change their syntax

Re: Patch 7.4.919

Bram Moolenaar wrote: > Patch 7.4.919 > Problem:The dll options are not in the options window. > Solution: Add the dll options. And other fixes. > Files:runtime/optwin.vim > Not a big deal to me, as I'm using linux -- but this patch isn't available via ftp yet. Regards, Chip

Re: Patch 7.4.907

Bram Moolenaar wrote: > Patch 7.4.907 > Problem:Libraries for dynamically loading interfaces can only be defined > at compile time. > Solution: Add options to specify the dll names. (Kazuki Sakamoto, > closes #452) > Files: runtime/doc/if_lua.txt,

Re: Patch 7.4.907

Bram Moolenaar wrote: > Charles Campbell wrote: > >> Bram Moolenaar wrote: >>> Patch 7.4.907 >>> Problem:Libraries for dynamically loading interfaces can only be defined >>> at compile time. >>> Solution: Add options to specify the dll names. (Kazuki Sakamoto, >>>

Re: [vim] Regression in 7.4.902 breaks window navigation (#484)

Malcolm Rowe wrote: > > After a0f849e > , > using netrw seems to break window navigation in some circumstances: > > $ cat > /tmp/vimrc > set nocompatible > filetype plugin on > $ vim -u /tmp/vimrc -U NONE > :Se > (open

Re: [vim] Splitted windows and File Explorer (It doesn't change directory in other window) (#395)

Vim Github Repository wrote: Hi all, I don't know if this could be a bug of netrw. I'm trying to have a splitted session in vim with a window that keep sticky the File Explorer. so I do this with: Try an up-to-date netrw (latest available at

Re: Should MatchParen plugin restore current window?

Benjamin Fritz wrote: > Currently the MatchParen plugin distributed with Vim, will > automatically cycle through all windows with :windo, when you use the > :NoMatchParen or :DoMatchParen command. > > This causes problems with (for example) the LargeFile plugin from Dr. > Chip, since that plugin

Re: Patch 866 problem

'James Kolb' via vim_dev wrote: > This should already be fixed by patch 897. Are you using patch 897? > Yes, I was using 7.4.1-963 -- and was still getting a hang. The application being hung was something I use for netrw testing -- and when it stopped working, I wasn't sure why, and got back to

Re: Patch 866 problem

Charles E Campbell wrote: > 'James Kolb' via vim_dev wrote: >> This should already be fixed by patch 897. Are you using patch 897? >> > Yes, I was using 7.4.1-963 -- and was still getting a hang. The > application being hung was something I use for netrw testing -- and when

Re: Bash syntax highlighting: miscomment

Богдан Горбешко wrote: > if [[ "$keyword" =~ \# ]]; then Hello: I'm afraid that I don't see a problem with your example's highlighting. Perhaps you need to upgrade your syntax/sh.vim? Its up to v143. You can get it from vim's git site: git clone https://github.com/vim/vim.git or, if you've

Re: Patch 7.4.967

Bram Moolenaar wrote: > Patch 7.4.967 > Problem:Cross compilation on MS-windows doesn't work well. > Solution: Tidy up cross compilation across architectures with Visual Studio. > (Mike Williams) > Files: src/Make_mvc.mak > Hello: this patch isn't available via ftp yet...

Re: Patch 7.4.1001

Bram Moolenaar wrote: > Charles Campbell wrote: > >> I had a problem with patch#1001: >> >> Applying patch 7.4.1001 >> can't find file to patch at input line 18 >> Perhaps you used the wrong -p or --strip option? >> The text leading up to this was: >> -- >> |To:

Folding patch updated for 7.4.1049

I've attached the patch. As a reminder: it makes folded lines more readable by doing some aligning. Regards, Chip Campbell -- -- 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

Re: Patch 7.4.1000

Bram Moolenaar wrote: >> Den onsdag 30 december 2015 kl. 15:49:30 UTC+1 skrev Bram Moolenaar: >>> Patch 7.4.1000 >>> Problem:Test 49 is slow and doesn't work on MS-Windows. >>> Solution: Start moving parts of test 49 to test_viml. >>> Files: src/Makefile, src/testdir/runtest.vim, >>>

Re: Patch 7.4.1001

Bram Moolenaar wrote: > Patch 7.4.1001 (after 7.4.1000) > Problem:test_viml isn't run. > Solution: Include change in makefile. > Files: src/testdir/Make_all.mak > > > *** ../vim-7.4.1000/src/testdir/Make_all.mak 2015-12-28 21:35:07.773243000 > +0100 > --- src/testdir/Make_all.mak

Re: warning during compilation

Bram Moolenaar wrote: > Charles Campbell wrote: > >> I just noticed that there's a warning when compiling with gcc under >> scientific linux: >> >> misc2.c: In function 'put_time': >> misc2.c:6312: warning: ignoring return value of 'fwrite', declared with >> attribute warn_unused_result >> >> In

Re: warning during compilation

Charles E Campbell wrote: > Bram Moolenaar wrote: >> Charles Campbell wrote: >> >>> I just noticed that there's a warning when compiling with gcc under >>> scientific linux: >>> >>> misc2.c: In function 'put_time': >>> misc2.

Re: vim_dev vs. vim_vim

Chris Jones wrote: > Since March 2015 I have been receiving vim development emails on two > separate mailing lists: the old vim_dev and a new list called vim_vim. > > What is the difference between the two lists and is there a particular > reason why there are two differents lists? > For one

Re: [vim] Vim removes last newline (#488)

Laurent Lyaudet wrote: > > Hi, > > I have found the following bug. When I open a file in Vim the last > newline disappears. > Hence it is impossible to see it is there and to remove it (suppress > or backspace doesn't work). > The problem occurs both with Linux '\n' and Windows '\r\n'. > > I join

Re: [vim] comments inside parentheses mess up the syntax coloring of shell script (#487)

Laurent Lyaudet wrote: > > Hi, > Thanks for the quick answer. > I tested the latest syntax/sh.vim (version 142) as you suggested. > I attach the result for a slightly modified shell script: > bugsyntaxcoloringvimsh_142 >

Re: [vim] comments inside parentheses mess up the syntax coloring of shell script (#487)

Laurent Lyaudet wrote: > > Hi, > Thanks for the quick answer. > I tested the latest syntax/sh.vim (version 142) as you suggested. > I attach the result for a slightly modified shell script: > bugsyntaxcoloringvimsh_142 >

Re: [vim] comments inside parentheses mess up the syntax coloring of shell script (#487)

h_east wrote: > BTW, There is a thread that you must reply. > https://groups.google.com/d/topic/vim_dev/ZSUw8grrOhw/discussion I already have a vim.vim syntax generator. Chip Campbell -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text

Re: [vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

Nikolai Aleksandrovich Pavlov wrote: > > @chrisbra I think it is obvious: whan > you linked there is a /plugin/. If this is merged it would be part of > the standard distribution. Given that all necessary functionality is > already here it is more convenient to have

Re: [vim] Vim directory browsing is leaving swap files (#552)

Marius Gedminas wrote: > On Mon, Jan 11, 2016 at 03:31:17PM -0500, Charles E Campbell wrote: >> Dino Morelli wrote: >>> On Monday, January 11, 2016 at 1:29:48 PM UTC-5, Christian Brabandt wrote: >>>> Closed #552. >>>> >>> Can you tell me if thi

Re: [vim] Vim directory browsing is leaving swap files (#552)

Dino Morelli wrote: > On Monday, January 11, 2016 at 1:29:48 PM UTC-5, Christian Brabandt wrote: >> Closed #552. >> > Can you tell me if this is an existing issue already reported? Or if it's not > an issue at all but something that can be changed with config? There are no > details for why this

Re: [vim] Vim cryptmethod uses SHA-256 for password-based key derivation (#639)

Benjamin Fritz wrote: > > On Wed, Mar 23, 2016 at 4:58 PM, Bram Moolenaar > wrote: > > > > > Speaking of defaults: I think Vim should default to the strongest > > > method available. I additionally think Vim should warn on saving with > > > a known

Re: Spellcheck after Ellipsis again [vim bug found?]

David Woodfall wrote: >> David Woodfall wrote: >>> syn sync fromstart >>> syn match Ellipsis /[.][.][.]\s\+\l.*\>/ contains=@NoSpell transparent >>> syn match Ellipsis2 /[.][.][.]\n\s\+\l.*\>/ contains=@NoSpell >>> transparent >>> syn cluster Spell add=Ellipsis >>> syn cluster Spell add=Ellipsis2

Re: Patch 7.4.1952

Bram Moolenaar wrote: > Patch 7.4.1952 > Problem:Cscope interface does not support finding assignments. > Solution: Add the "a" command. (ppettina, closes #882) > Files: runtime/doc/if_cscop.txt, src/if_cscope.c > Hello! I'm using git .. and I don't seem to have if_cscop.txt (or

Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

Ben Fritz wrote: > On Friday, January 8, 2016 at 2:33:04 AM UTC-6, Christian Brabandt wrote: >> Having said that, I personally don't like the argument as >> well. Perhaps we could use a new command modifier like >> :keeppos windo ... >> >> That could be useful for other commands as well. >> > I

Re: [vim] Vim directory browsing is leaving swap files (#552)

Dino Morelli wrote: > > This behavior was observed with version 74994 but not in 74778 > > Steps to reproduce: > > In a terminal window > > |$ mkdir -p vimswap/foo/bar $ touch vimswap/foo/bar/file1 $ touch > vimswap/foo/bar/file2 $ cd vimswap | > > In a different terminal window > > |$ cd vimswap

backing out patch 866

Hello! I'm afraid that patch 866, which is flawed, will end up in 7.5. Could this patch be backed out until its fixed, please? Thank you, Charles Campbell -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For

Re: backing out patch 866

Tony Mechelynck wrote: > On Mon, Feb 1, 2016 at 4:43 PM, Charles E Campbell > <drc...@campbellfamily.biz> wrote: >> Bram Moolenaar wrote: >>> Charles Campbell wrote: >>> >>>> I'm afraid that patch 866, which is flawed, will end up in 7.5. Cou

Re: backing out patch 866

Bram Moolenaar wrote: > Charles Campbell wrote: > >> I'm afraid that patch 866, which is flawed, will end up in 7.5. Could >> this patch be backed out until its fixed, please? > I'm not aware of a known problem. What is the flaw? > Hello, Bram: With the latest batch of patches I can no longer

Problem with patch#866

Hello: Back to the patch#866 problem I'm having. I'm using vim 7.4.1416: * using efence: links fine, but won't run (runs out of memory) * using valgrind: works * using valgrind --leak-check=full: works As can be seen from the trace below, the program hangs in a call to nanosleep in

Re: Problem with patch#866

Charles E Campbell wrote: > Hello: > > Back to the patch#866 problem I'm having. I'm using vim 7.4.1416: > > * using efence: links fine, but won't run (runs out of memory) > * using valgrind: works > * using valgrind --leak-check=full: works > > As can b

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

Josh Reichardt wrote: > > With no plugins installed: > > With the cursor before the |--install| flag I get |shConditional|. > With the cursor after the |--install| flag I get |shCaseEsac|. > > shCaseEsac should only be in effect when one is using a case construct. Your example doesn't have a case

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

Christian Brabandt wrote: > > Well, what is the output of the synID command given above? It does not > seem reproducible. > > Version questions: * what version of syntax/sh.vim are you using? The latest release: v145 * what version of vim are you using? You need 7.4.1141 or later. Charles

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

Christian Brabandt wrote: > > I think, the problem is this line from sh.vim (distributed with vim): > > |syn region shCaseEsac matchgroup=shConditional start="\ matchgroup=shConditional end="\" end="\" contains=@shLoopList | > > which matches the xcode-select command.

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

Christian Brabandt wrote: > Hi Charles! > > On Di, 01 Mär 2016, Charles E Campbell wrote: > >> This is a solution, but inadequate, I'm afraid. The right solution >> (now, for the 3rd time): use a vim with patch 1141, along with >> syntax/sh.vim v145. > I am a

Re: Undefined variable: b:netrw_curdir

Xavier de Gaye wrote: > This is a regression introduced somewhere after 7.4.944. > > This error occurs when opening a file and when: > let g:netrw_browse_split = 3" open file in new tab > > Error message: > Error detected while processing function 27_NetrwBrowseChgDir: > line

Re: [vim] netrw suppress '@' when editing a file (from ssh) (#684)

pLesur wrote: > > When SSHing to a directory using vim: > > |scp://user@host//dir/| > > and you want to edit a file, the command will read as: > > |scp://userhost//dir/file #<- '@' is missing !| > > An empty file is then opened, and if saved, will override the real, > potentially non empty, remote

Re: Vim 7.5 or Vim 8?

Bram Moolenaar wrote: > I have been wondering if the next release should be called 7.5 or 8. > We have quite a few new features, but not that many as with the Vim 7 > release. Well, that was a big release. I think the most important > addition since then is persistent undo in 7.3. Now we have

Re: iskKeep is a global variable in runtime/syntax/vim.vim.

Naruhiko Nishino wrote: > Hi Bram and Charles, > > I found that `iskKeep` is a global variable in runtime/syntax/vim.vim. > I think that the variable have to use script scope better than global scope. > > I wrote this patch. Please check it. > Hello! Thank you -- I've included it. Chip Campbell

Re: BSD specific cType's for syntax highlighting

frantisek holop wrote: > Christian Brabandt, 08 Apr 2016 08:08: >> I don't have any saying in that, but I guess what Bram wants is >> something like this: >> >> if exists("c_bsd_types") >> syn keyword cType u_int8_t u_int16_t u_int32_t u_int64_t >> endif >> >> And then add an entry

Re: [vim] netrw silently closing buffers on its own (#231)

Jake Bell wrote: > > Also experiencing this issue, as noted in macvim-dev/macvim#255 > . It appears to have > /started/ happening for me some time between patch 7.4.1362 and the > current HEAD. > > I'll try to do a |git bisect| in the next few days

Re: [vim] Long lines make VIM slow but... (#555)

Hugo Oliveira wrote: > > @chrisbra , I can also confirm the > behaviour of @Deluxo . Using the kludge of > setting synmaxcol to a high value and calling syntax on again make > scrolling faster. Can you explain why? > > I have syntax on on my

Re: [bug]Strange interaction between Netrw and expr mapping with ! command

Nicola wrote: > To reproduce, use this vimrc_minimal: > > set nocompatible > fun! MyFun() > silent !ls > endf > nmap o MyFun() > > Then: > > vim -u vimrc_minimal > :Ex > :enew > \o > > (:enew is optional). You should get the following error: > > Error detected while processing function

Re: $VIMRUNTIME/syntax/vim.vim seems to be highlighted wrongly

tyru wrote: Hi Vimmers and Dr.Chip, Some items seems to be highlighted wrongly in my vimrc. Please see attached Vim script file, HTML(:TOhtml), screenshot. Vim script file: reproducible script HTML: ":TOhtml"'s result PNG: screen capture of HTML Hello! I see nothing wrong in the

Re: Patch 7.4.1770

Charles Campbell wrote: > Bram Moolenaar wrote: >> Charles Campbell wrote: >> >>> Bram Moolenaar wrote: Patch 7.4.1770 Problem:Cannot use true color in the terminal. Solution: Add the 'guicolors' option. (Nikolai Pavlov) Files: runtime/doc/options.txt,

Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

Murukesh Mohanan wrote: > > Typically man pages have bold and underlines displayed using |x\bx| > and |_\bx|, |\b| being the backspace and |x| the letter in question > (Thomas Dickey talks about this in this Unix & Linux post > ). That's what makes >

warning in term.c

Hello: I'm getting a warning from term.c: term.c|6180 warning| ignoring return value of 'fgets', declared with attribute warn_unused_result The line in question does use (void)fgets(...) so the result is intentionally thrown away. Regards, Chip Campbell -- -- You received this message

Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

Enno wrote: > Dear Charles, > > Does this mean that ManPageView overrides Vim's built-in :Man? Then :MANPAGER > would use it, once ManPageView installed. > > You should propose to SungHyun Nam, the maintainer of :Man, to merge > :ManPageView into :Man. > > As an aside, perhaps worth thinking

Re: $VIMRUNTIME/syntax/vim.vim seems to be highlighted wrongly

tyru wrote: > Hi Vimmers and Dr.Chip, > > Some items seems to be highlighted wrongly in my vimrc. > Please see attached Vim script file, HTML(:TOhtml), screenshot. > > Vim script file: reproducible script > HTML: ":TOhtml"'s result > PNG: screen capture of HTML > You might want to try swapping the

Re: Vim 7.5 or Vim 8?

Michael Jarvis wrote: > On Tuesday, April 5, 2016 at 2:28:34 AM UTC-5, Dominique Pelle wrote: >> Bram Moolenaar wrote: >> >>> I have been wondering if the next release should be called 7.5 or 8. >>> We have quite a few new features, but not that many as with the Vim 7 >>> release. Well, that was

Re: Changing the defaults with Vim 8

Bram Moolenaar wrote: > Vim has always been conservative about the default option values. > Without any .vimrc the default is 'compatible'. That's nice for people > who rely on the old Vi. But how many of these still exist? I expect > nearly all Vim users to want 'nocompatible', thus create a

Re: Wish list for a more powerful search in Vim

Christian Brabandt wrote: > Hi Yegappan! > > On Fr, 29 Jul 2016, Yegappan Lakshmanan wrote: > >> Hi Christian, >> >> On Thu, Jul 28, 2016 at 11:16 PM, Christian Brabandt >> wrote: >>> On Do, 28 Jul 2016, Bram Moolenaar wrote: >>> I think it should. Most users will have

Re: Changing the defaults with Vim 8

Christian Brabandt wrote: > Hi Bram! > > On So, 24 Jul 2016, Bram Moolenaar wrote: > >>> please no hlsearch. That is most often annoying. >> Well, I find it useful. But I suppose that's more a personal >> preference. > perhaps, if we made ctrl-l clear the search highlighting by default? > >>>

Re: [vim/vim] Syntax highlighting for messages with RFC3339 timestamp (#946)

Sung Po-Han wrote: > > vim-messages > > It seems that the hostname is considered as a tag name. > > By checking the file runtime/syntax/messages.vim, I found it is easy > to fix. > > |diff --git

Re: [vim/vim] sh syntax script highlights multiline arrays inside an if statement incorrectly (#962)

keremc wrote: > > Inside an if statement the opening parenthesis of a multiline array > will not be highlighted at all, while the closing parenthesis will be > highlighted as an error. > > Hello: Please try the attached syntax/sh.vim. Regards, Chip Campbell -- -- You received this message

folding patch

Hello: Here's my patch for neater folding displays, updated to apply cleanly for vim 7.4.1979. Regards, Chip Campbell -- -- 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

Re: [vim/vim] sh.vim: Feature request - Better processing of bash's substring expansion (#1437)

Norman Abramovitz wrote: > > A valid substring expansion that can be differentiated from the :- > expansion should not show as an error. > > #!/bin/bash > f() { > local last=${1: -1:1} > echo ${last} > } > f abc > I don't see any error highlighting with this; I'm using syntax/sh.vim v168,

Re: [patch] fix syntax error in syntax/tex.vim

h_east wrote: > Hello Dr.Chip (as a maintainer of syntax/tex.vim) > > PS > This issue was reported by YamaCIR-KIT. > > I am reporting on behalf. > > He/She found syntax error in syntax/tex.vim L514 > Comma is used instead of Right square bracket. > > Patch attached. > Please check it. > > -- >

tag priority

Hello: Maybe I was just lucky for years, but it seemed to me that the order of tags files (left to right in the tags option) and order of tags (top-to-bottom in the tags file) was important in resolving multiple tags with the same name. That no longer seems to be the case, which makes it hard to

Re: [vim/vim] sh.vim: Syntax highlighting thinks quote does not close (#1008)

Norman Abramovitz wrote: > > Still seeing incorrect syntax highlighting for shell scripts > > " Vim syntax file > " Language: shell (sh) Korn shell (ksh) bash (sh) > " Maintainer: Charles E. Campbell ndroch...@pcampbellafamily.mbiz > <mailto:ndroch...@pcampbe

Re: [patch] fixed small mistakes in documentation

Dominique Pellé wrote: > Hi > > Attached patch fixes a few minor mistakes in help files. > > Dominique > regardless vs irregardless -- doesn't matter, really; "irregardless" is a commonly used albeit non-standard word (that appears, btw, in several dictionaries). About "thirty-two" vs "thirty

Re: [vim/vim] sh.vim: Feature request - Better processing of bash's substring expansion (#1437)

Norman Abramovitz wrote: > > Tried out 168 and still seeing the error. > > Uploading some screenshots showing the error colorization. Also > uploaded some highlight colorization showing that colorization is an > error colorization. > > screen shot 2017-02-06 at 9 30 39 am >

<    1   2   3   >