after a long time of relative inactivity, i'm happy to announce a new
major release of csound-vim, a set of tools for editing Csound files with
Vim.

csound-vim provides syntax recognition and highlighting, folding, auto
completion, on-line reference, and templates, plus a set of macros to
compile your orchestra and listen to the results without leaving the
editor. these tools turn Vim, with all its editing power, into a simple
but efficient Csound development environment. 

major changes in this release:

- it's on github! now it's not only easy to install and update, but also
  to contribute code. just visit https://github.com/luisjure/csound;

- it's pathogen-compatible, making it very easy to install and update with
  pathogen or any other plugin manager, like Vundle, NeoBundle, or
  VimPlug;

- now it has a formal license: it's released under the MIT license.

improvements, updates and new features include:

- general clean up and update of the syntax file. lots remain to be done
  there, though;

- the list of opcodes was updated to the latest release;

- NEW FEATURE: auto-completion of opcode names with Ctl-n / Ctl-p

- several minor changes and fixes.

i hope that csounders who also use vim will find it useful.
comments, suggestions, ideas (and patches!) are most welcome.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Luis,

Fantastic!  I've been using an older version of your plugin that I had
put on github at http://github.com/kunstmusik/csound-vim that was
modified to work with Pathogen/Vundle/etc.  I think any changes that
were there are already present in your updated version, so I will
remove that project shortly.  (If anyone was using the one I had on
github, please do uninstall it and use the one from Luis.)

One thing that I had been wanting to investigate for a long time, but
never got around to, was having commands to run Csound interactively
for live coding.  I know Victor added features to the csound
executable for this, but I have not worked with it.  Have you thought
about such a feature too?

Thanks!
steven


On Sun, Jul 17, 2016 at 10:27 PM, luis jure  wrote:
> after a long time of relative inactivity, i'm happy to announce a new
> major release of csound-vim, a set of tools for editing Csound files with
> Vim.
>
> csound-vim provides syntax recognition and highlighting, folding, auto
> completion, on-line reference, and templates, plus a set of macros to
> compile your orchestra and listen to the results without leaving the
> editor. these tools turn Vim, with all its editing power, into a simple
> but efficient Csound development environment.
>
> major changes in this release:
>
> - it's on github! now it's not only easy to install and update, but also
>   to contribute code. just visit https://github.com/luisjure/csound;
>
> - it's pathogen-compatible, making it very easy to install and update with
>   pathogen or any other plugin manager, like Vundle, NeoBundle, or
>   VimPlug;
>
> - now it has a formal license: it's released under the MIT license.
>
> improvements, updates and new features include:
>
> - general clean up and update of the syntax file. lots remain to be done
>   there, though;
>
> - the list of opcodes was updated to the latest release;
>
> - NEW FEATURE: auto-completion of opcode names with Ctl-n / Ctl-p
>
> - several minor changes and fixes.
>
> i hope that csounders who also use vim will find it useful.
> comments, suggestions, ideas (and patches!) are most welcome.
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

thank you, victor. 

live coding is one of 853 (or is it 1279?) "new" features in csound i
still haven't had time to explore. so no, i have no idea yet how i could
integrate that functionality into csound-vim. it would surely be a great
addition, though. where can i learn more about csound live coding?


el 2016-07-17 a las 23:10 Steven Yi escribió:

> Hi Luis,
> 
> Fantastic!  I've been using an older version of your plugin that I had
> put on github at http://github.com/kunstmusik/csound-vim that was
> modified to work with Pathogen/Vundle/etc.  I think any changes that
> were there are already present in your updated version, so I will
> remove that project shortly.  (If anyone was using the one I had on
> github, please do uninstall it and use the one from Luis.)
> 
> One thing that I had been wanting to investigate for a long time, but
> never got around to, was having commands to run Csound interactively
> for live coding.  I know Victor added features to the csound
> executable for this, but I have not worked with it.  Have you thought
> about such a feature too?

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

It's been a few years since I've looked at this, but I managed to do live coding with Csound and Vim using shell scripts and named pipes using this code:

https://github.com/paulbatchelor/icsnd

It worked pretty well for my needs.

Here is me using a more complicated iteration of it here:

https://youtu.be/NjSrh71B2yo

-P

luis jure, Jul 18 2016:

> after a long time of relative inactivity, i'm happy to announce a new
> major release of csound-vim, a set of tools for editing Csound files with
> Vim.
Luis,
I have used csound-vim for a long time and have taken great comfort from it. Thank you for the update. This is brilliant! Thank you for the good work.
...

Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Paul's video shows it, and I did a video a very long time ago with a
basic Java application when were implementing features for live coding
in Csound 6:

https://www.youtube.com/watch?v=xQAesz-ViKk

The online csound notebook (http://csound-notebook.kunstmusik.com)
also has live coding re-evaluation, as does CsoundQT.

I use the notebook for quick projects here and there but the interface
needs work. ;)  Paul's code would probably work but requires starting
the server in a separate script and writing to a named pipe, which
won't work here on Windows.  It'd be nice to have it all within the
csound-vim package if possible where it could manage creating a csound
process and piping data to it.

On Mon, Jul 18, 2016 at 12:10 AM, luis jure  wrote:
> thank you, victor.
>
> live coding is one of 853 (or is it 1279?) "new" features in csound i
> still haven't had time to explore. so no, i have no idea yet how i could
> integrate that functionality into csound-vim. it would surely be a great
> addition, though. where can i learn more about csound live coding?
>
>
> el 2016-07-17 a las 23:10 Steven Yi escribió:
>
>> Hi Luis,
>>
>> Fantastic!  I've been using an older version of your plugin that I had
>> put on github at http://github.com/kunstmusik/csound-vim that was
>> modified to work with Pathogen/Vundle/etc.  I think any changes that
>> were there are already present in your updated version, so I will
>> remove that project shortly.  (If anyone was using the one I had on
>> github, please do uninstall it and use the one from Luis.)
>>
>> One thing that I had been wanting to investigate for a long time, but
>> never got around to, was having commands to run Csound interactively
>> for live coding.  I know Victor added features to the csound
>> executable for this, but I have not worked with it.  Have you thought
>> about such a feature too?
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-19 a las 22:11 Steven Yi escribió:

