The only problem I’ve run into so far on OS X is (and it could be my
fault, I’m not sure) terminal.app’s poor handling of ncurses (and thus
ruby-ncurses).
–matt
The only problem I’ve run into so far on OS X is (and it could be my
fault, I’m not sure) terminal.app’s poor handling of ncurses (and thus
ruby-ncurses).
–matt
[email protected] writes:
The only problem I’ve run into so far on OS X is (and it could be my
fault, I’m not sure) terminal.app’s poor handling of ncurses (and thus
ruby-ncurses).
I recommend iTerm.
On 11/19/05, [email protected]
[email protected] wrote:
The only problem I’ve run into so far on OS X is (and it could be my
fault, I’m not sure) terminal.app’s poor handling of ncurses (and thus
ruby-ncurses).
What problems does Terminal.app cause?
I connect to screen with several curses applications from OS X,
NetBSD, and GNU/Linux, and I did not notice any problem specific to
Terminal.app.
Michal
–
Support the freedom of music!
Maybe it’s a weird genre … but weird is not illegal.
Maybe next time they will send a special forces commando
to your picnic … because they think you are weird.
www.music-versus-guns.org http://en.policejnistat.cz
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs