Christian Brabandt wrote:
On Fri, September 10, 2010 12:47 am, Rahul wrote:
If I do :AnsiEsc I get this error:
Error detected while processing function AnsiEsc#AnsiEsc:
line 139:
E62: Nested \=
E475: Invalid argument: ansiStop^I^I"\e\[0\{1,2}\=m"
I am CC'ing Charles. As he is the ma
On Fri, September 10, 2010 12:47 am, Rahul wrote:
> If I do :AnsiEsc I get this error:
>
> Error detected while processing function AnsiEsc#AnsiEsc:
> line 139:
> E62: Nested \=
> E475: Invalid argument: ansiStop^I^I"\e\[0\{1,2}\=m"
I am CC'ing Charles. As he is the maintainer, he probably knows
On Fri, September 10, 2010 12:57 am, Rahul wrote:
> :help AnsiEsc still doesn't work. Is there a command that forces vim
> to re-index its help docs?
Yes, it's called :helptags. Run it like :helptags ~/.vim/doc/
(I think you need to restart vim) The vimball plugin is supposed to run it.
May be yo
On Thursday 09 September 2010 17:47:38 Rahul wrote:
> On Sep 9, 5:17 pm, sc wrote:
> > the first thing i'd try is renaming those files so they end
> > with .vim -- restart vim and see if you can't use it now
> Did that. Renamed files. Restarted vim
> > you're right to wonder why they have funny
On Sep 9, 4:58 pm, Christian Brabandt wrote:
> That does not sound right. Usually those files should be called .vim.
I renamed them now. They had an additional extension before that
looked like a control character
> I haven't used AnsiEsc yet, but if I see that right, you should have the
> follo
On Sep 9, 5:17 pm, sc wrote:
>
> the first thing i'd try is renaming those files so they end
> with .vim -- restart vim and see if you can't use it now
Did that. Renamed files. Restarted vim
> you're right to wonder why they have funny endings -- did you
> gunzip the vba.gz before vimming it?
Y
On Thursday 09 September 2010 16:47:31 Rahul wrote:
> On Sep 9, 3:43 pm, sc wrote:
> > On Thursday 09 September 2010 15:06:39 Rahul wrote:
> > you need at least a big build to have conceal, normal won't
> > include it -- look at the output of
> >
> > :ver
> Thanks! I did a "huge" build now.
Hi Rahul!
On Do, 09 Sep 2010, Rahul wrote:
> On Sep 9, 3:43 pm, sc wrote:
> > On Thursday 09 September 2010 15:06:39 Rahul wrote:
> > you need at least a big build to have conceal, normal won't
> > include it -- look at the output of
> >
> > :ver
>
> Thanks! I did a "huge" build now. Have a
On Sep 9, 3:43 pm, sc wrote:
> On Thursday 09 September 2010 15:06:39 Rahul wrote:
> you need at least a big build to have conceal, normal won't
> include it -- look at the output of
>
> :ver
Thanks! I did a "huge" build now. Have a +conceal and a +syntax. Still
can't use AnsiEsc successfully
On Thursday 09 September 2010 15:06:39 Rahul wrote:
> On Sep 8, 12:48 am, "Christian Brabandt"
wrote:
> > >> I was wondering if vim had a smart way of dealing with
> > >> this?!
> > >
> > > You could use the new conceal support in Vim 7.3.
> >
> > Have never used it, but I believe AnsiEsc[1] by
On Thu, Sep 09, 2010 at 01:06:39PM -0700, Rahul wrote:
> [snip]
>
> How do I enable the "conceal" option at compile time? I tried './
> configure --enable-conceal' but doesn't work.
>
> Or do I have to actually pull the patches from the conceal developers
> website? I am confused! Any tips?
You ne
On Sep 8, 12:48 am, "Christian Brabandt" wrote:
> >> I was wondering if vim had a smart way of dealing with this?!
>
> > You could use the new conceal support in Vim 7.3.
>
> Have never used it, but I believe AnsiEsc[1] by Charles Campbell does
> conceal color codes.
Thanks Christian and Simon. T
On Wed, September 8, 2010 1:16 am, Simon Ruderich wrote:
> On Tue, Sep 07, 2010 at 01:26:32PM -0700, Rahul wrote:
>> Is there a convenient way to edit /etc/motd (or for that matter any
>> other file that has color codes / multibyte characters in it)? The
>> usual problem is that many if the file ha
On Tue, Sep 07, 2010 at 01:26:32PM -0700, Rahul wrote:
> Is there a convenient way to edit /etc/motd (or for that matter any
> other file that has color codes / multibyte characters in it)? The
> usual problem is that many if the file has a color code (say,
> ^[[33m^[[1m ) then this occupies multip
Is there a convenient way to edit /etc/motd (or for that matter any
other file that has color codes / multibyte characters in it)? The
usual problem is that many if the file has a color code (say,
^[[33m^[[1m ) then this occupies multiple characters in the editor but
zero characters when finally di
15 matches
Mail list logo
