Yes! I'll definitely try it, I don't see why it wouldn't work. It will
also make it easier for people to identify the version they need.

We're in the process of preparing the beta release for 0.6.0, but I'll
try to make the final release of 0.6.0 a universal binary.

Cheers,
Andrés

On Tue, Jun 8, 2010 at 9:47 PM,   wrote:
> Now that it looks like we have a working Universal ppc-i386, it would be
> good to have a universal frontend as well. Any chances of a universal
> qutecsound?
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>



-- 


Andrés


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

Good. Also could you consider providing a doubles version of  
qutecsound? I think we might be moving to a doubles-only future.

Victor
On 9 Jun 2010, at 08:32, Andres Cabrera wrote:

> Yes! I'll definitely try it, I don't see why it wouldn't work. It will
> also make it easier for people to identify the version they need.
>
> We're in the process of preparing the beta release for 0.6.0, but I'll
> try to make the final release of 0.6.0 a universal binary.
>
> Cheers,
> Andrés
>
> On Tue, Jun 8, 2010 at 9:47 PM,   wrote:
>> Now that it looks like we have a working Universal ppc-i386, it  
>> would be
>> good to have a universal frontend as well. Any chances of a universal
>> qutecsound?
>>
>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>> National University of Ireland, Maynooth
>>
>
>
>
> -- 
>
>
> Andrés
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

on 2010-06-09 at 15:38 Dima Bak wrote:

> And I have a kind request for Csound developers : Can you remove this
> piece of shit from standart installation? 

wow, that's a "kind request" if i ever saw one... :-)


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

I don't know what Stefano would think about this, but I  think in  
addition to qutecsound (which I love) the installer could also include  
WinXound (also a great editor)?

Best,

Peiman

On 9 Jun 2010, at 11:44, Victor Lazzarini wrote:

> Good. Also could you consider providing a doubles version of  
> qutecsound? I think we might be moving to a doubles-only future.
>
> Victor
> On 9 Jun 2010, at 08:32, Andres Cabrera wrote:
>
>> Yes! I'll definitely try it, I don't see why it wouldn't work. It  
>> will
>> also make it easier for people to identify the version they need.
>>
>> We're in the process of preparing the beta release for 0.6.0, but  
>> I'll
>> try to make the final release of 0.6.0 a universal binary.
>>
>> Cheers,
>> Andrés
>>
>> On Tue, Jun 8, 2010 at 9:47 PM,   wrote:
>>> Now that it looks like we have a working Universal ppc-i386, it  
>>> would be
>>> good to have a universal frontend as well. Any chances of a  
>>> universal
>>> qutecsound?
>>>
>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>> National University of Ireland, Maynooth
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

How about an inbuilt manners test inside the installer?

On 9 Jun 2010, at 13:56, luis jure wrote:

>
> on 2010-06-09 at 15:38 Dima Bak wrote:
>
>> And I have a kind request for Csound developers : Can you remove this
>> piece of shit from standart installation?
>
> wow, that's a "kind request" if i ever saw one... :-)
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

This message should be ignored. Besides the disgusting language, the  
writer has no idea what she is talking about.
-Lou


On Jun 9, 2010, at 8:38 AM, Dima Bak wrote:

> Qutecsound is piece of shit. I even don't understand goal of  
> creation such a cuts freak like qutecsound. It's one of most fuckin  
> editor's, that I even see. And I have a kind request for Csound  
> developers : Can you remove this piece of shit from standart  
> installation? I use csoundx mode for emacs and it's very good and  
> usefull tool, and you even can use all the power of emacs in  
> editing, rother than use dunce editor, like qute csound.
>
> 2010/6/9 Victor Lazzarini 
> Good. Also could you consider providing a doubles version of  
> qutecsound? I think we might be moving to a doubles-only future.
>
> Victor
>
> On 9 Jun 2010, at 08:32, Andres Cabrera wrote:
>
> Yes! I'll definitely try it, I don't see why it wouldn't work. It will
> also make it easier for people to identify the version they need.
>
> We're in the process of preparing the beta release for 0.6.0, but I'll
> try to make the final release of 0.6.0 a universal binary.
>
> Cheers,
> Andrés
>
> On Tue, Jun 8, 2010 at 9:47 PM,   wrote:
> Now that it looks like we have a working Universal ppc-i386, it  
> would be
> good to have a universal frontend as well. Any chances of a universal
> qutecsound?
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>
>
>
>
> -- 
>
>
> Andrés
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>
>



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

Anyone tried to use CSound 5 with Emacs (Carbon or Aqua) in Mac OSX?


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

On 9 June 2010 10:27, Bernardo Barros  wrote:
> Anyone tried to use CSound 5 with Emacs (Carbon or Aqua) in Mac OSX?
>

That's the csound emacs mode, right? Is there another?
http://www.zogotounga.net/comp/csoundx.html

cheers,
Bernardo


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

on 2010-06-09 at 14:00 Peiman Khosravi wrote:

>I don't know what Stefano would think about this, but I  think in  
>addition to qutecsound (which I love) the installer could also include  
>WinXound (also a great editor)?

well, leaving aside the previous "kind request" (which one could find either
amusing or disgusting, depending on the mood of the moment), i must say that i
think that bloating the csound installer with editors and front-ends is a Very
Bad Idea. i agree that winxound is a great editor and i recommend it to my
students, since virtually all of them use windows. but i don't use it and i
wouldn't be able to use it even if i wanted to, since it doesn't run on linux,
as far as i know. qutecsound is cross-platform, but i don't use it because it
doesn't suit my way of working. why do i have to download it and install it
with every csound release?

two reasons why i think that the csound installer should NOT include any
external editor are:

1. they are not part of csound, you may use them or not depending on how you
organize your work flow. forcing csound users to download and install
additional software seems to me arbitrary, we might as well include emacs, vim
and audacity;

2. they are they are different applications by different developers with
completely different and independent release moments. suppose i use winxsound
and qutecsound so i download them and install them. then for every new
release of csound i have to download and install them again and again and again.
and then there's a new release of winxsound/qutecsound, do i have to wait to
the next release of csound to have it? or i just download it as soon as it is
available? in that case, do i have to download it yet again with the following
csound release? i just can't get myself to find this idea very clever...

honestly, i don't see the point bloating the installer with software that is
freely and easily available elsewhere.

but those are just my two (very devalued) uruguayan pesos...



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

I understand your view, but at least on os x qutecsound is not  
installed by default. You have to manually drag it into the  
applications folder from the csound disk image.

Also for a beginner, it would be nice to have a package that is ready  
to be used out of the box. It's very off-putting to install csound and  
realise that nothing has (seemingly) been installed.

On 9 Jun 2010, at 15:02, luis jure wrote:

>
> on 2010-06-09 at 14:00 Peiman Khosravi wrote:
>
>> I don't know what Stefano would think about this, but I  think in
>> addition to qutecsound (which I love) the installer could also  
>> include
>> WinXound (also a great editor)?
>
> well, leaving aside the previous "kind request" (which one could  
> find either
> amusing or disgusting, depending on the mood of the moment), i must  
> say that i
> think that bloating the csound installer with editors and front-ends  
> is a Very
> Bad Idea. i agree that winxound is a great editor and i recommend it  
> to my
> students, since virtually all of them use windows. but i don't use  
> it and i
> wouldn't be able to use it even if i wanted to, since it doesn't run  
> on linux,
> as far as i know. qutecsound is cross-platform, but i don't use it  
> because it
> doesn't suit my way of working. why do i have to download it and  
> install it
> with every csound release?
>
> two reasons why i think that the csound installer should NOT include  
> any
> external editor are:
>
> 1. they are not part of csound, you may use them or not depending on  
> how you
> organize your work flow. forcing csound users to download and install
> additional software seems to me arbitrary, we might as well include  
> emacs, vim
> and audacity;
>
> 2. they are they are different applications by different developers  
> with
> completely different and independent release moments. suppose i use  
> winxsound
> and qutecsound so i download them and install them. then for every new
> release of csound i have to download and install them again and  
> again and again.
> and then there's a new release of winxsound/qutecsound, do i have to  
> wait to
> the next release of csound to have it? or i just download it as soon  
> as it is
> available? in that case, do i have to download it yet again with the  
> following
> csound release? i just can't get myself to find this idea very  
> clever...
>
> honestly, i don't see the point bloating the installer with software  
> that is
> freely and easily available elsewhere.
>
> but those are just my two (very devalued) uruguayan pesos...
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

