On 07/30/2016 09:54 AM, meino.cra...@gmx.de wrote:
Hi,
I got some problems to comile vim (current patch level) on an Orangs
PI PC (Allwinner H3) and Armbian Linux.
The make command:
./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge
--enable-luainterp=yes --enable-pyt
you could define your own set of static rule checks so
that the editor would highlight where those are amiss instead of having
to run a third party checker... maybe not a full fledged analyzer as
that seems quite taxing, but some basic parsing might be nice.
I'd like to follow your progr
On 03/12/2016 06:22 PM, Gary Johnson wrote:
On 2016-03-11, Yang Luo wrote:
I'm a vim newbie.
for example this code block:
///
wire [3:0] w_buff_length;//0--15
always @(posedge clk or negedge rst_n)
if (!rst_n) begin
for(i=0; i< w_buff_length; i=
Sorry to bug.Do i have to recreate the whole directory structure as found in
/usr/share/vim?
Not at all. You don't even need to create the .vim directory if you
don't need it. If you do, then just create whatever you currently
require, you'll then go about filling it up with other stuff once you
Hi
Thanks for the advice,i guess i'm trying to run before i could run.However i'm
still in the dark because there's no .vim file either in my home directory
The .vim file in your home directory is actually a directory itself. If
it doesn't exist you can just go ahead and create it. This is
come in handy in the future.
Once again, thanks!
-- Sycc
On 10/29/2015 11:00 AM, Charles E Campbell wrote:
sycc wrote:
Hello all!
I'm trying to write a function for switching between the current
buffer syntax highlighting and whitespace, but I'm really new to vim
scripting and suc
ghlighting, so I'd need it to go back to the one
I'd changed to instead of the filetype.
Thank you very much!
-- Sycc
On 10/28/2015 08:20 PM, Nikolay Pavlov wrote:
2015-10-29 2:19 GMT+03:00 Nikolay Pavlov :
2015-10-29 0:52 GMT+03:00 sycc :
Thank you all for the answers!
Yes, I
27;t work the way I though they did...? I'd
like to store the syntax of each buffer I have open, how can this be done?
-- Sycc
On 10/28/2015 12:38 PM, David Fishburn wrote:
> Didn't quite follow what you are tying to do with whitespace.
>
...
> I use this plu
highlighting.
Now, I'm pretty sure I'm missing something important here... given that
I'm pretty new to vim scripting and such. I was under the impression
that b: variables were local to buffers, so I thought I could create one
per opened buffer and this would work, does it not be
elated to this and no, none of them are
being mapped to anything. 'c' does the same thing.
I'll try leaving this vim session open in case any of you think there's
something I could try to troubleshoot this. I've closed the files I was
working on and re-opened them with anoth
#x27;s' command that behaves weirdly. If I go into insert mode I
can type an "s" without trouble whatsoever, same thing in any other
applications, terminal, etc.
I'll keep my eyes open until it happens again and check if it's somehow
been remapped.
Thank you all f
I'm not
holding my breath for it being in the vimrc =P
On 09/21/2015 04:58 AM, Nikolay Pavlov wrote:
2015-09-21 1:55 GMT+03:00 sycc :
Greetings everyone!
So far I've always managed to google my way out of whatever came up in vim,
but this time I have no idea what's going on a
Greetings everyone!
So far I've always managed to google my way out of whatever came up in
vim, but this time I have no idea what's going on and would really
appreciate some help.
A couple of days ago I've started noticing some weird behavior with the
's' command. I'd be using vim for a coupl
13 matches
Mail list logo