Re: big with windows codepage 65001 (UTF-8)

Hi Ben, 2016/2/27 Sat 9:05:32 UTC+9 Ben Fritz wrote: > On Friday, February 26, 2016 at 4:29:32 PM UTC-6, Ken Takata wrote: > > However recent vim.exe doesn't use 'termencoding'. > > > > Woah, when did that happen? It's 7.4.852. Now vim.exe uses Unicode API. Regards, Ken Takata -- -- You

Re: big with windows codepage 65001 (UTF-8)

On Friday, February 26, 2016 at 4:29:53 PM UTC+1, Ben Fritz wrote: > > Works fine, for me. > > > What is your 'termencoding' setting after launching Vim in this way (if you > can see that)? It should match (i.e. it should be cp65001). Thanks. I've set encoding to utf8 in my vimrc and it is

Re: Replace c cast to c++ style cast

Hi, > There is a switch in g++ that warns about c style casts. > I will try to fix those but there are plenty in the project where I > am working. > > Can someone recommend a function that would allow to do this in vim? In lh-cpp (*), I have 3 mappings that transform C casts into C++ casts --

Re: Replace c cast to c++ style cast

skeept wrote: > There is a switch in g++ that warns about c style casts. > I will try to fix those but there are plenty in the project where I am > working. > > Can someone recommend a function that would allow to do this in vim? > > Or outside vim, can anyone recommend a tool

Re: big with windows codepage 65001 (UTF-8)

On Friday, February 26, 2016 at 4:29:32 PM UTC-6, Ken Takata wrote: > However recent vim.exe doesn't use 'termencoding'. > Woah, when did that happen? -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more

Re: Search for line containing stringB, not preceded by a line containing stringA

On Friday, February 26, 2016 at 4:58:01 PM UTC-5, Ben Fritz wrote: > On Friday, February 26, 2016 at 3:25:33 PM UTC-6, Paul wrote: >> On Friday, February 26, 2016 at 12:26:21 PM UTC-5, Ben Fritz wrote: >>> On Friday, February 26, 2016 at 9:50:50 AM UTC-6, Paul wrote: >> >>

Re: gvim acts differently when invoked from mingw64 and ms-windows

Hi, 2016/2/26 Fri 17:16:41 UTC+9 Alexas Chee wrote: > I just built gvim (+tcl) with patch 1421 on mingw64. > I changed file syntax/vim.vim to highlight tcl embeded in vim script (line > 621): > let g:vimsyn_embed= "lmpPrt" > > When invoked directly from ms-windows, it acts just as expected; >

Re: big with windows codepage 65001 (UTF-8)

Hi, 2016/2/26 Fri 20:45:38 UTC+9 klo uo wrote: > Hi, > > > on Windows I've set my default code page to 65001 (UTF-8) > > > This is how vim looks like: > > > > ​ > > If I change code page to some other, like `chcp 866` if works as expected. Your vim.exe seems old. Try gvim74-1024.exe from

Re: Search for line containing stringB, not preceded by a line containing stringA

On Friday, February 26, 2016 at 3:25:33 PM UTC-6, Paul wrote: > On Friday, February 26, 2016 at 12:26:21 PM UTC-5, Ben Fritz wrote: > > On Friday, February 26, 2016 at 9:50:50 AM UTC-6, Paul wrote: > > \(stringA.*\n\)\@ \(stringA.*\n\)\@ > >>> > >>> Move the newline

Re: Search for line containing stringB, not preceded by a line containing stringA

On Friday, February 26, 2016 at 12:26:21 PM UTC-5, Ben Fritz wrote: > On Friday, February 26, 2016 at 9:50:50 AM UTC-6, Paul wrote: >> On Wednesday, February 24, 2016 at 3:01:24 PM UTC-5, Ben Fritz >> wrote: >>> On Wednesday, February 24, 2016 at 12:00:22 PM UTC-6, Paul wrote: I have a text

Replace c cast to c++ style cast

There is a switch in g++ that warns about c style casts. I will try to fix those but there are plenty in the project where I am working. Can someone recommend a function that would allow to do this in vim? Or outside vim, can anyone recommend a tool that would be useful in doing this? Thank

Re: Packages

On Friday, February 26, 2016 at 12:02:42 PM UTC-6, Bram Moolenaar wrote: > Christian Brabandt wrote: > > > > Really a plugin directory is necessary? That sounds awkward. What about > > colorschemes, indent or ftplugins and syntax scripts? > > > > We could still change it, right? > > > > > It

Re: Packages

Christian Brabandt wrote: > On Fr, 26 Feb 2016, Bram Moolenaar wrote: > > > > > Matthew Desjardins wrote: > > > > > There have been a couple of people posting about how the new package > > > feature can, in its current state, replace Pathogen. > > > > > >

Re: Packages

On Fr, 26 Feb 2016, Bram Moolenaar wrote: > > Matthew Desjardins wrote: > > > There have been a couple of people posting about how the new package > > feature can, in its current state, replace Pathogen. > > > > https://groups.google.com/d/msg/vim_dev/BN5DuHpzzBc/OjoGDSqeEQAJ > >

Re: Search for line containing stringB, not preceded by a line containing stringA