Here's my view as someone who does not build or modify csound, and who  
is not very comfortable working at the command line level.

A csound front end is indispensable to me. I have an elaborate control  
surface, built with MacCsound, which I use for performing live, and I  
also use csound extensively for composition, without using my control  
surface. In either mode I rely heavily on MacCsound, and I hope soon  
to rely exclusively on QuteCsound.

For me MacCsound IS csound. In the future, I hope that QuteCsound will  
be the same. (One of the main advantages I look forward to, which  
MacCsound did not provide, is platform independence.)

All I want to do when I visit Sourceforge is to click one button to  
download the latest reliable version of csound. Then after the  
download, I want to click one icon to install. Then I want to open the  
front end (ultimately QuteCsound) and work on music.

I certainly hope that csound and its front end(s) will all be bundled  
together.

-Lou Cohen




On Jun 9, 2010, at 10:02 AM, luis jure wrote:

>
> on 2010-06-09 at 14:00 Peiman Khosravi wrote:
>
>> I don't know what Stefano would think about this, but I  think in
>> addition to qutecsound (which I love) the installer could also  
>> include
>> WinXound (also a great editor)?
>
> well, leaving aside the previous "kind request" (which one could  
> find either
> amusing or disgusting, depending on the mood of the moment), i must  
> say that i
> think that bloating the csound installer with editors and front-ends  
> is a Very
> Bad Idea. i agree that winxound is a great editor and i recommend it  
> to my
> students, since virtually all of them use windows. but i don't use  
> it and i
> wouldn't be able to use it even if i wanted to, since it doesn't run  
> on linux,
> as far as i know. qutecsound is cross-platform, but i don't use it  
> because it
> doesn't suit my way of working. why do i have to download it and  
> install it
> with every csound release?
>
> two reasons why i think that the csound installer should NOT include  
> any
> external editor are:
>
> 1. they are not part of csound, you may use them or not depending on  
> how you
> organize your work flow. forcing csound users to download and install
> additional software seems to me arbitrary, we might as well include  
> emacs, vim
> and audacity;
>
> 2. they are they are different applications by different developers  
> with
> completely different and independent release moments. suppose i use  
> winxsound
> and qutecsound so i download them and install them. then for every new
> release of csound i have to download and install them again and  
> again and again.
> and then there's a new release of winxsound/qutecsound, do i have to  
> wait to
> the next release of csound to have it? or i just download it as soon  
> as it is
> available? in that case, do i have to download it yet again with the  
> following
> csound release? i just can't get myself to find this idea very  
> clever...
>
> honestly, i don't see the point bloating the installer with software  
> that is
> freely and easily available elsewhere.
>
> but those are just my two (very devalued) uruguayan pesos...
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

Thanks Peiman for your suggestion about to include also WinXound in the 
cSound package ...
but I think that it's better to leave WinXound as a separate download (at 
least at the moment),
So, I agree with Luis and his "uruguayan pesos" ...
maybe in the future the package maintainers could think about a "complete
package" with all editors included and an other "base package" without them 
...

About a WinXound version for Linux, I'm already working on it (at the moment 
on
Ubuntu 10.04 with GTK and Scintilla GTK) ... and I hope to release an 
official beta
for the next coming September.

Stefano






--------------------------------------------------
From: "luis jure" 
Sent: Wednesday, June 09, 2010 4:02 PM
To: "csound list" 
Subject: [Csnd] Re: Re: Re: Re: Universal qutecsound ?

>
> on 2010-06-09 at 14:00 Peiman Khosravi wrote:
>
>>I don't know what Stefano would think about this, but I  think in
>>addition to qutecsound (which I love) the installer could also include
>>WinXound (also a great editor)?
>
> well, leaving aside the previous "kind request" (which one could find 
> either
> amusing or disgusting, depending on the mood of the moment), i must say 
> that i
> think that bloating the csound installer with editors and front-ends is a 
> Very
> Bad Idea. i agree that winxound is a great editor and i recommend it to my
> students, since virtually all of them use windows. but i don't use it and 
> i
> wouldn't be able to use it even if i wanted to, since it doesn't run on 
> linux,
> as far as i know. qutecsound is cross-platform, but i don't use it because 
> it
> doesn't suit my way of working. why do i have to download it and install 
> it
> with every csound release?
>
> two reasons why i think that the csound installer should NOT include any
> external editor are:
>
> 1. they are not part of csound, you may use them or not depending on how 
> you
> organize your work flow. forcing csound users to download and install
> additional software seems to me arbitrary, we might as well include emacs, 
> vim
> and audacity;
>
> 2. they are they are different applications by different developers with
> completely different and independent release moments. suppose i use 
> winxsound
> and qutecsound so i download them and install them. then for every new
> release of csound i have to download and install them again and again and 
> again.
> and then there's a new release of winxsound/qutecsound, do i have to wait 
> to
> the next release of csound to have it? or i just download it as soon as it 
> is
> available? in that case, do i have to download it yet again with the 
> following
> csound release? i just can't get myself to find this idea very clever...
>
> honestly, i don't see the point bloating the installer with software that 
> is
> freely and easily available elsewhere.
>
> but those are just my two (very devalued) uruguayan pesos...
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"
>
>
>
> ---
> avast! Antivirus: In arrivo messaggio pulito.
> Virus Database (VPS): 100609-0, 09/06/2010
> Controllato il: 09/06/2010 17:17:05
> avast! - copyright (c) 1988-2010 ALWIL Software.
> http://www.avast.com
>
>
> 


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

On 9 Jun 2010, at 16:35, Stefano Bonetti wrote:

> About a WinXound version for Linux, I'm already working on it (at  
> the moment on
> Ubuntu 10.04 with GTK and Scintilla GTK) ... and I hope to release  
> an official beta
> for the next coming September.

Great, that will make my transition to Ubuntu much easier :-)

P


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

I didn't read this other agressive e-mail. I really just kindly wanted
to know about the (aqua/carbon)emacs/csound5/osx setup.


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

>> Anyone tried to use CSound 5 with Emacs (Carbon or Aqua) in Mac OSX?

Should work... I'd be interested in the feedback though.
>
> That's the csound emacs mode, right? Is there another?
> http://www.zogotounga.net/comp/csoundx.html

Yes, that's the one. It's my baby :)

There are also the modes by John, which are the historical base for 
csound-x, at http://www.cs.bath.ac.uk/pub/dream/utilities/Emacs-macros/
Some people complain csound-x is overkill, so you may be interested in 
those.


Stef




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

I agree with Lou on this. I feel it's important to provide as simple an
installation procedure as possible, for the benefit of new users. Not
everyone is comfortable configuring their system by choosing the components
they would prefer. In this day and age, hard drive space is cheap enough
that if you don't want to use the supplied front end, you can just ignore it
or drag it to the trash.

I happen to think QuteCsound is a great choice as the default editor: It's
cross-platform, it has many useful features, and it's quite transparent. By
"transparent," I mean that you can just write traditional .csd files with it
-- you never need to use the graphic widgets. blue is also a terrific
editor, but it's not transparent; there's a blue learning curve that can't
be sidestepped.