> I use the notebook for quick projects here and there but the interface
> needs work. ;)  Paul's code would probably work but requires starting
> the server in a separate script and writing to a named pipe, which
> won't work here on Windows.  It'd be nice to have it all within the
> csound-vim package if possible where it could manage creating a csound
> process and piping data to it.

i see... yes, that would definitely be a great addition to csound-vim. but
i'd need 1) a clear idea of how this live-coding thing actually works and
what's needed to make it work all within vim and independently from the
OS, and 2) how to actually implement it in VimL code or whatever.

your video and paul's are both great and very interesting, but the truth
is that i never had a particular interest in live coding myself, so i'm
far from 1). and i'm not an expert in vim or anything like that, so i
wouldn't be very close to 2) either...

unless i could do this in collaboration with other people, this feature
could live in the TODO list for some time...

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

hola

On 07/20/16 12:24, luis jure wrote:
> unless i could do this in collaboration with other people, this feature
> could live in the TODO list for some time...

no worries- thank you for your excellent work with csound vim.

since you have little interest in live coding, it probably doesn't make 
too much sense for you to spend time on it. maybe some of the others who 
want this feature will do the work to implement it.

I think it's alright if it is just listed in a TODO for now.

How it would work in terms of Vim:

1. A function is necessary to start a csound process using --daemon mode.
2. A function for evaluating orchestra code.
3. A function for evaluating score code.

2 and 3 would take a selection and route it to the csound process
created in 1.  I don't remember the exact format, but I think Victor
put in code where if you send over pipes data prepended with 'orc' it
gets evaluated as new orc code, and with 'sco' as score code.

I'd be happy to collaborate on this, but my vimscript knowledge is not
very strong.

On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
> el 2016-07-19 a las 22:11 Steven Yi escribió:
>
>> I use the notebook for quick projects here and there but the interface
>> needs work. ;)  Paul's code would probably work but requires starting
>> the server in a separate script and writing to a named pipe, which
>> won't work here on Windows.  It'd be nice to have it all within the
>> csound-vim package if possible where it could manage creating a csound
>> process and piping data to it.
>
> i see... yes, that would definitely be a great addition to csound-vim. but
> i'd need 1) a clear idea of how this live-coding thing actually works and
> what's needed to make it work all within vim and independently from the
> OS, and 2) how to actually implement it in VimL code or whatever.
>
> your video and paul's are both great and very interesting, but the truth
> is that i never had a particular interest in live coding myself, so i'm
> far from 1). and i'm not an expert in vim or anything like that, so i
> wouldn't be very close to 2) either...
>
> unless i could do this in collaboration with other people, this feature
> could live in the TODO list for some time...
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
> 
> I think it's alright if it is just listed in a TODO for now.
> 
> How it would work in terms of Vim:
> 
> 1. A function is necessary to start a csound process using --daemon mode.
> 2. A function for evaluating orchestra code.
> 3. A function for evaluating score code.
> 
> 2 and 3 would take a selection and route it to the csound process
> created in 1.  I don't remember the exact format, but I think Victor
> put in code where if you send over pipes data prepended with 'orc' it
> gets evaluated as new orc code, and with 'sco' as score code.
> 
> I'd be happy to collaborate on this, but my vimscript knowledge is not
> very strong.
> 
>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>> 
>>> I use the notebook for quick projects here and there but the interface
>>> needs work. ;)  Paul's code would probably work but requires starting
>>> the server in a separate script and writing to a named pipe, which
>>> won't work here on Windows.  It'd be nice to have it all within the
>>> csound-vim package if possible where it could manage creating a csound
>>> process and piping data to it.
>> 
>> i see... yes, that would definitely be a great addition to csound-vim. but
>> i'd need 1) a clear idea of how this live-coding thing actually works and
>> what's needed to make it work all within vim and independently from the
>> OS, and 2) how to actually implement it in VimL code or whatever.
>> 
>> your video and paul's are both great and very interesting, but the truth
>> is that i never had a particular interest in live coding myself, so i'm
>> far from 1). and i'm not an expert in vim or anything like that, so i
>> wouldn't be very close to 2) either...
>> 
>> unless i could do this in collaboration with other people, this feature
>> could live in the TODO list for some time...
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Thanks for correcting me on that. :) Paul's code, from what I
understand, used a named pipe.  Perhaps I misunderstood.

On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
 wrote:
> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>
>> I think it's alright if it is just listed in a TODO for now.
>>
>> How it would work in terms of Vim:
>>
>> 1. A function is necessary to start a csound process using --daemon mode.
>> 2. A function for evaluating orchestra code.
>> 3. A function for evaluating score code.
>>
>> 2 and 3 would take a selection and route it to the csound process
>> created in 1.  I don't remember the exact format, but I think Victor
>> put in code where if you send over pipes data prepended with 'orc' it
>> gets evaluated as new orc code, and with 'sco' as score code.
>>
>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>> very strong.
>>
>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>
>>>> I use the notebook for quick projects here and there but the interface
>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>> the server in a separate script and writing to a named pipe, which
>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>> csound-vim package if possible where it could manage creating a csound
>>>> process and piping data to it.
>>>
>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>> what's needed to make it work all within vim and independently from the
>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>
>>> your video and paul's are both great and very interesting, but the truth
>>> is that i never had a particular interest in live coding myself, so i'm
>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>> wouldn't be very close to 2) either...
>>>
>>> unless i could do this in collaboration with other people, this feature
>>> could live in the TODO list for some time...
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
> 
> Thanks for correcting me on that. :) Paul's code, from what I
> understand, used a named pipe.  Perhaps I misunderstood.
> 
> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>  wrote:
>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>> 
>>> I think it's alright if it is just listed in a TODO for now.
>>> 
>>> How it would work in terms of Vim:
>>> 
>>> 1. A function is necessary to start a csound process using --daemon mode.
>>> 2. A function for evaluating orchestra code.
>>> 3. A function for evaluating score code.
>>> 
>>> 2 and 3 would take a selection and route it to the csound process
>>> created in 1.  I don't remember the exact format, but I think Victor
>>> put in code where if you send over pipes data prepended with 'orc' it
>>> gets evaluated as new orc code, and with 'sco' as score code.
>>> 
>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>> very strong.
>>> 
>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>> 
>>>>> I use the notebook for quick projects here and there but the interface
>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>> the server in a separate script and writing to a named pipe, which
>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>> csound-vim package if possible where it could manage creating a csound
>>>>> process and piping data to it.
>>>> 
>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>> what's needed to make it work all within vim and independently from the
>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>> 
>>>> your video and paul's are both great and very interesting, but the truth
>>>> is that i never had a particular interest in live coding myself, so i'm
>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>> wouldn't be very close to 2) either...
>>>> 
>>>> unless i could do this in collaboration with other people, this feature
>>>> could live in the TODO list for some time...
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
> 
> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>> 
>> Thanks for correcting me on that. :) Paul's code, from what I
>> understand, used a named pipe.  Perhaps I misunderstood.
>> 
>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>  wrote:
>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>> 
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>> 
>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>> 
>>>> I think it's alright if it is just listed in a TODO for now.
>>>> 
>>>> How it would work in terms of Vim:
>>>> 
>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>> 2. A function for evaluating orchestra code.
>>>> 3. A function for evaluating score code.
>>>> 
>>>> 2 and 3 would take a selection and route it to the csound process
>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>> 
>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>> very strong.
>>>> 
>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>> 
>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>> process and piping data to it.
>>>>> 
>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>> what's needed to make it work all within vim and independently from the
>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>> 
>>>>> your video and paul's are both great and very interesting, but the truth
>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>> wouldn't be very close to 2) either...
>>>>> 
>>>>> unless i could do this in collaboration with other people, this feature
>>>>> could live in the TODO list for some time...
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>      https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I see now, I just checked and I did indeed misread the code in Paul's
github.  He's using the named pipe to send to nc, which in turns
broadcasts to UDP to a running Csound.  I think I need a solution that
would work on Windows though.  I'm taking a look at vim-fireplace (a
Clojure Vim plugin) and it uses python to deal with encoding and
sending data.  I'm not quite sure if the starting of a process is
happening within vimscript or not.  Anyways, between the two, maybe
I'll be able to sort out something for Windows here.

On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
 wrote:
> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>
>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>
>>> Thanks for correcting me on that. :) Paul's code, from what I
>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>
>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>  wrote:
>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>
>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>
>>>>> How it would work in terms of Vim:
>>>>>
>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>> 2. A function for evaluating orchestra code.
>>>>> 3. A function for evaluating score code.
>>>>>
>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>
>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>> very strong.
>>>>>
>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>
>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>> process and piping data to it.
>>>>>>
>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>> what's needed to make it work all within vim and independently from the
>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>
>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>> wouldn't be very close to 2) either...
>>>>>>
>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>> could live in the TODO list for some time...
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>      https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

As a sidenote, I was curious to look at vim scripting and, after a bit
of studying, I found that executing python code from vim was quite
simple (at least, I was able to send selected text to Csound via UDP
just now).  Extremely handy and works well here on Windows.  I'll
continue on with this tomorrow and when it's in a state worth testing
I'll create a github repo for this project.

On Sat, Jul 23, 2016 at 3:42 PM, Steven Yi  wrote:
> I see now, I just checked and I did indeed misread the code in Paul's
> github.  He's using the named pipe to send to nc, which in turns
> broadcasts to UDP to a running Csound.  I think I need a solution that
> would work on Windows though.  I'm taking a look at vim-fireplace (a
> Clojure Vim plugin) and it uses python to deal with encoding and
> sending data.  I'm not quite sure if the starting of a process is
> happening within vimscript or not.  Anyways, between the two, maybe
> I'll be able to sort out something for Windows here.
>
> On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
>  wrote:
>> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>>
>>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>>
>>>> Thanks for correcting me on that. :) Paul's code, from what I
>>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>>
>>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>>  wrote:
>>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>>
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>>
>>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>>
>>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>>
>>>>>> How it would work in terms of Vim:
>>>>>>
>>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>>> 2. A function for evaluating orchestra code.
>>>>>> 3. A function for evaluating score code.
>>>>>>
>>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>>
>>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>>> very strong.
>>>>>>
>>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>>
>>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>>> process and piping data to it.
>>>>>>>
>>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>>> what's needed to make it work all within vim and independently from the
>>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>>
>>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>>> wouldn't be very close to 2) either...
>>>>>>>
>>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>>> could live in the TODO list for some time...
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>      https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Can you do the github project under Csound? 

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 24 Jul 2016, at 06:19, Steven Yi  wrote:
> 
> As a sidenote, I was curious to look at vim scripting and, after a bit
> of studying, I found that executing python code from vim was quite
> simple (at least, I was able to send selected text to Csound via UDP
> just now).  Extremely handy and works well here on Windows.  I'll
> continue on with this tomorrow and when it's in a state worth testing
> I'll create a github repo for this project.
> 
>> On Sat, Jul 23, 2016 at 3:42 PM, Steven Yi  wrote:
>> I see now, I just checked and I did indeed misread the code in Paul's
>> github.  He's using the named pipe to send to nc, which in turns
>> broadcasts to UDP to a running Csound.  I think I need a solution that
>> would work on Windows though.  I'm taking a look at vim-fireplace (a
>> Clojure Vim plugin) and it uses python to deal with encoding and
>> sending data.  I'm not quite sure if the starting of a process is
>> happening within vimscript or not.  Anyways, between the two, maybe
>> I'll be able to sort out something for Windows here.
>> 
>> On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
>>  wrote:
>>> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>>> 
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>> 
>>>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>>> 
>>>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>>> 
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>> 
>>>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>>> 
>>>>> Thanks for correcting me on that. :) Paul's code, from what I
>>>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>>> 
>>>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>>>  wrote:
>>>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>>> 
>>>>>> Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>> Maynooth University
>>>>>> Ireland
>>>>>> 
>>>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>>> 
>>>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>>> 
>>>>>>> How it would work in terms of Vim:
>>>>>>> 
>>>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>>>> 2. A function for evaluating orchestra code.
>>>>>>> 3. A function for evaluating score code.
>>>>>>> 
>>>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>>> 
>>>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>>>> very strong.
>>>>>>> 
>>>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>>> 
>>>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>>>> process and piping data to it.
>>>>>>>> 
>>>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>>>> what's needed to make it work all within vim and independently from the
>>>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>>> 
>>>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>>>> wouldn't be very close to 2) either...
>>>>>>>> 
>>>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>>>> could live in the TODO list for some time...
>>>>>>>> 
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> 
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>     https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>> 
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>      https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I setup the project under my own account for now. I figure we can see
how it pans out, and maybe if it's
useful enough, we can merge it into csound-vim, or move it to the
Csound organization repository.

