Hi all,
I see that there is a set of vim tools for csound . . . but the last  
update appears to date from early in version 4.
Does anyone use this, and if so, is there a slightly newer version,  
possibly with the autocomplete functions?
It sounds worth my while enough/a decent way to learn vim scripting  
that I might be interested in taking it up for myself, but I'd also  
like to see if anyone else is using vim to edit csound anymore.
Greg


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

on 2010-05-22 at 21:33 gmschroeder wrote:

>I see that there is a set of vim tools for csound . . . but the last  
>update appears to date from early in version 4.
>Does anyone use this, and if so, is there a slightly newer version,  

every now and then someone asks this very same question, and my answer
is always the same: i do have a newer version, but i think it needs
some polishing before releasing it. then i promise to do it "soon" and
there it goes to my to-do list, where it has been for so many years.
give me a couple of days and i'll try to keep my word this time...

>possibly with the autocomplete functions?

that is fairly easy to implement but i'm not sure it would be terribly
useful. could you give me an example of what kind of auto-completion
you have in mind?





Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I was just talking about (what I understand to be) a native function  
in vim:
http://vim.wikia.com/wiki/Any_word_completion
I'd like to see opcodes and their variables spelled out - for  
example, type "asig oscil" and then ctrl-n/p to see everything  
matching those initial characters and maybe get the generic names for  
the variables from the manual as well. Then I don't need to look at  
the manual constantly - that's what would make this useful for me,  
anyway.

I'd love it to work out so one could tab through the variables to  
assign them immediately after one chooses an opcode, but I'd never  
ask someone to do that for me. Perhaps an excuse to teach myself vim  
scripting . . .

Greg

On May 22, 2010, at 11:30 PM, luis jure wrote:

>
> on 2010-05-22 at 21:33 gmschroeder wrote:
>
>> I see that there is a set of vim tools for csound . . . but the last
>> update appears to date from early in version 4.
>> Does anyone use this, and if so, is there a slightly newer version,
>
> every now and then someone asks this very same question, and my answer
> is always the same: i do have a newer version, but i think it needs
> some polishing before releasing it. then i promise to do it "soon" and
> there it goes to my to-do list, where it has been for so many years.
> give me a couple of days and i'll try to keep my word this time...
>
>> possibly with the autocomplete functions?
>
> that is fairly easy to implement but i'm not sure it would be terribly
> useful. could you give me an example of what kind of auto-completion
> you have in mind?
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/? 
> group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Luis: Release early, release often. That is the One True Way®

On Sat, May 22, 2010 at 11:35, gmschroeder  wrote:
> I was just talking about (what I understand to be) a native function in vim:
> http://vim.wikia.com/wiki/Any_word_completion
> I'd like to see opcodes and their variables spelled out - for example, type
> "asig oscil" and then ctrl-n/p to see everything matching those initial
> characters and maybe get the generic names for the variables from the manual
> as well. Then I don't need to look at the manual constantly - that's what
> would make this useful for me, anyway.
>
> I'd love it to work out so one could tab through the variables to assign
> them immediately after one chooses an opcode, but I'd never ask someone to
> do that for me. Perhaps an excuse to teach myself vim scripting . . .
>
> Greg
>
> On May 22, 2010, at 11:30 PM, luis jure wrote:
>
>>
>> on 2010-05-22 at 21:33 gmschroeder wrote:
>>
>>> I see that there is a set of vim tools for csound . . . but the last
>>> update appears to date from early in version 4.
>>> Does anyone use this, and if so, is there a slightly newer version,
>>
>> every now and then someone asks this very same question, and my answer
>> is always the same: i do have a newer version, but i think it needs
>> some polishing before releasing it. then i promise to do it "soon" and
>> there it goes to my to-do list, where it has been for so many years.
>> give me a couple of days and i'll try to keep my word this time...
>>
>>> possibly with the autocomplete functions?
>>
>> that is fairly easy to implement but i'm not sure it would be terribly
>> useful. could you give me an example of what kind of auto-completion
>> you have in mind?
>>
>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>



-- 

Saludos,
Felipe Sateler


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"