On Friday, February 26, 2016 at 9:50:50 AM UTC-6, Paul wrote: > On Wednesday, February 24, 2016 at 3:01:24 PM UTC-5, Ben Fritz wrote: > > On Wednesday, February 24, 2016 at 12:00:22 PM UTC-6, Paul wrote: > > > I have a text file and I would like to compose a regular expression > > > that matches

Re: gvim acts differently when invoked from mingw64 and ms-windows

Hi, Christian, Thanks for your comment. I compared 2 outputs of : scriptnames, turned out that the one in windows has two more lines: $VIMRUNTIME\syntax\tcl.vim $VIMRUNTIME\indent\vim.vim All others are the same: same runtime path and other scripts. Wonder why gvim refuses to load those 2

Re: Packages

Matthew Desjardins wrote: > There have been a couple of people posting about how the new package > feature can, in its current state, replace Pathogen. > > https://groups.google.com/d/msg/vim_dev/BN5DuHpzzBc/OjoGDSqeEQAJ > https://groups.google.com/d/msg/vim_use/QHqDKtdqUkk/PY7WydFdAQAJ > >

Re: how to transfer output of ':.w !sh' back to current buffer

> On Friday, February 26, 2016 at 11:29:48 AM UTC-5, Roman wrote: > > I use ':.w !sh' to run some lines with shell commands > > Is any way to transfer output of this commands back to buffer or maybe to > > split buffer window or do something like ':r !sh $current_line' > > You could always just

Re: how to transfer output of ':.w !sh' back to current buffer

On Friday, February 26, 2016 at 11:29:48 AM UTC-5, Roman wrote: > I use ':.w !sh' to run some lines with shell commands > Is any way to transfer output of this commands back to buffer or maybe to > split buffer window or do something like ':r !sh $current_line' You could always just *replace*

how to transfer output of ':.w !sh' back to current buffer

I use ':.w !sh' to run some lines with shell commands Is any way to transfer output of this commands back to buffer or maybe to split buffer window or do something like ':r !sh $current_line' -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below

Re: Search for line containing stringB, not preceded by a line containing stringA

On Wednesday, February 24, 2016 at 3:01:24 PM UTC-5, Ben Fritz wrote: > On Wednesday, February 24, 2016 at 12:00:22 PM UTC-6, Paul wrote: > > I have a text file and I would like to compose a regular expression > > that matches lines containing stringB but not preceded by a line > > containing

Re: big with windows codepage 65001 (UTF-8)

On Friday, February 26, 2016 at 5:45:38 AM UTC-6, klo uo wrote: > Hi, > > > on Windows I've set my default code page to 65001 (UTF-8) > > > This is how vim looks like: > > > > ​ > > If I change code page to some other, like `chcp 866` if works as expected. > > Works fine, for me. What

Re: Referring to a buffer, and :help help

On Friday, February 26, 2016 at 9:53:42 AM UTC-5, Jan wrote: > On Friday, 26 February, 2016 at 14:51:00 GMT, Matthew Desjardins wrote: > >There is also ":sbuffer" which will take a buffer number or partial buffer > >name. > > Ah, thanks. I actually just realised that #2 does with with :split!

Re: Referring to a buffer, and :help help

On Friday, 26 February, 2016 at 14:51:00 GMT, Matthew Desjardins wrote: There is also ":sbuffer" which will take a buffer number or partial buffer name. Ah, thanks. I actually just realised that #2 does with with :split! But I'd still like to know what to search for for help on those

Re: Referring to a buffer, and :help help

On Friday, February 26, 2016 at 9:46:16 AM UTC-5, Jan wrote: > I've two files loaded, FileNumberOne in buffer 1, and FileNumberTwo in buffer > 2, with just FileNumberOne currently shown. I want to open FileNumberTwo in a > new split window. I can do ":split FileNumberTwo" to achieve this.

Referring to a buffer, and :help help

I've two files loaded, FileNumberOne in buffer 1, and FileNumberTwo in buffer 2, with just FileNumberOne currently shown. I want to open FileNumberTwo in a new split window. I can do ":split FileNumberTwo" to achieve this. However, I don't want to type out or use completion to refer to

Packages

There have been a couple of people posting about how the new package feature can, in its current state, replace Pathogen. https://groups.google.com/d/msg/vim_dev/BN5DuHpzzBc/OjoGDSqeEQAJ https://groups.google.com/d/msg/vim_use/QHqDKtdqUkk/PY7WydFdAQAJ Could someone explain how? It doesn't seem

big with windows codepage 65001 (UTF-8)

Hi, on Windows I've set my default code page to 65001 (UTF-8 ) This is how vim looks like: ​ If I change code page to some other, like `chcp 866` if works as expected. > vim --version VIM -

Re: gvim acts differently when invoked from mingw64 and ms-windows

Hi Junrin! On Fr, 26 Feb 2016, Junrin Sei wrote: > I just built gvim (+tcl) with patch 1421 on mingw64. > I changed file syntax/vim.vim to highlight tcl embeded in vim script (line > 621): > let g:vimsyn_embed= "lmpPrt" > > When invoked directly from ms-windows, it acts just as expected; >

gvim acts differently when invoked from mingw64 and ms-windows

I just built gvim (+tcl) with patch 1421 on mingw64. I changed file syntax/vim.vim to highlight tcl embeded in vim script (line 621): let g:vimsyn_embed= "lmpPrt" When invoked directly from ms-windows, it acts just as expected; but when invoked from mingw bash, it fails to highlight tcl as if