Re: Patch: Optimise ascii char classificaton

Mike Williams wrote: So with my setup, nerdtree takes a while to start in large directory of files, such as VIM's src directory. On Windows the profiler shows a large amount of time is being spent in the CRT's isalnum(), isalpha() and islower() internals, coping with locale handling. With v

Re: netrwBrowseX should use , not

Jonas Diemer wrote: Hi, working on windows, I found that opening files externally using gx does not work well for filenames with spaces. I added space to the filename characters (:set isfname=+32), which fixes gf. However, I still cannot open files with spaces using gx The fix is rather eas

warnings while compiling vim 7.4a.14

Hello! Got two warnings: regexp.c: In function ‘match_follows’: regexp_nfa.c|3814 warning| will never be executed ui.c: In function ‘clip_gen_owner_exists’: ui.c|1471 warning| will never be executed Two nearly trivial patches attached. Regards, Chip Campbell -- -- You received this message f

Re: Patch: Remove invalid keywords from syntax/vim.vim

Hello! Please try syntax/vim.vim at my website: http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM Regards, C 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 http://ww

Re: Vim syntax file should not require interpreter support to highlight :{interp}<

ZyX wrote: I see that all g:vimsyn_embed flags say things like “embed … **(but only if vim supports it)**”. This is ridiculous: Ah, I disagree -- not ridiculous at all. What's ridiculous is to assume that one will be writing code for an interpreter embedded in vimscript without being able to

Re: [bug] netrw with netrw_liststyle = 3

Bruno Sutic wrote: Hi, I "discovered" netrw liststyle=3 aka tree style listing a couple days ago. (I love it!) Ever since, I've had a weird issue where I would open a file and it would be completely blank. I'll look into it (and I was able to duplicate it -- thanks for the good directions

Re: extremely bad 7.4 regex performance for syntax highlighting

Ben Fritz wrote: On Wednesday, October 9, 2013 10:09:05 AM UTC-5, Julian Taylor wrote: Is easytag just doing the highlight regex wrong or is this a issue in the new engine? the regex used looks like this: syntax match cFunctionTag /\C\<\%(cpl_column_get_mean_complex\|cx_tree_previous\|cpl_ta

Re: Segmentation fault when opening a README file

claudelepois...@gmail.com wrote: echo "/**" > README I put a au BufNewFile,BufReadPost README setf asciidoc line into my .vim/filetype.vim so opening README would cause vim to use asciidoc highlighting. I'm

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, runtime/doc/if_p

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, >>> clos

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 Cam

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 an

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 a

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 yo

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_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 thing,

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 th

Re: Patch 7.4.866

Hello! I'm having problems with patch#866; I've attached a small script to illustrate this issue: vim -u NONE Hang.vim :Hang The client hangs waiting for a reply, but the two GOT HEREs in the server show that its been sent. Regards, Chip Campbell -- -- You received this message from the "vim

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 ca

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 it

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 -

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... C

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 do

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, >>> sr

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 2015

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 http://www.vi

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: vim_dev@goog

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 gr

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': >>&

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 l

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 $

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 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

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 more

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 c

Re: backing out patch 866

Tony Mechelynck wrote: > On Mon, Feb 1, 2016 at 4:43 PM, Charles E Campbell > wrote: >> 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

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 mch_dela

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 > >

Re: Netrw failure with latest Vim

François Ingelrest wrote: Hi all, I've updated Vim to 7.3.744 (features=big) and now netrw fails the second time I try to open a file using :Explore 1. Start vim 2. :E and open a file 3. :E fails At step 3 I get a blank screen with no listing. This seems to be caused by this line in my .vimrc:

Re: Netrw failure with latest Vim

John Little wrote: On Saturday, December 1, 2012 8:54:16 PM UTC+13, John Little wrote: Attempting to install the latest netrw... I downloaded netrw 147b from http://www.drchip.org/astronaut/vim/index.html#NETRW but it didn't work at all, "home/john/" was prepended to every filename, note no

Re: Netrw failure with latest Vim

John Little wrote: John Little wrote: I downloaded netrw 147b from http://www.drchip.org/astronaut/vim/index.html#NETRW but it didn't work at all, "home/john/" was prepended to every filename, note no leading "/" (yes, my home directory is /home/john). and DrChip replied: I haven't been ab

subscribe

subscribe -- 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: if/else/end broken in netrw.vim

mattn wrote: Typing o in netrw occur error. https://gist.github.com/4583859 Thank you for your patch. The error was still in netrw, although the key is now O rather than o. Please try the copy of netrw available from my website: http://www.drchip.org/astronaut/vim/index.html#NETRW . Rega

Re: New feature: absolute line number in relativenumber for the current line

Ben Fritz wrote: I only rarely edit files with 1 or more lines. Most of the time for me, my 'rnu' column takes 4 columns, and my 'nu' column takes 5. I don't care about the extra width, and would probably never turn off the option to show the absolute number on the current line if there we

Re: [patch] Netrw error when the clipboard feature is disabled

Charles E Campbell wrote: Ken Takata wrote: Hi Charles, I got the following error with netrw v150 when I changed the directory: Error detected while processing function 40_NetrwBrowseChgDir..40_NetrwOptionRestore: line 69: E354: Invalid register name: '*' It occurs when the

Re: Problem with netrw and diffing files

Felix Herrmann wrote: Hey folks :) I just stumbled upon a problem with netrw (which truly is great btw. I mean netrw is great. The problem: not so much ;) ) and making diffs. When I use netrw and mark two files, and then do "md" to diff them, I always get: Error detected while processin

