. . . while we're working on the command options, could we please get
csound --help | less and the like working? I mentioned this before,
and got a pretty la-dee-dah "It would be hard" answer. Having to go to
the full documentation to look at the list of flags is ridiculous.
I'm not the most-experienced user on earth, but this is the only
established piece of software I've found that lacks this ability.

Does that seriously bother people less than lack of  an always-on
setting? Isn't the current situation such that one could run csound
for months with minimal timing issues? Are you involving csound in
installation artwork or servers that run for years on end? If you are,
please share. That sounds awesome, and by all means, let's get
infinite rendering. Otherwise . . .
Is this about elegance? Really?

Isn't making csound more accessible in very, very orthodox ways to
those inexperienced users with limited resources more important than
catering to the specialized needs of what is starting to look to me
like an increasingly insular, almost-entirely professional academic,
and rapidly aging community with access to powerful machines who seem
mostly interested in performing complex tasks in realtime?

These are honest questions.

Also, do these people whose email clients add an extra "re" not
realize they're doing it? Could someone (with some sort of real, or
delegated by real authority) tell them politely off-list? I'd do it
myself if I felt it was place, but it certainly is not my place.
It comes up every couple months, nobody seems willing to take a
systematic approach to it, and It's really obnoxious.
If I do it (I don't believe I do), please tell me so I can fix it.

Greg


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

Actually it is more complex than you suggest.  This is not code I wrote,
but the problems lies with Csound not being a program but a library, with
an API to call it.  There are a number of driver programs including a
basic command-line one.  Messages of all kinds from the csound engine are
passed to the program via a callback mechanism.  The default version
pronts on stderr.  Clearly it could be changed to stdout, but that would
affect other stuff.  Or you could learn to redirect stderr with or example

csound --help |& less

(not sure of dsyntax in bash -- I have bene using (t)csh for decades)

==John ff

>  . . . while we're working on the command options, could we please get
> csound --help | less and the like working? I mentioned this before,
> and got a pretty la-dee-dah "It would be hard" answer. Having to go to
> the full documentation to look at the list of flags is ridiculous.
> I'm not the most-experienced user on earth, but this is the only
> established piece of software I've found that lacks this ability.
>
> Does that seriously bother people less than lack of  an always-on
> setting? Isn't the current situation such that one could run csound
> for months with minimal timing issues? Are you involving csound in
> installation artwork or servers that run for years on end? If you are,
> please share. That sounds awesome, and by all means, let's get
> infinite rendering. Otherwise . . .
> Is this about elegance? Really?
>
> Isn't making csound more accessible in very, very orthodox ways to
> those inexperienced users with limited resources more important than
> catering to the specialized needs of what is starting to look to me
> like an increasingly insular, almost-entirely professional academic,
> and rapidly aging community with access to powerful machines who seem
> mostly interested in performing complex tasks in realtime?
>
> These are honest questions.
>
>> Greg
>
>




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

Hello!
# The default version
# prints on stderr.  Clearly it could be changed to stdout, but that would
# affect other stuff.  Or you could learn to redirect stderr with or example
# csound --help |& less
# (not sure of dsyntax in bash -- I have bene using (t)csh for decades)
Searching for solutions to redirect stderr output to a pipe in a bash shell, I found the following:
http://www.cygwin.com/ml/cygwin/2003-06/msg00772.html
And using
csound --help 2>&1 | less
worked fine on my Ubuntu laptop (version 9.04).
Best wishes,
Anja Hofmann


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, both of you. To scripting (and bothering to learn more about
my shell) I go . . .
Greg

On Fri, Aug 20, 2010 at 9:56 AM, Anja Hofmann  wrote:
> Hello!
> # The default version
> # prints on stderr.  Clearly it could be changed to stdout, but that would
> # affect other stuff.  Or you could learn to redirect stderr with or example
> # csound --help |& less
> # (not sure of dsyntax in bash -- I have bene using (t)csh for decades)
> Searching for solutions to redirect stderr output to a pipe in a bash shell, I found the following:
> http://www.cygwin.com/ml/cygwin/2003-06/msg00772.html
> And using
> csound --help 2>&1 | less
> worked fine on my Ubuntu laptop (version 9.04).
> Best wishes,
> Anja Hofmann
>
>
> 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"

*both examples work for me.
Sorry for excluding that.
greg

On Sat, Aug 21, 2010 at 12:13 PM, Greg Schroeder  wrote:
> Thanks, both of you. To scripting (and bothering to learn more about
> my shell) I go . . .
> Greg
>
> On Fri, Aug 20, 2010 at 9:56 AM, Anja Hofmann  wrote:
>> Hello!
>> # The default version
>> # prints on stderr.  Clearly it could be changed to stdout, but that would
>> # affect other stuff.  Or you could learn to redirect stderr with or example
>> # csound --help |& less
>> # (not sure of dsyntax in bash -- I have bene using (t)csh for decades)
>> Searching for solutions to redirect stderr output to a pipe in a bash shell, I found the following:
>> http://www.cygwin.com/ml/cygwin/2003-06/msg00772.html
>> And using
>> csound --help 2>&1 | less
>> worked fine on my Ubuntu laptop (version 9.04).
>> Best wishes,
>> Anja Hofmann
>>
>>
>> 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"