I recently tried to access a non-existant colorscheme (:colorscheme idontexist)
and got the expected error message ("Cannot find color scheme..."), but was
surprised how quickly it disappeared (after about one second). Is there a
setting that controls this?
--
--
You received this message fro
On Tuesday, December 31, 2013 10:01:39 PM UTC-6, Dejan Ranisavljevic wrote:
> I have been using vim for past 2,3 years, but there are still some issues i
> am not able to come over.
>
> I find it really convenient to have windows managed manually. I tried
> buffkill for some time,
> but it does
On Wednesday, January 1, 2014 7:36:45 AM UTC-6, MarcWeber wrote:
>
> I even consider moving vim RUNTIEMPATH into its own community maintained
>
> repository could be a success - because a lot of things could be
>
> improved - and we could work on new standards such as "asynchronous task
>
> lis
On 22:47 Wed 01 Jan , Erik Christiansen wrote:
> On 01.01.14 11:07, Marcin Szamotulski wrote:
> > On 20:01 Tue 31 Dec , Dejan Ranisavljevic wrote:
> > > Ideally i would delete that new buffer and get a previous buffer i was
> > > working on.
> ...
>
> > :BufWipe commands to delete/wipe ou
On Wednesday, January 1, 2014 5:36:45 PM UTC+4, MarcWeber wrote:
> Maybe you've noticed the discussion on vim-dev about providing a single
> repository containing all vim plugin repository information.
>
> The goal is to allow multiple parties (VAM, NeoBundle, ..) to use this
> repository.
>
> Th
Maybe you've noticed the discussion on vim-dev about providing a single
repository containing all vim plugin repository information.
The goal is to allow multiple parties (VAM, NeoBundle, ..) to use this
repository.
Thinking about it I come up with:
- my UltiSnips fork
- Snipmate (and vim-snippet
On 01.01.14 11:07, Marcin Szamotulski wrote:
> On 20:01 Tue 31 Dec , Dejan Ranisavljevic wrote:
> > Ideally i would delete that new buffer and get a previous buffer i was
> > working on.
...
> :BufWipe commands to delete/wipe out a buffer but do not close the
> window. They do not open previ
On 20:01 Tue 31 Dec , Dejan Ranisavljevic wrote:
> I have been using vim for past 2,3 years, but there are still some issues i
> am not able to come over.
>
> I find it really convenient to have windows managed manually. I tried
> buffkill for some time,
> but it doesn't work always as expe
On 01/01/14 05:01, Dejan Ranisavljevic wrote:
I have been using vim for past 2,3 years, but there are still some issues i am
not able to come over.
I find it really convenient to have windows managed manually. I tried buffkill
for some time,
but it doesn't work always as expected.
To be more
I have been using vim for past 2,3 years, but there are still some issues i am
not able to come over.
I find it really convenient to have windows managed manually. I tried buffkill
for some time,
but it doesn't work always as expected.
To be more precise, lets say i am working on something, an
10 matches
Mail list logo