On 2010-02-05 11:14 , Russel Winder wrote: > I appreciate that this isn't so much a dark corner, more inside the > event horizon of a black hole, but . . . > > If I connect to a Mac OS X machine using SSH over Ethernet, I get a > terminal as per expectation. (I should add that normally I am logged > onto the console of the machine even though I don't actually use the > console because various things to do with using Java on a Mac OS X > machine require you to be logged onto the console before connecting via > SSH over Ethernet.) > > If I do: > > bzr log > > then the output appears on the terminal. If I do: > > bzr explorer . > > then a window appears on the console, and nothing appears on the > terminal, it just appears to have hung. Both of these surprised me. A > lot.
This is the way that SSH connections to Mac OS X machines work. If you are logged in on the console and you start a graphical application in an SSH session, that application can make its windows on the console. No output to the terminal is the ordinary behavior of the ``bzr explorer`` command and nothing different is happening here. If you want to surprise yourself more, run a terminal on the console, SSH to localhost and do "open -a TextEdit.app". Bug or feature, it's up to you, but this is the way OS X works. -Neil _______________________________________________ Mailing list: https://launchpad.net/~bzr-mac Post to : bzr-mac@lists.launchpad.net Unsubscribe : https://launchpad.net/~bzr-mac More help : https://help.launchpad.net/ListHelp