--JA


Louis Cohen wrote:
> 
> Here's my view as someone who does not build or modify csound, and who  
> is not very comfortable working at the command line level.
> 
> A csound front end is indispensable to me. I have an elaborate control  
> surface, built with MacCsound, which I use for performing live, and I  
> also use csound extensively for composition, without using my control  
> surface. In either mode I rely heavily on MacCsound, and I hope soon  
> to rely exclusively on QuteCsound.
> 
> For me MacCsound IS csound. In the future, I hope that QuteCsound will  
> be the same. (One of the main advantages I look forward to, which  
> MacCsound did not provide, is platform independence.)
> 
> All I want to do when I visit Sourceforge is to click one button to  
> download the latest reliable version of csound. Then after the  
> download, I want to click one icon to install. Then I want to open the  
> front end (ultimately QuteCsound) and work on music.
> 
> I certainly hope that csound and its front end(s) will all be bundled  
> together.
> 
> -Lou Cohen
> 

I agree with both Louis and Luis on this matter.

Maybe there could be
1) front ends with compatible versions of Csound included that could
be simple 'one-click' (or few clicks) downloads, which would be
reliable but not necessarily on the cutting edge of Csound
development.
2) components listed completely separately for those who want to stay
on the cutting edge. (I guess this would be more or less what it is
now)
I think this is basically also what Stefano was saying in his email.
I guess this would mean a lot more maintenance on the part of the
developers to keep the all in one type packages from getting too far
out of date, though.





2010/6/9 Stéphane Rollandin :
>>> Anyone tried to use CSound 5 with Emacs (Carbon or Aqua) in Mac OSX?
>
> Should work... I'd be interested in the feedback though.
>>
>> That's the csound emacs mode, right? Is there another?
>> http://www.zogotounga.net/comp/csoundx.html
>
> Yes, that's the one. It's my baby :)
>
> There are also the modes by John, which are the historical base for
> csound-x, at http://www.cs.bath.ac.uk/pub/dream/utilities/Emacs-macros/
> Some people complain csound-x is overkill, so you may be interested in
> those.
>
>
> Stef
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


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

> Maybe there could be
> 1) front ends with compatible versions of Csound included that could
> be simple 'one-click' (or few clicks) downloads, which would be
> reliable but not necessarily on the cutting edge of Csound
> development.
> 2) components listed completely separately for those who want to stay
> on the cutting edge. (I guess this would be more or less what it is
> now)

This is exactly what I do with my own front-end: I provide both separate 
components and an all-in-one package including my own software plus all 
what is needed to run it, including the latest release of csound.

(more at http://www.zogotounga.net/surmulot/surmulot.html)

Stef





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

Looks like a really good work, Stéphane. I'll take a look in yout system!
(But now I don't have the time...)
I love Emacs to work with SuperCollider and Lilypond.
I was wondering about CSound. When I did use CSound I didn't have all
this nice things.
But I was using Windows and I didn't know about your work. (That was
like 5 years ago).

The idea of a 'compositional envolriment' is really nice. And Emacs
helps me clustering SC and Lilypond, (but also python, gnuplot, latex
and lilypond-book (actually a branch of latex)). And the nice thing
about emacs is that you can really make your editor. Everything can be
done...

2010/6/9 Stéphane Rollandin :
>> Maybe there could be
>> 1) front ends with compatible versions of Csound included that could
>> be simple 'one-click' (or few clicks) downloads, which would be
>> reliable but not necessarily on the cutting edge of Csound
>> development.
>> 2) components listed completely separately for those who want to stay
>> on the cutting edge. (I guess this would be more or less what it is
>> now)
>
> This is exactly what I do with my own front-end: I provide both separate
> components and an all-in-one package including my own software plus all what
> is needed to run it, including the latest release of csound.
>
> (more at http://www.zogotounga.net/surmulot/surmulot.html)
>
> Stef
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


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

Hello,

I've just installed emacs on OS X. I'm completely new to emacs and  
have no idea where the site-lisp directory is, which is where your  
externals are installed right?

Thanks

Peiman

On 9 Jun 2010, at 19:58, Stéphane Rollandin wrote:

>> Maybe there could be
>> 1) front ends with compatible versions of Csound included that could
>> be simple 'one-click' (or few clicks) downloads, which would be
>> reliable but not necessarily on the cutting edge of Csound
>> development.
>> 2) components listed completely separately for those who want to stay
>> on the cutting edge. (I guess this would be more or less what it is
>> now)
>
> This is exactly what I do with my own front-end: I provide both  
> separate components and an all-in-one package including my own  
> software plus all what is needed to run it, including the latest  
> release of csound.
>
> (more at http://www.zogotounga.net/surmulot/surmulot.html)
>
> Stef
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

On Wed, Jun 9, 2010 at 18:18, Bernardo Barros  wrote:
> And the nice thing
> about emacs is that you can really make your editor. Everything can be
> done...

Like blowing up your hands trying to press Ctrl+blah, Ctrl+0... emacs
has a nice habit of setting the most annoying shortcuts. Vim FTW! (not
for csound, though).

> I've just installed emacs on OS X. I'm completely new to emacs and
> have no idea where the site-lisp directory is, which is where your
> externals are installed right?

I don't know where site-lisp is on OS X, but you can find it by looking 
at the value of variable load-path in Emacs

You can add any directory to the load-path, by evaluating something like:
(add-to-list 'load-path "my-path")

Stef




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

> Like blowing up your hands trying to press Ctrl+blah, Ctrl+0... emacs
> has a nice habit of setting the most annoying shortcuts. Vim FTW! (not
> for csound, though).
>

Felipe, you didn't understand what I said. You can set any shortcut to
anything you want if you don't like the standard ones.

If you are on a Mac, try Aquamacs Emacs. It has the same shortcuts of
all the others standard Mac applications. Some people prefer Carbon
Emacs, others like Aquamacs. In Carbon Emacs you can also install the
plug in (mode) for mac-keys

Like this:
(require 'mac-key-mode)
(mac-key-mode 1)

Or you can massively setup your own shortcuts (yes, Emacs Rocks!):

;; Functions Keys
(global-set-key (kbd "") 'sclang-start)
(global-set-key (kbd "") 'sclang-mode)
(global-set-key (kbd "") 'LilyPond-mode)
(global-set-key (kbd "") 'sclang-clear-post-buffer)

;; Just for SuperCollider
(add-hook 'sclang-mode-hook
	  (lambda ()
	    (define-key sclang-mode-map (kbd "C-c q") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c w") 'sc-while)
	    (define-key sclang-mode-map (kbd "C-c e") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c r") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c t") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c y") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c u") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c i") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c o") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c p") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c a") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c s") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c d") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c f") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c g") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c h") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c j") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c k") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c l") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c z") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c x") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c c") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c v") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c b") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c n") "-teste-")
	    (define-key sclang-mode-map (kbd "C-c m") "-teste-")
))

'sc-while stands for a skeleton where you could use a WHILE statement:

;;sc-while
(define-skeleton sc-while
  "Inserts SC while"
  "Condition: "
  \n
  > "while({ " str "}, {"
  \n
  > _
  \n
  > "});")


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

Bernardo,

he was just winding you up, he's a VIM guy. They are from another  
planet where people
cannot admire the greatness of emacs, so they make do with a  
substandard editor. ;)
No point of discussing it.

Victor

ps: I hope people in this list can recognise a windup when they see  
one. =)
On 10 Jun 2010, at 15:48, Bernardo Barros wrote:

>> Like blowing up your hands trying to press Ctrl+blah, Ctrl+0... emacs
>> has a nice habit of setting the most annoying shortcuts. Vim FTW!  
>> (not
>> for csound, though).
>>
>
> Felipe, you didn't understand what I said. You can set any shortcut to
> anything you want if you don't like the standard ones.
>
> If you are on a Mac, try Aquamacs Emacs. It has the same shortcuts of
> all the others standard Mac applications. Some people prefer Carbon
> Emacs, others like Aquamacs. In Carbon Emacs you can also install the
> plug in (mode) for mac-keys
>
> Like this:
> (require 'mac-key-mode)
> (mac-key-mode 1)
>
> Or you can massively setup your own shortcuts (yes, Emacs Rocks!):
>
> ;; Functions Keys
> (global-set-key (kbd "") 'sclang-start)
> (global-set-key (kbd "") 'sclang-mode)
> (global-set-key (kbd "") 'LilyPond-mode)
> (global-set-key (kbd "") 'sclang-clear-post-buffer)
>
> ;; Just for SuperCollider
> (add-hook 'sclang-mode-hook
> 	  (lambda ()
> 	    (define-key sclang-mode-map (kbd "C-c q") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c w") 'sc-while)
> 	    (define-key sclang-mode-map (kbd "C-c e") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c r") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c t") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c y") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c u") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c i") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c o") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c p") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c a") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c s") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c d") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c f") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c g") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c h") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c j") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c k") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c l") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c z") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c x") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c c") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c v") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c b") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c n") "-teste-")
> 	    (define-key sclang-mode-map (kbd "C-c m") "-teste-")
> ))
>
> 'sc-while stands for a skeleton where you could use a WHILE statement:
>
> ;;sc-while
> (define-skeleton sc-while
>  "Inserts SC while"
>  "Condition: "
>  \n
>> "while({ " str "}, {"
>  \n
>> _
>  \n
>> "});")
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

I think site-lisp for Aquamacs is

"/Library/Application Support/Emacs"

Victor
On 10 Jun 2010, at 08:35, Stéphane Rollandin wrote:

>> I've just installed emacs on OS X. I'm completely new to emacs and
>> have no idea where the site-lisp directory is, which is where your
>> externals are installed right?
>
> I don't know where site-lisp is on OS X, but you can find it by  
> looking at the value of variable load-path in Emacs
>
> You can add any directory to the load-path, by evaluating something  
> like:
> (add-to-list 'load-path "my-path")
>
> Stef
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

ok sorry :-)

On 10 June 2010 12:19, Victor Lazzarini  wrote:
> Bernardo,
>
> he was just winding you up, he's a VIM guy. They are from another planet
> where people
> cannot admire the greatness of emacs, so they make do with a substandard
> editor. ;)
> No point of discussing it.
>
> Victor
>
> ps: I hope people in this list can recognise a windup when they see one. =)
> On 10 Jun 2010, at 15:48, Bernardo Barros wrote:
>
>>> Like blowing up your hands trying to press Ctrl+blah, Ctrl+0... emacs
>>> has a nice habit of setting the most annoying shortcuts. Vim FTW! (not
>>> for csound, though).
>>>
>>
>> Felipe, you didn't understand what I said. You can set any shortcut to
>> anything you want if you don't like the standard ones.
>>
>> If you are on a Mac, try Aquamacs Emacs. It has the same shortcuts of
>> all the others standard Mac applications. Some people prefer Carbon
>> Emacs, others like Aquamacs. In Carbon Emacs you can also install the
>> plug in (mode) for mac-keys
>>
>> Like this:
>> (require 'mac-key-mode)
>> (mac-key-mode 1)
>>
>> Or you can massively setup your own shortcuts (yes, Emacs Rocks!):
>>
>> ;; Functions Keys
>> (global-set-key (kbd "") 'sclang-start)
>> (global-set-key (kbd "") 'sclang-mode)
>> (global-set-key (kbd "") 'LilyPond-mode)
>> (global-set-key (kbd "") 'sclang-clear-post-buffer)
>>
>> ;; Just for SuperCollider
>> (add-hook 'sclang-mode-hook
>>          (lambda ()
>>            (define-key sclang-mode-map (kbd "C-c q") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c w") 'sc-while)
>>            (define-key sclang-mode-map (kbd "C-c e") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c r") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c t") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c y") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c u") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c i") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c o") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c p") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c a") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c s") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c d") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c f") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c g") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c h") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c j") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c k") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c l") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c z") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c x") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c c") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c v") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c b") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c n") "-teste-")
>>            (define-key sclang-mode-map (kbd "C-c m") "-teste-")
>> ))
>>
>> 'sc-while stands for a skeleton where you could use a WHILE statement:
>>
>> ;;sc-while
>> (define-skeleton sc-while
>>  "Inserts SC while"
>>  "Condition: "
>>  \n
>>>
>>> "while({ " str "}, {"
>>
>>  \n
>>>
>>> _
>>
>>  \n
>>>
>>> "});")
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


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

