Stéphane Rollandin wrote:

>> I'm a bit confused posting about csound-x on this list, but maybe someone
>> here uses (or tries to) it too and could help me.
> 
> well I am the developper and as far as I am concerned this is the right
> place for general questions about it.
> 
> now if the problem happens to be very specific to your
> installation/system, then we may proceed via private mails.
> 
>> And when i try to 'process file' (from the CSD menu), i get following
>> error message:
>> Error opening plugin directory '~': ??? ?????? ????? ??? ????????
>> 
> 
> this is a csound error message, and it seems to say that your plugin
> directory is not valid. the following garbage is not related to csound-x
> in any way I can fathom.

You're right. More than that, it's related to my /dev/hands/ and /dev/brain 
(as i recently discovered). I just didn't want that "custom" mess in my 
.emacs, so i decided to split it to a number of files, each of which would 
include settings for a particular package (stef-elisp in this case). 
However, i encountered some unusual (to me) behavior of Emacs (i'm just a 
newbie in Emacs, Elisp, Csound and everything else you could probably 
imagine ))), concerning environment variables managing. My code for setting 
csound-x environment was at least incorrect i suppose (but for now i didn't 
figured out which is the correct one). Now if i use "custom" to set 
environment of csound-x, everything works fine (but i have a little mess in 
.emacs thanks to "custom" code).
> 

So, if i use (setq ....) to set environment, then
 does (file-exists-p (cscsd-OPCODEDIR)) return t in Emacs ? yes
 does (cscsd-OPCODEDIR) indeed return "/usr/lib/csound/plugins64-5.2/" ? yes
 does (getenv "OPCODEDIR") also return "/usr/lib/csound/plugins64-5.2/" ? no 
(it's '~')

But i think there is a way to set things correct without using "custom", 
which i will try to discover meanwhile.

PS. That way is not in using (setenv ...) which i tried and it won't work as 
expected.


 
> best,
> 
> Stef
> 
> 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Mon, 2009-11-09 at 01:00 +0400, Dmitriy wrote:
> Stéphane Rollandin wrote:
> 
> >> I'm a bit confused posting about csound-x on this list, but maybe someone
> >> here uses (or tries to) it too and could help me.
> > 
> > well I am the developper and as far as I am concerned this is the right
> > place for general questions about it.
> > 
> > now if the problem happens to be very specific to your
> > installation/system, then we may proceed via private mails.
> > 
> >> And when i try to 'process file' (from the CSD menu), i get following
> >> error message:
> >> Error opening plugin directory '~': ??? ?????? ????? ??? ????????
> >> 
> > 
> > this is a csound error message, and it seems to say that your plugin
> > directory is not valid. the following garbage is not related to csound-x
> > in any way I can fathom.
> 
> You're right. More than that, it's related to my /dev/hands/ and /dev/brain 
> (as i recently discovered). I just didn't want that "custom" mess in my 
> .emacs, so i decided to split it to a number of files, each of which would 
> include settings for a particular package (stef-elisp in this case). 
> However, i encountered some unusual (to me) behavior of Emacs (i'm just a 
> newbie in Emacs, Elisp, Csound and everything else you could probably 
> imagine ))), concerning environment variables managing. My code for setting 
> csound-x environment was at least incorrect i suppose (but for now i didn't 
> figured out which is the correct one). Now if i use "custom" to set 
> environment of csound-x, everything works fine (but i have a little mess in 
> .emacs thanks to "custom" code).
> > 
> 
> So, if i use (setq ....) to set environment, then
>  does (file-exists-p (cscsd-OPCODEDIR)) return t in Emacs ? yes
>  does (cscsd-OPCODEDIR) indeed return "/usr/lib/csound/plugins64-5.2/" ? yes
>  does (getenv "OPCODEDIR") also return "/usr/lib/csound/plugins64-5.2/" ? no 
> (it's '~')
> 
> But i think there is a way to set things correct without using "custom", 
> which i will try to discover meanwhile.
> 
> PS. That way is not in using (setenv ...) which i tried and it won't work as 
> expected.

Note that there is probably some mangling involved that shouldn't really
be there. Debian csound does not need OPCODEDIR64 to be set to work (it
defaults to the location of the Debian provided plugins).


-- 
Saludos,
Felipe Sateler

>>
>> But i think there is a way to set things correct without using "custom", 
>> which i will try to discover meanwhile.

have a look at the code around line 90 in csound-csd.el
that's where the environment variable handling via custom is 
implemented. beware of the big macros :) cscsd-defenv does most of the job.

this thing is rather complex, also because csound-x is a component of a 
larger system, called Surmulot, where csound is packaged as another 
component. in Surmulot, the user can swap on-the-fly from the packaged 
csound to its own system-wide csound, if any. so csound-x provides all 
the logic needed to reconfigure the whole environment of the Emacs 
process dynamically.

if you're brave enough to go and dig in the code, then good luck !

best,

Stef




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"