It has to be (u)xterm because it is the only terminal we have(had)
that handles utf-8 correctly end-to-end in both the shell (on the
command line) and in local and remote applications that don't generate
their own windows.
- the emacs that comes with Tiger or Leopard runs only in an xterm
window. In order to encode utf-8 correctly it needs to run in a
uxterm. Now that doesn't work.
- when I log on to a machine at my university in Beirut (I work
there part time but live in Norway) which is behind firewalls and
other barricades, there is no way an X11 application is going to
show its own pretty face here. But I still want utf-8 to work - I
will often be working with various Latin scripts and Arabic in one
and the same file.
Having worked this far I just don't see any good reason why it
shouldn't work again. Terminal.app doesn't just doesn't do it. Don't
the people who make this stuff realize that there's a world beyond
- Børre Ludvigsen
On Sun, Oct 28, 2007 at 05:16:42PM -0400, Mark J. Reed wrote:
> On 10/28/07, Bob Greschke <email@hidden> wrote:
> > We have secretaries (that are not going to be entering command line
> > anythings any time soon) that just start X11, pull down the
> > Applications menu and select an item that ssh'es them into, let's say,
> > our inventory system. How will that work now?
> Why does it have to be an xterm? There are much better terminal
> applications for the Mac. With the new automatic X start, you can use
> any of them, ssh -X somewhere, and still have the ability to fire up
> remote X apps.
> Heck, instead of using the Applications menu, you could have them
> double-click an icon that is a shell script that just does "ssh -Y
> hostname". Mac OS will fire up Terminal and execute the ssh command,
> and whatever it is they've been doing in xterm will continue to work.
Børre Ludvigsen - http://www.hiof.no/~borrel/ - +47 908 24 608
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden