hi guys,
when using gf vim can open a file with the same name in the current directory.
I use vim for verilog files editing in Verilog syntax one can see something
line this
(.);
I want to be able to open the .v file in current directory when
cursor is on the
On 5 February 2016 at 17:23, Christian Brabandt wrote:
> On Fr, 05 Feb 2016, Dominique Pellé wrote:
>
>> You're using vim-7.4.827. The latest vim is vim-7.4.1261
>> so you're missing quite a few patches.
>>
>> Since you wrote that you compiled vim yourself, could you
>>
On 08.02.16 10:50, Matt Ackeret wrote:
> The next text will be from the Russian input method:
> АВСРОМИС
>
> This wasn't typed in Terminal, but I just typed Russian characters
> into Terminal, and they showed up fine.
Viewing Cyrillic, Greek, or Russian characters doesn't work for me in
"xterm"
On 2016-02-08 03:41, zismad wrote:
> hi guys,
>
> when using gf vim can open a file with the same name in the current
> directory. I use vim for verilog files editing in Verilog syntax
> one can see something line this
>
> (.);
>
> I want to be able to open the .v file in current
>
On Sunday, January 31, 2016 at 4:43:25 AM UTC-5, Justin Dearing wrote:
> I'd like to edit EBCDIC encoded files in VIM on windows vim --version shows
> this:
I just read all the answers here. Apparently I was not subscribed to this post
because the moderator didn't approve me, and I forgot all
On Sunday, January 31, 2016 at 6:14:49 PM UTC-5, Eric Christopherson wrote:
> I find it interesting to see
> this question, just a few days after reading a page laying out the case
> for NeoVim . . . it
> gave EBCDIC support as an example of something that no one would ever
> use Vim for!
Ok that
> On Feb 6, 2016, at 3:47 PM, Tony Mechelynck
> wrote:
>
> http://users.skynet.be/antoine.mechelynck/other/keybbe.htm — but I
> don't know how one would get those non-ASCII letters on a
> (non-international) QWERTY keyboard meant for en-US.
>
Use a different
Christian Brabandt wrote:
> Hi Bram!
>
> On Sa, 06 Feb 2016, Bram Moolenaar wrote:
>
> > There are a few more places in the docs that need to point to this flag.
> >
> > Is there a better character than "_" to use for this?
>
> Updated patch uses 'z'
>
> Also added some more references to
Justin Dearing wrote:
> I'd like to edit EBCDIC encoded files in VIM on windows vim --version shows
> this:
>
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Sep 16 2015 08:44:57)
> Included patches: 1-872
> Compiled by
> Huge version without GUI. Features included (+) or not
On Mon, Feb 8, 2016 at 3:14 PM Nikolay Aleksandrovich Pavlov <
zyx@gmail.com> wrote:
> Also do you have an access to such mainframe and can you test whether
> *Vim* compiles there with EBCDIC macros defined?
I'm not a mainframe guy I'm dealing with the IBM i (formerly AS/400).
That's a
Hi Bram!
On Sa, 06 Feb 2016, Bram Moolenaar wrote:
> There are a few more places in the docs that need to point to this flag.
>
> Is there a better character than "_" to use for this?
Updated patch uses 'z'
Also added some more references to it in the documentation.
> Also, plugin writers
On 8 February 2016, Justin Dearing wrote:
> On Mon, Feb 8, 2016 at 3:14 PM Nikolay Aleksandrovich Pavlov <
> zyx@gmail.com> wrote:
>
> > Also do you have an access to such mainframe and can you test
> > whether *Vim* compiles there with EBCDIC macros defined?
>
>
> I'm
2016-02-08 21:35 GMT+03:00 Justin Dearing :
> On Sunday, January 31, 2016 at 6:14:49 PM UTC-5, Eric Christopherson wrote:
>> I find it interesting to see
>> this question, just a few days after reading a page laying out the case
>> for NeoVim . . . it
>> gave EBCDIC support as
13 matches
Mail list logo