You can use ~/.emacs.d/

.emacs and .emacs.d/ are not just for Aquamacs, but for any emacs you
use (GNU Emacs, Carbon Emacs, Aquamacs Emacs, or other future
branches).

See http://www.emacswiki.org/emacs/DotEmacsDotD

All files and folders starting with a dot are hidden files/folders. So
you may not see it in Finder.
If you want to see this files with FINDER:

defaults write com.apple.finder AppleShowAllFiles TRUE

then this to refresh the finder:

killall Finder

You can also put this silly aliases and something similar in yout
.bash_profile file, so you can turn it on and off easily:

alias showhidden="defaults write com.apple.finder AppleShowAllFiles"

then:

showhidden TRUE

or:

showhidden FALSE


On 10 June 2010 12:32, Victor Lazzarini  wrote:
> I think site-lisp for Aquamacs is
>
> "/Library/Application Support/Emacs"
>
> Victor
> On 10 Jun 2010, at 08:35, Stéphane Rollandin wrote:
>
>>> I've just installed emacs on OS X. I'm completely new to emacs and
>>> have no idea where the site-lisp directory is, which is where your
>>> externals are installed right?
>>
>> I don't know where site-lisp is on OS X, but you can find it by looking at
>> the value of variable load-path in Emacs
>>
>> You can add any directory to the load-path, by evaluating something like:
>> (add-to-list 'load-path "my-path")
>>
>> Stef
>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


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

Ah,
You can also specify any folder, you just have to add this to your
.emacs startup file:

(add-to-list 'load-path "~/theFolderWithTheStuff")


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

Thanks for the tips, I'm gonna give it a try!

P

On 10 Jun 2010, at 17:43, Bernardo Barros wrote:

> Ah,
> You can also specify any folder, you just have to add this to your
> .emacs startup file:
>
> (add-to-list 'load-path "~/theFolderWithTheStuff")
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



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

Hello,

> Error opening plugin directory '~': No such file or directory
> 

You have to customize the variables cscsd-OPCODEDIR and 
cscsd-OPCODEDIR64 so that they reflect your csound installation.

> It seems that csound-x didn't find csound

Well it found csound since you get that error message from it. What 
csound-x did was keep the default value for OPCODEDIR, which is "~", 
that is the default directory of emacs. What is weird here is that "~" 
seems not to have been expanded as it should have, so it really does not 
make any sense whatsoever to csound.

> But it runs from terminal.... I don't understand.
> Maybe the el file needs some hacking

Please begin by setting cscsd-OPCODEDIR and cscsd-OPCODEDIR64 to their 
correct value.

You can do this via command
M-x customize-group csound-x-applications-paths

Best,

Stef




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

> Please begin by setting cscsd-OPCODEDIR and cscsd-OPCODEDIR64 to their
> correct value.
>
> You can do this via command
> M-x customize-group csound-x-applications-paths

Oh, a simpler way is to use command
M-x surmulot-use-system-csound

This will have your csound-x settings reflect your system-wide settings, 
so it should read OPCODEDIR and al. directly from their values in the 
environment.

Never tried it in MacOS though, so please report any problem...


Stef




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