The project is available at:

https://github.com/kunstmusik/csound-repl

The doc folder contains the documentation on how it is designed.  It's
a very small plugin and relies on the user to start Csound with a csd
file in a separate terminal.  Once that is done, you can use
eo to evaluate selected orchestra code within visual mode
(e.g, my leader key is set to ',', so I use ,eo to evaluate the code).

I saw that the server.c code only accepts orchestra code over UDP.
Perhaps we can figure out a protocol for sending SCO code as well?

I have only tested on Windows so far. I think of this as just a start,
so any suggestions or pull-requests appreciated.

Thanks!
steven


On Sun, Jul 24, 2016 at 6:27 AM, Victor Lazzarini
 wrote:
> Can you do the github project under Csound?
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 24 Jul 2016, at 06:19, Steven Yi  wrote:
>>
>> As a sidenote, I was curious to look at vim scripting and, after a bit
>> of studying, I found that executing python code from vim was quite
>> simple (at least, I was able to send selected text to Csound via UDP
>> just now).  Extremely handy and works well here on Windows.  I'll
>> continue on with this tomorrow and when it's in a state worth testing
>> I'll create a github repo for this project.
>>
>>> On Sat, Jul 23, 2016 at 3:42 PM, Steven Yi  wrote:
>>> I see now, I just checked and I did indeed misread the code in Paul's
>>> github.  He's using the named pipe to send to nc, which in turns
>>> broadcasts to UDP to a running Csound.  I think I need a solution that
>>> would work on Windows though.  I'm taking a look at vim-fireplace (a
>>> Clojure Vim plugin) and it uses python to deal with encoding and
>>> sending data.  I'm not quite sure if the starting of a process is
>>> happening within vimscript or not.  Anyways, between the two, maybe
>>> I'll be able to sort out something for Windows here.
>>>
>>> On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
>>>  wrote:
>>>> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>>>>
>>>>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>>>>
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>>
>>>>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>>>>
>>>>>> Thanks for correcting me on that. :) Paul's code, from what I
>>>>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>>>>
>>>>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>>>>  wrote:
>>>>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>>>>
>>>>>>> Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> Maynooth University
>>>>>>> Ireland
>>>>>>>
>>>>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>>>>
>>>>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>>>>
>>>>>>>> How it would work in terms of Vim:
>>>>>>>>
>>>>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>>>>> 2. A function for evaluating orchestra code.
>>>>>>>> 3. A function for evaluating score code.
>>>>>>>>
>>>>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>>>>
>>>>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>>>>> very strong.
>>>>>>>>
>>>>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>>>>
>>>>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>>>>> process and piping data to it.
>>>>>>>>>
>>>>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>>>>> what's needed to make it work all within vim and independently from the
>>>>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>>>>
>>>>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>>>>> wouldn't be very close to 2) either...
>>>>>>>>>
>>>>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>>>>> could live in the TODO list for some time...
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>      https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-22 a las 09:52 s escribió:

> since you have little interest in live coding, it probably doesn't make 
> too much sense for you to spend time on it.

i guess you're right. on the other hand, it would have been a good
opportunity to try to learn a new feature that i wouldn't have cared about
otherwise.

but you can't beat people like steven. he spent like ten minutes browsing
the index of the documentation and he already knows more about vim
scripting than i could ever expect to learn. in less than 24 hours he came
up with a working solution i couldn't have achieved after six months
banging my head against the wall.

so it's time i return to diddle with syntax highlighting and other things
more according to my abilities...

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Don't feel disheartened, that's just Steven being Steven ;)

A couple of remarks

1) you don't need a CSD with --port or --daemon

2) line events can be piped in with -L

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 24 Jul 2016, at 19:49, Steven Yi  wrote:
> 
> I setup the project under my own account for now. I figure we can see
> how it pans out, and maybe if it's
> useful enough, we can merge it into csound-vim, or move it to the
> Csound organization repository.
> 
> The project is available at:
> 
> https://github.com/kunstmusik/csound-repl
> 
> The doc folder contains the documentation on how it is designed.  It's
> a very small plugin and relies on the user to start Csound with a csd
> file in a separate terminal.  Once that is done, you can use
> eo to evaluate selected orchestra code within visual mode
> (e.g, my leader key is set to ',', so I use ,eo to evaluate the code).
> 
> I saw that the server.c code only accepts orchestra code over UDP.
> Perhaps we can figure out a protocol for sending SCO code as well?
> 
> I have only tested on Windows so far. I think of this as just a start,
> so any suggestions or pull-requests appreciated.
> 
> Thanks!
> steven
> 
> 
> On Sun, Jul 24, 2016 at 6:27 AM, Victor Lazzarini
>  wrote:
>> Can you do the github project under Csound?
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 24 Jul 2016, at 06:19, Steven Yi  wrote:
>>> 
>>> As a sidenote, I was curious to look at vim scripting and, after a bit
>>> of studying, I found that executing python code from vim was quite
>>> simple (at least, I was able to send selected text to Csound via UDP
>>> just now).  Extremely handy and works well here on Windows.  I'll
>>> continue on with this tomorrow and when it's in a state worth testing
>>> I'll create a github repo for this project.
>>> 
>>>> On Sat, Jul 23, 2016 at 3:42 PM, Steven Yi  wrote:
>>>> I see now, I just checked and I did indeed misread the code in Paul's
>>>> github.  He's using the named pipe to send to nc, which in turns
>>>> broadcasts to UDP to a running Csound.  I think I need a solution that
>>>> would work on Windows though.  I'm taking a look at vim-fireplace (a
>>>> Clojure Vim plugin) and it uses python to deal with encoding and
>>>> sending data.  I'm not quite sure if the starting of a process is
>>>> happening within vimscript or not.  Anyways, between the two, maybe
>>>> I'll be able to sort out something for Windows here.
>>>> 
>>>> On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
>>>>  wrote:
>>>>> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>>>>> 
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>> 
>>>>>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>>>>> 
>>>>>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>>>>> 
>>>>>> Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>> Maynooth University
>>>>>> Ireland
>>>>>> 
>>>>>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>>>>> 
>>>>>>> Thanks for correcting me on that. :) Paul's code, from what I
>>>>>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>>>>> 
>>>>>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>>>>>  wrote:
>>>>>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>>>>> 
>>>>>>>> Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>> Maynooth University
>>>>>>>> Ireland
>>>>>>>> 
>>>>>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>>>>> 
>>>>>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>>>>> 
>>>>>>>>> How it would work in terms of Vim:
>>>>>>>>> 
>>>>>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>>>>>> 2. A function for evaluating orchestra code.
>>>>>>>>> 3. A function for evaluating score code.
>>>>>>>>> 
>>>>>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>>>>> 
>>>>>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>>>>>> very strong.
>>>>>>>>> 
>>>>>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>>>>> 
>>>>>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>>>>>> process and piping data to it.
>>>>>>>>>> 
>>>>>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>>>>>> what's needed to make it work all within vim and independently from the
>>>>>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>>>>> 
>>>>>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>>>>>> wouldn't be very close to 2) either...
>>>>>>>>>> 
>>>>>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>>>>>> could live in the TODO list for some time...
>>>>>>>>>> 
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>    https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> 
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>    https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> 
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> 
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>     https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>> 
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Oh, I think that vastly overestimates my abilities, and understimates
your own. I had looked at vimscript before but never enough to get
something working.  I studied your code, Paul Batchelor's, other
plugins, and Steve Losh's text [1] to put this small plugin together.
I learned quite a bit and it was nice that things started to make
sense for vim scripting.  (But if you look at the code I wrote
closely, I'm sure you'll find there's some not very elegant things
happening!)

But I'm happy something works now, and it will be fun to get others
involved to try it out and help this all grow.  I have to spend some
time practicing and exploring this and csound-vim, but hopefully I'll
be able to contribute back to csound-vim more now.

Thanks!
steven


[1] - http://learnvimscriptthehardway.stevelosh.com/

On Sun, Jul 24, 2016 at 9:13 PM, luis jure  wrote:
> el 2016-07-22 a las 09:52 s escribió:
>
>> since you have little interest in live coding, it probably doesn't make
>> too much sense for you to spend time on it.
>
> i guess you're right. on the other hand, it would have been a good
> opportunity to try to learn a new feature that i wouldn't have cared about
> otherwise.
>
> but you can't beat people like steven. he spent like ten minutes browsing
> the index of the documentation and he already knows more about vim
> scripting than i could ever expect to learn. in less than 24 hours he came
> up with a working solution i couldn't have achieved after six months
> banging my head against the wall.
>
> so it's time i return to diddle with syntax highlighting and other things
> more according to my abilities...
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Thanks Victor for mentioning that --port and --daemon don't require a
CSD, that's very handy.  I need to figure out the right way to start
and manage a long running process with vim and, once that's figured
out, modify the csound-repl scripts to offer that possibility.

For line events, I think that won't really work for Windows since it's
pipe system is different than *nix. Also, having Csound with pipes
goes against the UDP design in a way.  Interestingly, since Python
works very easily within Vim, I may be able to use ctcsound.py to
create an instance and have more options.  Good thing is that there
are some options with the existing state of things.  One thing I
thought might be nice is that when server mode is used with Csound, it
could be handy to have an option to echo something from Csound to
acknowledge that new code was compiled.  As it is, Csound will only
print anything if there is an error.  On the other hand, it could get
noisy if the user's interaction style ends up with many calls to
Csound.

I'll have to spend more time exploring this and will see if any ideas come up.

Thanks!
steven

On Mon, Jul 25, 2016 at 4:31 AM, Victor Lazzarini
 wrote:
> A couple of remarks
>
> 1) you don't need a CSD with --port or --daemon
>
> 2) line events can be piped in with -L
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 24 Jul 2016, at 19:49, Steven Yi  wrote:
>>
>> I setup the project under my own account for now. I figure we can see
>> how it pans out, and maybe if it's
>> useful enough, we can merge it into csound-vim, or move it to the
>> Csound organization repository.
>>
>> The project is available at:
>>
>> https://github.com/kunstmusik/csound-repl
>>
>> The doc folder contains the documentation on how it is designed.  It's
>> a very small plugin and relies on the user to start Csound with a csd
>> file in a separate terminal.  Once that is done, you can use
>> eo to evaluate selected orchestra code within visual mode
>> (e.g, my leader key is set to ',', so I use ,eo to evaluate the code).
>>
>> I saw that the server.c code only accepts orchestra code over UDP.
>> Perhaps we can figure out a protocol for sending SCO code as well?
>>
>> I have only tested on Windows so far. I think of this as just a start,
>> so any suggestions or pull-requests appreciated.
>>
>> Thanks!
>> steven
>>
>>
>> On Sun, Jul 24, 2016 at 6:27 AM, Victor Lazzarini
>>  wrote:
>>> Can you do the github project under Csound?
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 24 Jul 2016, at 06:19, Steven Yi  wrote:
>>>>
>>>> As a sidenote, I was curious to look at vim scripting and, after a bit
>>>> of studying, I found that executing python code from vim was quite
>>>> simple (at least, I was able to send selected text to Csound via UDP
>>>> just now).  Extremely handy and works well here on Windows.  I'll
>>>> continue on with this tomorrow and when it's in a state worth testing
>>>> I'll create a github repo for this project.
>>>>
>>>>> On Sat, Jul 23, 2016 at 3:42 PM, Steven Yi  wrote:
>>>>> I see now, I just checked and I did indeed misread the code in Paul's
>>>>> github.  He's using the named pipe to send to nc, which in turns
>>>>> broadcasts to UDP to a running Csound.  I think I need a solution that
>>>>> would work on Windows though.  I'm taking a look at vim-fireplace (a
>>>>> Clojure Vim plugin) and it uses python to deal with encoding and
>>>>> sending data.  I'm not quite sure if the starting of a process is
>>>>> happening within vimscript or not.  Anyways, between the two, maybe
>>>>> I'll be able to sort out something for Windows here.
>>>>>
>>>>> On Sat, Jul 23, 2016 at 2:30 PM, Victor Lazzarini
>>>>>  wrote:
>>>>>> besides there is no mechanism for compiling orchestras via pipes. You need UDP for that.
>>>>>>
>>>>>> Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>> Maynooth University
>>>>>> Ireland
>>>>>>
>>>>>>> On 23 Jul 2016, at 20:25, Victor Lazzarini  wrote:
>>>>>>>
>>>>>>> Not as I remember it, because he was asking about the UDP server at the time, but I might be wrong.
>>>>>>>
>>>>>>> Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> Maynooth University
>>>>>>> Ireland
>>>>>>>
>>>>>>>> On 23 Jul 2016, at 19:51, Steven Yi  wrote:
>>>>>>>>
>>>>>>>> Thanks for correcting me on that. :) Paul's code, from what I
>>>>>>>> understand, used a named pipe.  Perhaps I misunderstood.
>>>>>>>>
>>>>>>>> On Sat, Jul 23, 2016 at 1:45 PM, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>>> you can send orchestras via udp sockets. Paul Batchelor  wrote code for vim to use it,if I am not mistaken.
>>>>>>>>>
>>>>>>>>> Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>>> Maynooth University
>>>>>>>>> Ireland
>>>>>>>>>
>>>>>>>>>> On 23 Jul 2016, at 19:16, Steven Yi  wrote:
>>>>>>>>>>
>>>>>>>>>> I think it's alright if it is just listed in a TODO for now.
>>>>>>>>>>
>>>>>>>>>> How it would work in terms of Vim:
>>>>>>>>>>
>>>>>>>>>> 1. A function is necessary to start a csound process using --daemon mode.
>>>>>>>>>> 2. A function for evaluating orchestra code.
>>>>>>>>>> 3. A function for evaluating score code.
>>>>>>>>>>
>>>>>>>>>> 2 and 3 would take a selection and route it to the csound process
>>>>>>>>>> created in 1.  I don't remember the exact format, but I think Victor
>>>>>>>>>> put in code where if you send over pipes data prepended with 'orc' it
>>>>>>>>>> gets evaluated as new orc code, and with 'sco' as score code.
>>>>>>>>>>
>>>>>>>>>> I'd be happy to collaborate on this, but my vimscript knowledge is not
>>>>>>>>>> very strong.
>>>>>>>>>>
>>>>>>>>>>>> On Wed, Jul 20, 2016 at 12:24 PM, luis jure  wrote:
>>>>>>>>>>>> el 2016-07-19 a las 22:11 Steven Yi escribió:
>>>>>>>>>>>>
>>>>>>>>>>>> I use the notebook for quick projects here and there but the interface
>>>>>>>>>>>> needs work. ;)  Paul's code would probably work but requires starting
>>>>>>>>>>>> the server in a separate script and writing to a named pipe, which
>>>>>>>>>>>> won't work here on Windows.  It'd be nice to have it all within the
>>>>>>>>>>>> csound-vim package if possible where it could manage creating a csound
>>>>>>>>>>>> process and piping data to it.
>>>>>>>>>>>
>>>>>>>>>>> i see... yes, that would definitely be a great addition to csound-vim. but
>>>>>>>>>>> i'd need 1) a clear idea of how this live-coding thing actually works and
>>>>>>>>>>> what's needed to make it work all within vim and independently from the
>>>>>>>>>>> OS, and 2) how to actually implement it in VimL code or whatever.
>>>>>>>>>>>
>>>>>>>>>>> your video and paul's are both great and very interesting, but the truth
>>>>>>>>>>> is that i never had a particular interest in live coding myself, so i'm
>>>>>>>>>>> far from 1). and i'm not an expert in vim or anything like that, so i
>>>>>>>>>>> wouldn't be very close to 2) either...
>>>>>>>>>>>
>>>>>>>>>>> unless i could do this in collaboration with other people, this feature
>>>>>>>>>>> could live in the TODO list for some time...
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>    https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>    https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>     https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>      https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>       https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-18 a las 19:39 Ffanci Silvain escribió:

> I have used csound-vim for a long time and have taken great comfort from
> it. Thank you for the update.

thank you, ffanci, i'm very glad to know that csound-vim has been useful to
you. i hope i can keep improving it in the future.

and for any csound-vimers using this feature, you might be interested to
know that i just updated the on-line vim help to the latest version of the
csound manual.


best,

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I'm thrilled too! I use csound-vim every day and the improvements you've
made to it are really exciting to me. Thanks for the heads-up about the
integrated help—I've never thought to look at the CSound documentation
from inside of vim before and I imagine it'll save time.

Best,
Zoë

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-27 a las 20:26 Zoë Sparks escribió:

> I'm thrilled too! I use csound-vim every day and the improvements you've
> made to it are really exciting to me. Thanks for the heads-up about the
> integrated help—I've never thought to look at the CSound documentation
> from inside of vim before and I imagine it'll save time.

hey, zoë, thanks for the positive feedback!

the help file is an abridged version of the manual with only the
description and the syntax section for each opcode. it's meant as a
reminder, and it doesn't include the detailed description of the arguments
or the examples. you'll have to check the actual manual for that.

