first of all i should apologize for the long time it took, but here there are
at last the updated csound vim files.

this is not a proper release (i should update the web page and documentation)
but rather a pre-release for the list.

i guess people using these files know where to put them, so i'll skip the
detailed instructions. let me know if everything works (or not...)

copy to $VIM/vimfiles/syntax
http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.vim
http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_opcodes.vim

copy to $VIM/vimfiles/doc
http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.txt

copy to $VIM/vimfiles/templates
http://www.eumus.edu.uy/docentes/jure/csound/vim/new/template.csd

copy to $VIM/vimfiles/macros
http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_macros.vim


what's new?

- general cleanup and minor improvements to the syntax file (csound.vim)
- list of opcodes updated to 5.12
- NEW FEATURE: folding of these elements:
   - csd sections (options, orchestra, score)
   - instruments and user-defined opcodes
   - multi-line commented blocks with /*  */
- the help file is reduced to the synopsis and syntax of each opcode (i don't
  think anyone is reading the csound manual from within vim)
- minor improvements to the csd template and macros (these you should modify to
  suit your own taste anyway)


TODOs

- keep improving the syntax for better recognition of syntactic elements (i
  need feedback here, what elements aren't colorized?)
- new features like autocompletion. this is not difficult to do, it seems, but
  i don't know how it should behave, i'm not sure i would use it myself...
- more?

thank you to everyone using these files, and again, sorry for the delay.

best,

lj



--


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"

Hmm, this might make me swallow my own words... I'll try this out.

Do you have some documentation on what is provided by your macros? Or
do we have to read the source? :/

On Wed, Jun 9, 2010 at 19:45, Greg Schroeder  wrote:
> Great, thank you!
> I'll be working at getting this installed sometime in the next couple days.
>
> List - discuss setup here or elsewhere?
>
> Greg
>
> On Thu, Jun 10, 2010 at 8:37 AM, luis jure  wrote:
>>
>> first of all i should apologize for the long time it took, but here there
>> are
>> at last the updated csound vim files.
>>
>> this is not a proper release (i should update the web page and
>> documentation)
>> but rather a pre-release for the list.
>>
>> i guess people using these files know where to put them, so i'll skip the
>> detailed instructions. let me know if everything works (or not...)
>>
>> copy to $VIM/vimfiles/syntax
>> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.vim
>> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_opcodes.vim
>>
>> copy to $VIM/vimfiles/doc
>> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.txt
>>
>> copy to $VIM/vimfiles/templates
>> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/template.csd
>>
>> copy to $VIM/vimfiles/macros
>> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_macros.vim
>>
>>
>> what's new?
>>
>> - general cleanup and minor improvements to the syntax file (csound.vim)
>> - list of opcodes updated to 5.12
>> - NEW FEATURE: folding of these elements:
>>   - csd sections (options, orchestra, score)
>>   - instruments and user-defined opcodes
>>   - multi-line commented blocks with /*  */
>> - the help file is reduced to the synopsis and syntax of each opcode (i
>> don't
>>  think anyone is reading the csound manual from within vim)
>> - minor improvements to the csd template and macros (these you should
>> modify to
>>  suit your own taste anyway)
>>
>>
>> TODOs
>>
>> - keep improving the syntax for better recognition of syntactic elements
>> (i
>>  need feedback here, what elements aren't colorized?)
>> - new features like autocompletion. this is not difficult to do, it seems,
>> but
>>  i don't know how it should behave, i'm not sure i would use it myself...
>> - more?
>>
>> thank you to everyone using these files, and again, sorry for the delay.
>>
>> best,
>>
>> lj
>>
>>
>>
>> --
>>
>>
>> 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"

I said on another thread that vim doesn't do it for csound...

On Wed, Jun 9, 2010 at 23:09, Greg Schroeder  wrote:
> Why does this involve word-swallowing?
> IDE evangelist? Church of Emacs?
> Greg
>
> On Thu, Jun 10, 2010 at 12:05 PM, Felipe Sateler  wrote:
>>
>> Hmm, this might make me swallow my own words... I'll try this out.
>>
>> Do you have some documentation on what is provided by your macros? Or
>> do we have to read the source? :/
>>
>> On Wed, Jun 9, 2010 at 19:45, Greg Schroeder 
>> wrote:
>> > Great, thank you!
>> > I'll be working at getting this installed sometime in the next couple
>> > days.
>> >
>> > List - discuss setup here or elsewhere?
>> >
>> > Greg
>> >
>> > On Thu, Jun 10, 2010 at 8:37 AM, luis jure  wrote:
>> >>
>> >> first of all i should apologize for the long time it took, but here
>> >> there
>> >> are
>> >> at last the updated csound vim files.
>> >>
>> >> this is not a proper release (i should update the web page and
>> >> documentation)
>> >> but rather a pre-release for the list.
>> >>
>> >> i guess people using these files know where to put them, so i'll skip
>> >> the
>> >> detailed instructions. let me know if everything works (or not...)
>> >>
>> >> copy to $VIM/vimfiles/syntax
>> >> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.vim
>> >> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_opcodes.vim
>> >>
>> >> copy to $VIM/vimfiles/doc
>> >> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.txt
>> >>
>> >> copy to $VIM/vimfiles/templates
>> >> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/template.csd
>> >>
>> >> copy to $VIM/vimfiles/macros
>> >> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_macros.vim
>> >>
>> >>
>> >> what's new?
>> >>
>> >> - general cleanup and minor improvements to the syntax file
>> >> (csound.vim)
>> >> - list of opcodes updated to 5.12
>> >> - NEW FEATURE: folding of these elements:
>> >>   - csd sections (options, orchestra, score)
>> >>   - instruments and user-defined opcodes
>> >>   - multi-line commented blocks with /*  */
>> >> - the help file is reduced to the synopsis and syntax of each opcode (i
>> >> don't
>> >>  think anyone is reading the csound manual from within vim)
>> >> - minor improvements to the csd template and macros (these you should
>> >> modify to
>> >>  suit your own taste anyway)
>> >>
>> >>
>> >> TODOs
>> >>
>> >> - keep improving the syntax for better recognition of syntactic
>> >> elements
>> >> (i
>> >>  need feedback here, what elements aren't colorized?)
>> >> - new features like autocompletion. this is not difficult to do, it
>> >> seems,
>> >> but
>> >>  i don't know how it should behave, i'm not sure i would use it
>> >> myself...
>> >> - more?
>> >>
>> >> thank you to everyone using these files, and again, sorry for the
>> >> delay.
>> >>
>> >> best,
>> >>
>> >> lj
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >>
>> >> 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"
>>
>
>



-- 

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"

on 2010-06-09 at 23:05 Felipe Sateler wrote:

>Hmm, this might make me swallow my own words... I'll try this out.

felipe (and everybody), my vim tools are very basic indeed, it's not like
you're going to have the equivalent of winxound or anything: just syntax
colorization and a few simple macros for compiling and listening to your
orchestras without leaving vim (and now also folding). but... you'll have all
the editing power of vim, and that's for me more valuable than all the bells
and whistles that any front-end could possibly offer.


>Do you have some documentation on what is provided by your macros? Or
>do we have to read the source? :/

there's (somewhat outdated) documentation here:

http://www.eumus.edu.uy/docentes/jure/csound/vim/

i'll try to update it soon. anyway, the "source" is more than obvious. like i
said, the macros are very basic, just save the csd you're editing, compile it
with different options, and play the sound file. if you were expecting complex
plugins for score processing and algorithmic composition, you'll be greatly
disappointed...

anyway, if you're a vim enthusiast, you should give it a try. feedback is
always welcome.

best,

lj



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'm getting a 404 error when I go to the addresses below.
Could you double-check them and post your results?
Greg

On Jun 10, 2010, at 8:37 AM, luis jure wrote:

>
> first of all i should apologize for the long time it took, but here  
> there are
> at last the updated csound vim files.
>
> this is not a proper release (i should update the web page and  
> documentation)
> but rather a pre-release for the list.
>
> i guess people using these files know where to put them, so i'll  
> skip the
> detailed instructions. let me know if everything works (or not...)
>
> copy to $VIM/vimfiles/syntax
> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.vim
> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/ 
> csound_opcodes.vim
>
> copy to $VIM/vimfiles/doc
> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound.txt
>
> copy to $VIM/vimfiles/templates
> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/template.csd
>
> copy to $VIM/vimfiles/macros
> http://www.eumus.edu.uy/docentes/jure/csound/vim/new/csound_macros.vim
>
>
> what's new?
>
> - general cleanup and minor improvements to the syntax file  
> (csound.vim)
> - list of opcodes updated to 5.12
> - NEW FEATURE: folding of these elements:
>    - csd sections (options, orchestra, score)
>    - instruments and user-defined opcodes
>    - multi-line commented blocks with /*  */
> - the help file is reduced to the synopsis and syntax of each  
> opcode (i don't
>   think anyone is reading the csound manual from within vim)
> - minor improvements to the csd template and macros (these you  
> should modify to
>   suit your own taste anyway)
>
>
> TODOs
>
> - keep improving the syntax for better recognition of syntactic  
> elements (i
>   need feedback here, what elements aren't colorized?)
> - new features like autocompletion. this is not difficult to do, it  
> seems, but
>   i don't know how it should behave, i'm not sure i would use it  
> myself...
> - more?
>
> thank you to everyone using these files, and again, sorry for the  
> delay.
>
> best,
>
> lj
>
>
>
> --
>
>
> 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"

on 2010-06-12 at 09:46 gmschroeder wrote:

>I'm getting a 404 error when I go to the addresses below.

yes, sorry, that was just a temporary address. i'm at the process of updating
the whole site (half-way through it, yet).

you can now download the new files following the links from the main page:

http://www.eumus.edu.uy/docentes/jure/csound/vim/

best,

lj



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-06-19 at 03:35 Greg Schroeder wrote:

>Luis,
>I am not seeing the csoundft.vim in the tarball.

but it is there:

/var/www/localhost/htdocs/docentes/jure/csound/vim $ tar tzvf csound.vim.tar.gz

-rw-r--r-- lj/eme         4630 2010-06-09 11:41 syntax/csound.vim
-rw-r--r-- lj/eme         9180 2010-06-09 10:02 syntax/csound_opcodes.vim
-rw-r--r-- lj/eme          822 2010-05-21 14:02 macros/csound_macros.vim
-rw-r--r-- lj/eme          286 2010-05-21 14:02 templates/template.csd
-rw-r--r-- lj/eme       224704 2010-06-09 18:30 doc/csound.txt
-rw-r--r-- lj/eme          199 2010-06-13 10:27 ftdetect/csoundft.vim


and the new version has been in the server for some time:

-rw-rw-r-- 1 lj eme 45286 jun 13 10:46 csound.vim.tar.gz

perhaps you're trying with a csound.vim.tar.gz that you downloaded more than a
week ago?


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-06-19 at 11:32 Greg Schroeder wrote:

>I have everything working, 

good!

> except the help functions.

not so good...

> When I run :helpfiles

the command is :helptags followed by the path where you have the cound.txt file
($VIM/vimfiles/doc)

must be run as root!



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-06-19 at 12:27 Greg Schroeder wrote:

>When I run :helptag $VIM/foo/doc (as root) I get the following errors.
>
>E154: Duplicate tag "#end" in file /usr/share/vim/doc/csound.txt

[...]

i see. well, that only reports that some tags are duplicated, which is a
problem, but you should still have your help file working. did you try it?

the help file is created from the opcodes.xml file in the manual, and there are
a few issues with the file and/or my script that result in a few duplicated
tags. i'll have to investigate that...

> Is there a general tutorial for details like how to toggle between
> expand/collapse with the options/orchestra/score/etc elements?

you can of course begin with the vim help :-) there's a brief introduction in
usr_28.txt and a complete manual in fold.txt (see specially 2. Fold commands).

in a nutshell (from the manual):

"All the folding commands start with "z".  With some fantasy, this looks like a
folded piece of paper, seen from the side.  The letter after the "z" has a
mnemonic meaning to make it easier to remember the commands:

	zf	F-old creation
	zo	O-pen a fold
	zc	C-lose a fold "

and there are scores more...


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"