Re: vim doesn't open some directories

Yuri Vic wrote: Beginning few months ago, vim behavior changed for this command: 'vim /some/dir/' It opens some directories with "Netrw", and it doesn't open some other directories. But it always prints in the bottom: "/some/dir/" Illegal file name. Directories it opens successfully tend to be

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

Yuri Vic wrote: Netrw shows the entry with the current directory name inside itself. For example: There are two directories /some/dir and /some/dir/other-dir Command 'cd /some/dir && vim .' shows this: ../ dir/ | other-dir/ And command 'cd /some/dir/other-dir && vim .' shows this: ../ other-dir/

Re: Need support for opening files via HTTPS

C Campbell > On Mar 21, 2014, at 12:46 AM, tooth pik wrote: > >> On Thu, Mar 20, 2014 at 11:55:29AM -0400, Charles Campbell wrote: >> Bohr Shaw wrote: >>> ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim >> Hello! > >> Please try netrw v151n, available from my website: >>

Re: [patch] add sortuniq() function

LCD 47 wrote: On 19 March 2014, Cade Forester wrote: Looks like you made a copy of f_sort() and modified it a bit. That's a lot of duplicate code. Better move the common stuff into a function that's used by both sort() and sortuniq(). Fixed How about separating it from sort()? That

Re: SL6.4: can't compile os_unix.c due to patch#238

Christ van Willegen wrote: On Wed, Apr 9, 2014 at 4:07 PM, Charles Campbell wrote: Hello: I'm getting some compiler errors with Scientific Linux 6.4: This is configured with: ./configure --with-features=huge --enable-gui=yes --enable-gui=gtk2 --enable-perlinterp --enable-pythoninterp --enable

Re: delete just left netrw buffer after opening file

Enno wrote: Le vendredi 23 mai 2014 10:42:55 UTC+2, Enno a écrit : Can one configure netrw so that when opening a file in netrw the just left netrw buffer is automatically deleted? For example type :e ., navigate to a file, hit . Then there is the netrw buffer, created by :e . that we just le

Re: delete just left netrw buffer after opening file

Enno wrote: Am Freitag, 23. Mai 2014 10:42:55 UTC+2 schrieb Enno: Can one configure netrw so that when opening a file in netrw the just left netrw buffer is automatically deleted? For example type :e ., navigate to a file, hit . Then there is the netrw buffer, created by :e . that we just lef

Re: Issue 230 in vim: "Vim: Caught deadly signal SEGV"

Charles Campbell wrote: v...@googlecode.com wrote: Comment #4 on issue 230 by brammool...@gmail.com: "Vim: Caught deadly signal SEGV" http://code.google.com/p/vim/issues/detail?id=230 The errors in the libfontconfig.so look like a library problem: reading 4 bytes where there are only 2. Be

Re: Issue 230 in vim: "Vim: Caught deadly signal SEGV"

Bram Moolenaar wrote: Charles Campbell wrote: Charles Campbell wrote: v...@googlecode.com wrote: Comment #4 on issue 230 by brammool...@gmail.com: "Vim: Caught deadly signal SEGV" http://code.google.com/p/vim/issues/detail?id=230 The errors in the libfontconfig.so look like a library problem

