On Mon, Jul 26, 2010 at 4:50 PM, Graham Percival
wrote:
> On Sun, Jul 25, 2010 at 12:43:40PM -0700, Patrick McCarty wrote:
>> IMO, that method is more reliable, and I don't have to worry about
>> modifying a ~/.vim/filetype.vim for LilyPond.
>
> Dudes! This is way simpler than we thought.
>
> The
On Mon, Jul 26, 2010 at 4:58 PM, Patrick McCarty wrote:
> On Mon, Jul 26, 2010 at 4:50 PM, Graham Percival
> wrote:
>> On Sun, Jul 25, 2010 at 12:43:40PM -0700, Patrick McCarty wrote:
>>> IMO, that method is more reliable, and I don't have to worry about
>>> modifying a ~/.vim/filetype.vim for Li
On Mon, Jul 26, 2010 at 4:50 PM, Graham Percival
wrote:
> On Sun, Jul 25, 2010 at 12:43:40PM -0700, Patrick McCarty wrote:
>> IMO, that method is more reliable, and I don't have to worry about
>> modifying a ~/.vim/filetype.vim for LilyPond.
>
> Dudes! This is way simpler than we thought.
>
> The
On Sun, Jul 25, 2010 at 12:43:40PM -0700, Patrick McCarty wrote:
> IMO, that method is more reliable, and I don't have to worry about
> modifying a ~/.vim/filetype.vim for LilyPond.
Dudes! This is way simpler than we thought.
The docs should be:
--
@node Vim mode
For VIM, a ‘vimrc’ is suppl
On Sun, Jul 25, 2010 at 07:18:24PM -0600, Colin Campbell wrote:
>As I understand it, the supported filetype.vim and vimrc are only found in
>the /vim directory of a source tree.
>Users who install binaries will need to get a copy of the source matching
>their installed version of Li
Hi Colin,
On 2010-07-25, Colin Campbell wrote:
>
> As I understand it, the supported filetype.vim and vimrc are only
> found in the /vim directory of a source tree.
I wouldn't call either of files *supported*, since as far as I can
see, neither of them have ever been installed on a user's system
On 10-07-25 02:32 PM, Graham Percival wrote:
On Sun, Jul 25, 2010 at 01:34:23PM -0600, Colin Campbell wrote:
On 10-07-25 12:45 PM, Graham Percival wrote:
I'm a bit suspicious about commit
4578dfbfdab5704ffc5317adfb252cb242f30115
1. AFAIK, we definitely want people creating or modifyi
Graham Percival wrote Sunday, July 25, 2010 9:32 PM
On Sun, Jul 25, 2010 at 01:34:23PM -0600, Colin Campbell wrote:
On 10-07-25 12:45 PM, Graham Percival wrote:
I'm a bit suspicious about commit
4578dfbfdab5704ffc5317adfb252cb242f30115
1. AFAIK, we definitely want people creating or modifying
On Sun, Jul 25, 2010 at 01:34:23PM -0600, Colin Campbell wrote:
> On 10-07-25 12:45 PM, Graham Percival wrote:
>> I'm a bit suspicious about commit
>> 4578dfbfdab5704ffc5317adfb252cb242f30115
>>
>> 1. AFAIK, we definitely want people creating or modifying
>> ~/.vim/filetype.vim
>
> I installed Vim
On Sun, Jul 25, 2010 at 11:45 AM, Graham Percival
wrote:
> I'm a bit suspicious about commit
> 4578dfbfdab5704ffc5317adfb252cb242f30115
>
> 1. AFAIK, we definitely want people creating or modifying
> ~/.vim/filetype.vim
> It's just possible that it might be on a different location on
> windows, bu
On 10-07-25 12:45 PM, Graham Percival wrote:
I'm a bit suspicious about commit
4578dfbfdab5704ffc5317adfb252cb242f30115
1. AFAIK, we definitely want people creating or modifying
~/.vim/filetype.vim
It's just possible that it might be on a different location on
windows, but most people using vim
On Sun, Jul 25, 2010 at 1:45 PM, Graham Percival
wrote:
> I'm a bit suspicious about commit
> 4578dfbfdab5704ffc5317adfb252cb242f30115
>
> 3. I think the previous runtimepath was wrong, but the new one
> isn't much better -- it should point to the locally-installed
> version of lilypond, which wil
I'm a bit suspicious about commit
4578dfbfdab5704ffc5317adfb252cb242f30115
1. AFAIK, we definitely want people creating or modifying
~/.vim/filetype.vim
It's just possible that it might be on a different location on
windows, but most people using vim on windows would probably be
using cygwin, so t
13 matches
Mail list logo
