Akinori Musha
Akinori Musha
The error you'll be seeing is Errno::EBADF, right? I'd rather do the following than to check the platform: ```ruby def noecho(&block) STDIN.noecho(&block) rescue Errno::EBADF begin print "\e[0;8m" STDOUT.flush block.call ensure...
I suppose noecho is mainly to prevent shoulder surfing. If someone had access to the terminal (emulator), they'd already have stolen what was typed.
Can we give the "rescue Errno::EBADF" approach a try? I'm not sure what exactly platform(s) this is about, so I think it's better to resort to symptomatic treatment.
I think this is fine as long as it is an opt-in feature. PostAgent and WebsiteAgent already deal with text responses and a text response in JSON/HTML/XML could also be...
I think the parameter name could be as simple as `category`.
My impression is that it is not a welcome situation of an agent having to have the knowledge of the event flow beyond its direct source. Can't we just have...
> > My impression is that it is not a welcome situation of an agent having to have the knowledge of the event flow beyond its direct source. > >...
OK, I'll check it out after fixing the broken specs.
Looks like calling select2() on an input element has been deprecated as of 4.0, so we might need to reimplement the presenter and the handler.
Thanks for the information. I worked hard to make Digest easy to extend, ensuring that adding new algorithms as external modules would be easy. From what I can see from...