Re: Patch 7.4.335

Bram Moolenaar wrote: Patch 7.4.335 Problem:No digraph for the new rouble sign. Solution: Add the digraphs =R and =P. Files: src/digraph.c, runtime/doc/digraph.txt Hello, Bram: This patch isn't on ftp.home.vim.org yet. Chip Campbell -- -- You received this message from the "vim_de

Re: latex spell check disabled if set filetype=latex

led a texDocZone by the syntax highlighting), and it does work for the letter document classes without sectioning. Regards, Chip Campbell Hello, there is c:\Program Files\Vim\vim74\syntax\tex.vim that says " Maintainer: Charles E. Campbell " Last Change: Mar 20, 2014 &quo

Re: is not highlighted (syntax/vim.vim)

Kenichi Ito wrote: Hi Chip, I tried vim.vim v7.4-30 in your website, but is not highlighted. This patch fixes it. --- diff --git a/runtime/syntax/vim.vim b/runtime/syntax/vim.vim index e86611a..b9b815c 100644 --- a/runtime/syntax/vim.vim +++ b/runtime/syntax/vim.vim @@ -327,7 +327,7 @@ syn ke

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 ove

Re: odd character drawing problem

John Little wrote: On Saturday, July 19, 2014 1:56:30 AM UTC+12, Charles Campbell wrote: I've been through all the fonts that have "mono" in their names ... >From mbyte.txt: "Double-width characters are supported." It appears to me that that's what you're doing, and that it should work. My r

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 syntax/sh

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 -- -- Y

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 B

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 ftp.nl

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 patch

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 <

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 <

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 n

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() retu

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

Roland Eggner wrote: On 2015-02-20 Friday at 20:02 -0500 James McCoy wrote: On Fri, Feb 20, 2015 at 10:52:51PM +0100, Bram Moolenaar wrote: James McCoy wrote: On Thu, Feb 19, 2015 at 08:38:02PM -0500, Charles E Campbell wrote: If after the ln -s file1 file2, one then types touch file1

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 tha

