Re: [Bug-apl] stdin still echoed to stdout even with --noCIN

2014-05-23 Thread Peter Teeson
Hi Jürgen: Thanks for your suggestion but CinOut::overflow(int c) { Q(uprefs.echo_current_file()); if (!uprefs.echo_current_file()) return 0; CInOut::overflow(int c) is never called. Please see my next post. Peter On 2014-05-23, at 8:43 AM, Juergen Sauermann wrote: > Hi Peter, >

Re: [Bug-apl] stdin still echoed to stdout even with --noCIN

2014-05-23 Thread Juergen Sauermann
Hi Peter, the decision if a cin character, say *c*, should be echoed or not is made in *CinOut::overflow(int c)* by asking *uprefs.echo_current_file()*. Note that *uprefs.echo_current_file() *not only depends on the command line option *--noCIN* but also on its position in relation to *-f *(if u

[Bug-apl] stdin still echoed to stdout even with --noCIN

2014-05-22 Thread Peter Teeson
In Xcode I pass TERM=xterm-256color as an env var. This is the value Terminal uses. Also --noCIN as an option at launch time to turn off echoing stdin. Set breakpoint here in UserPreferences.cc: else if (!strcmp(opt, "--noCIN")) { do_not_echo = true;