i think that's a reasonable decision, but i wouldn't know, i don't use
this feature much. i maintain it because i know some people use it. so i'm
open to suggestions of a different format.

best,

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Luis,

Very nice update!  One thing I was thinking was that it might be nice
to also have a function and shortcut to open the manual entry for an
opcode in a browser.  The way it works in Blue (and perhaps other
programs?) is when the caret is within a word, you hit a shortcut key
and it creates a URL using:

[manualBase] + "/" + [opcodeName] + ".html"

This works as all of the opcodes in the Csound manual have entries
that get generated just as opcodeName.html.

I don't know if there's a built-in way to do this in Vim, but the
commands I use when working on a command line on various platforms
are:

Mac OSX:  open URL
Windows:   start URL
Linux:         xdg-open URL

The manualBase could default to:

http://csound.github.io/docs/manual

and the user could maybe set it so that they could use a local version, such as:

file://path/to/local/csound/manual

I found the other day I was looking at the Vim help (the latest
version from the update) and even though I was reading the opcode
documentation, I didn't have a good idea of what some of the
parameters meant and had to go to the manual online.  A shortcut at
the moment would have been nice. ;)

Thoughts?

steven

On Thu, Jul 28, 2016 at 7:18 PM, luis jure  wrote:
> el 2016-07-27 a las 20:26 Zoë Sparks escribió:
>
>> I'm thrilled too! I use csound-vim every day and the improvements you've
>> made to it are really exciting to me. Thanks for the heads-up about the
>> integrated help—I've never thought to look at the CSound documentation
>> from inside of vim before and I imagine it'll save time.
>
> hey, zoë, thanks for the positive feedback!
>
> the help file is an abridged version of the manual with only the
> description and the syntax section for each opcode. it's meant as a
> reminder, and it doesn't include the detailed description of the arguments
> or the examples. you'll have to check the actual manual for that.
>
> i think that's a reasonable decision, but i wouldn't know, i don't use
> this feature much. i maintain it because i know some people use it. so i'm
> open to suggestions of a different format.
>
> best,
>
> lj
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-28 a las 20:57 Steven Yi escribió:

> One thing I was thinking was that it might be nice to also have a
> function and shortcut to open the manual entry for an opcode in a
> browser.

hmmm... i hadn't thought of that, but it would be a nifty little addition
to csound-vim, wouldn't it?

i'm sure it has to be possible to do that in vim, although i wouldn't know
how right now. i'll look into it.

> I found the other day I was looking at the Vim help (the latest
> version from the update) and even though I was reading the opcode
> documentation, I didn't have a good idea of what some of the
> parameters meant and had to go to the manual online.  A shortcut at
> the moment would have been nice. ;)

well, there's also the possibility *not* to strip down the sections where
all the parameters are described. i conceived the help file as a quick
reference, but it could be more complete. would you prefer that? it's just
a matter of modifying the scripts a little bit.

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

> > One thing I was thinking was that it might be nice to also have a
> > function and shortcut to open the manual entry for an opcode in a
> > browser.
> 
> hmmm... i hadn't thought of that, but it would be a nifty little addition
> to csound-vim, wouldn't it?
> 
> i'm sure it has to be possible to do that in vim, although i wouldn't know
> how right now. i'll look into it.

I wouldn't mind this either. I have found myself frequently going to the
online manual when I need more information, so it would probably be
convenient for me.

I can think of a kind of hacky way to do it using `call system(xdg-open
)` (or whatever the application launcher is on the current system)
and getting the appropriate URL by matching to the line numbers of the
respective entries in the manual. There's probably a more elegant way, I
imagine—my knowledge of Vimscript isn't the deepest. But I'd be up for
coding this and submitting a pull request if you'd like.

> > I found the other day I was looking at the Vim help (the latest
> > version from the update) and even though I was reading the opcode
> > documentation, I didn't have a good idea of what some of the
> > parameters meant and had to go to the manual online.  A shortcut at
> > the moment would have been nice. ;)
> 
> well, there's also the possibility *not* to strip down the sections where
> all the parameters are described. i conceived the help file as a quick
> reference, but it could be more complete. would you prefer that? it's just
> a matter of modifying the scripts a little bit.

I think it would be nice if the documentation included the descriptions
of the parameters—sometimes it's hard for me to figure out what all of
them mean without more information. 

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-29 a las 19:06 Zoë Sparks escribió:

> I think it would be nice if the documentation included the descriptions
> of the parameters

done. haven't had time to check the results in depth, please update and
use it a little bit. it seems to be fine, but please report back if you
discover some bad formatting.

i'll investigate later on how to link to the html manual.

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

> > I think it would be nice if the documentation included the descriptions
> > of the parameters
> 
> done. haven't had time to check the results in depth, please update and
> use it a little bit. it seems to be fine, but please report back if you
> discover some bad formatting.

Oh awesome, thanks for all your work! I'll check it out.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Luis,

Thanks for the update, the information that is now there is very
handy!  I imagine I won't need to go to the HTML manual much now as a
result.

Also, I have posted a news story for yours and my plugins:

http://csound.github.io/site/news/2016/07/17/csound-vim

Thanks!
steven


On Fri, Jul 29, 2016 at 8:02 PM, luis jure  wrote:
> el 2016-07-29 a las 19:06 Zoë Sparks escribió:
>
>> I think it would be nice if the documentation included the descriptions
>> of the parameters
>
> done. haven't had time to check the results in depth, please update and
> use it a little bit. it seems to be fine, but please report back if you
> discover some bad formatting.
>
> i'll investigate later on how to link to the html manual.
>
> lj
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-30 a las 13:47 Steven Yi escribió:

> Thanks for the update, the information that is now there is very
> handy!  I imagine I won't need to go to the HTML manual much now as a
> result.

great! anyway, a shortcut to the manual page is still in my todo list. i
have a general idea of how this could be done, but i still have a way to
go to have a working solution. i don't think i'll have much to work on
this on the next few days, though.

> Also, I have posted a news story for yours and my plugins:

looks great, thanks!

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-07-30 a las 18:17 Justin Smith escribió:

> couldn't we also use the manual path to look up examples and open them in
> vim based on opcode name? (if the example exists that is)

that's a great idea, and the same solution for the manual page could be
adapted to open the example csd. i think this would be easier, actually.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

> > couldn't we also use the manual path to look up examples and open them in
> > vim based on opcode name? (if the example exists that is)
> 
> that's a great idea, and the same solution for the manual page could be
> adapted to open the example csd. i think this would be easier, actually.

I'd love this! If I could open and play the example csd all from within
vim I'd be thrilled.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

it's winter in montevideo and we've been having cold and rainy days. and
hacking this is more fun than all the pending affairs that keep piling up
on my desk. so i decided to give it a try.

i just updated the git repository with a preliminary (and undocumented)
new version of csound-vim, with functions to open the manual page and the
example csd of the opcode under the cursor.

=== provisionally mapped to F1:

opens the html manual page of the opcode under the cursor. the global
variable g:csound_manual can be defined in .vimrc pointing to the local
directory with the html manual, like this (linux):

let g:csound_manual = "/home/me/csound_stuff/html/"

or whatever for windows and mac (note the trailing slash).

if this variable is not defined, the web version at
http://csound.github.io/docs/manual/ will be opened.

it works on linux and i think also on windows. it would be a miracle if it
worked on osx (i'm not even sure if the function to detect the os works).

=== provisionally mapped to F2: 

opens the example csd (if it exists) on a separate tab. this function only
works with a local copy of the html manual, because a) i don't know a way
to check in advance if a remote csd exists, and b) if i try to open a
remote file that doesn't exist, vim seems to freeze. anyway, i don't think
that it makes much sense to try to open a csd on the web. but if anyone
knows how to overcome these problems, i could eliminate this limitation.

WARNING: this is an "experimental" alpha version strictly for the
adventurous, careless use of these functions could make your computer
explode. but it would be great if you could try it (specially those of you
on mac osx) and let me know if it works, and eventually help me solve the
os-specific problems that might appear.

best,

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Luis,

I tried the update here and F2 doesn't really do much as expected
using the default manual base, which is fine.  For F1 though, I had
issues as I use Vim under msys2 shell.  With this version of vim, it
assumes the system is unix, not windows.  I made a modification to the
plugin/csound.vim file to add these lines:

$ git diff
diff --git a/plugin/csound.vim b/plugin/csound.vim
index fa10de4..7e9075a 100644
--- a/plugin/csound.vim
+++ b/plugin/csound.vim
@@ -19,6 +19,8 @@ if !exists("g:os")
       let g:os = "OSX"
     elseif system('uname')=~'Linux'
       let g:os = "Linux"
+    elseif system('uname')=~'MINGW'
+      let g:os = "Mingw"
     endif
   endif
 endif
@@ -36,6 +38,8 @@ function! OpenManual()
     execute "!open" manual_page
   elseif g:os == "Windows"
     execute "!start cmd /c start" manual_page
+  elseif g:os == "Mingw"
+    execute "!start" manual_page
   else
     echo "sorry, cannot detect your OS"
     echo "try setting the variable g:os in your .vimrc"

The + lines show the additional code.  Would you be willing to
integrate this into your plugin?  (Also, how do you prefer
contributions: email, patch file, pull request?)

Thanks!
steven

On Mon, Aug 1, 2016 at 10:52 PM, luis jure  wrote:
> it's winter in montevideo and we've been having cold and rainy days. and
> hacking this is more fun than all the pending affairs that keep piling up
> on my desk. so i decided to give it a try.
>
> i just updated the git repository with a preliminary (and undocumented)
> new version of csound-vim, with functions to open the manual page and the
> example csd of the opcode under the cursor.
>
> === provisionally mapped to F1:
>
> opens the html manual page of the opcode under the cursor. the global
> variable g:csound_manual can be defined in .vimrc pointing to the local
> directory with the html manual, like this (linux):
>
> let g:csound_manual = "/home/me/csound_stuff/html/"
>
> or whatever for windows and mac (note the trailing slash).
>
> if this variable is not defined, the web version at
> http://csound.github.io/docs/manual/ will be opened.
>
> it works on linux and i think also on windows. it would be a miracle if it
> worked on osx (i'm not even sure if the function to detect the os works).
>
> === provisionally mapped to F2:
>
> opens the example csd (if it exists) on a separate tab. this function only
> works with a local copy of the html manual, because a) i don't know a way
> to check in advance if a remote csd exists, and b) if i try to open a
> remote file that doesn't exist, vim seems to freeze. anyway, i don't think
> that it makes much sense to try to open a csd on the web. but if anyone
> knows how to overcome these problems, i could eliminate this limitation.
>
> WARNING: this is an "experimental" alpha version strictly for the
> adventurous, careless use of these functions could make your computer
> explode. but it would be great if you could try it (specially those of you
> on mac osx) and let me know if it works, and eventually help me solve the
> os-specific problems that might appear.
>
> best,
>
> lj
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

hi, steven! thanks for the bug report and the patch. i knew there had to
be more cases i hadn't foreseen.


el 2016-08-02 a las 15:19 Steven Yi escribió:

> I tried the update here and F2 doesn't really do much as expected
> using the default manual base, which is fine.

yes, that's the intended behavior, let me know how it goes as soon as you
follow the instructions in the message... :-)


> The + lines show the additional code.  Would you be willing to
> integrate this into your plugin?

done.

> (Also, how do you prefer contributions: email, patch file, pull
> request?)

mmm... i guess both patches and pull requests are fine. perhaps i'd prefer
a patch, but it's more or less the same, really. and for small patches
like this one, an email is also fine.

thanks again for the report and the patch, it'd be great if we had some
reports from mac users.

best,

lj

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

el 2016-08-02 a las 19:52 luis jure escribió:

> yes, that's the intended behavior, let me know how it goes as soon as you
> follow the instructions in the message... :-)

ugh, no, that was *not* the intended behavior. there was a stupid bug (are
there clever ones?) in the way the path was detected and set. please
update.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here