[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: Maintainer of runtime/syntax/make.vim

C Campbell > On Feb 23, 2015, at 4:28 PM, Bram Moolenaar wrote: > > > Matthias wrote: > >> I tried to contact Claudio Fleiner, but got no response. >> He maintains the syntax file for make. >> What is the correct way now, >> to deal with bugfixes for this file? >> Is there anyone on this lis

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 highli

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 http://www.drchip.org/astronaut/vim/index.html#NET

Re: Syntax highlight error in .vim ??

Ken Takata wrote: > Hi, > > 2016/7/20 Wed 13:41:57 UTC+9 Tony Mechelynck wrote: >> On Wed, Jul 20, 2016 at 4:55 AM, skywind3...@163.com >> wrote: >>> Reproduce: >>> 1. vim abc.vim: >>> 2. add this line: >>> let my_dict = { "key1":"val1", "key2": "val2", "key3": "val3", >>> "key4":"val4" } >>> >>>

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 .v

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? > >>> some

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 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 'wrapscan' on, since

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 from

Re: [vim/vim] Broken syntax in tex when defining custom math column type (#984)

Bart Baker wrote: > \documentclass{article} > > \newcolumntype{R}{>{$}r<{$}} > > \begin{document} > > This is colored as if it is in a math section, rather than the default > text > color. > > \end{document} I get the following when I apply latex to the file containing the above example: baker01.

problems with git and maintaining files

Hello: I'm having a problem with using git and making local changes to files I maintain. In particular: I make changes to syntax/sh.vim (locally), and then git fails: runtime/syntax/sh.vim: needs merge runtime/syntax/sh.vim: needs merge runtime/syntax/sh.vim: unmerged (711971ea4ae7b3a72c2062c181

Re: problems with git and maintaining files

Christ van Willegen wrote: > > Op 19 aug. 2016 22:05 schreef "Charles E Campbell" > mailto:drc...@campbellfamily.biz>>: > > My solution so far > > involves manually saving the changed files, wiping out the repository > > copy on > > my local sys

Re: problems with git and maintaining files

Christ van Willegen wrote: > > Op 19 aug. 2016 22:28 schreef "Charles E Campbell" > mailto:drc...@campbellfamily.biz>>: > > > > > I tried git stash push instead of git push -- and it still doesn't work: > > Probably only 'stash' then...

Re: problems with git and maintaining files

Charles E Campbell wrote: > Christ van Willegen wrote: >> Op 19 aug. 2016 22:28 schreef "Charles E Campbell" >> mailto:drc...@campbellfamily.biz>>: >>> I tried git stash push instead of git push -- and it still doesn't work: >> Probably on

Re: problems with git and maintaining files

Marius Gedminas wrote: > On Fri, Aug 19, 2016 at 04:56:34PM -0400, Charles E Campbell wrote: >> Charles E Campbell wrote: >>> Christ van Willegen wrote: >>>> Op 19 aug. 2016 22:28 schreef "Charles E Campbell" >>>> mailto:drc...@campbellfamily.biz

Re: problems with git and maintaining files

Christ van Willegen wrote: > > git stash > git checkout / git revert > git stash pop > ? > > Sorry, getting terse, tablets are not helpful for > cutting/pasting/editing... > I understand -- I try to avoid using my tablet to say much via email. I'll give this a go the next time I have the problem.

Re: [vim/vim] Changed DB_COUNT to 16 (#1000)

Marius Gedminas wrote: > > I once needed to diff more files than vim would support (IIRC I was > comparing lists of installed packages across five servers). Having to > recompile vim for that was a pain. > > Forgetting that you set diff on for a buffer is already possible when > you're diffing just

Re: [vim/vim] Vim cryptmethod is not authenticated (#638)

Marvin Renich wrote: > Bugs in Vim's encryption algorithms should, of course, be fixed if > possible, but not in a way that prevents access to older encrypted > data files. That includes keeping, for a significant amount of time > (two years? I'm not sure how long), the ability to write files that

syntax clear -- should it be removed from syntax files?

Hello: In nosing around the help, I see for :help filetypedetect-changed the following: The distributed syntax files no longer contain "syntax clear". That makes it possible to include one in the other without tricks. The syntax is now cleared when the 'syntax' option is set (by an autocommand

unexpected "ad behavior

Hello: With the following 6 lines: (the last three are empty) - hello world! hello world! hello world! - Put cursor on line 4, use ctrl-v and move down 2 lines. Press "ad . This operation grabs the visually selected text and puts it into register a. (ie. the

Re: unexpected "ad behavior

Tony Mechelynck wrote: > On Wed, Sep 7, 2016 at 7:06 AM, Tony Mechelynck > wrote: >> On Wed, Sep 7, 2016 at 6:22 AM, Charles E Campbell >> wrote: >>> Hello: >>> >>> With the following 6 lines: (the last three are empty) >>> -

Re: [vim/vim] Runtime files do not include sbt.vim (#1051)

Denton Liu wrote: > > Inside |runtime/compiler|, a file is missing, |sbt.vim|, which can be > found here > . This > is because |ftplugin/scala.vim| > >

Re: gx doesn't work anymore with vim 8.0.4

Cesar Romani wrote: > I'm using vim 8.0.4 on Windows 7 compiled with MinGW. > When doing gx on an url I get: > > E117: Unknown function: netrw#CheckIfRemote > E116: Invalid arguments for function netrw#BrowseX > > Many thanks in advance, netrw#CheckIfRemote is in v156 which is distributed with vim

Re: [vim/vim] fix syntax error in runtime/autoload/netrw.vim (#1090)

haya14busa wrote: > > Closed #1090 . > > Thank you -- I've applied your patches, albeit to a later netrw than you used (v162bNR). I need to work on it some more before releasing it. Regards, Chip Campbell -- -- You received this message from the "vim_dev"

Re: gvim and ASCII glyphs

Matěj Cepl wrote: > So, for example how to make >= and <= be included so that they > translate into (glyphs from :digraphs): > > =< ≤ 8804 > >= ≥ 8805 > > Matěj > Hello: If you're using utf-8, its easy to get the glyph transform with mathmenu.vim (comes with http://www.drchip.org/astron

Re: gvim and ASCII glyphs

Matěj Cepl wrote: > On 2016-10-27, 11:58 GMT, Tony Mechelynck wrote: >> Ohhh, so that's what you mean. Well, here is another try: Not >> being imitated, or not being a copycat himself, don't >> necessarily mean that Dr. Chip is wrong, especially with Vim, >> which prides himself about allowing t

  1   2   3   4   >