[X2Go-User] Keyboard Translation Mac/OS

[Robert Dinse]

      What seems odd to me is that if I originate from a Ubuntu machine, with
csh as the shell on the target host, it works.  It only breaks if originated
from a Mac.  It would seem there should be some way to separate the shell
x2go uses to process commands, i.e., explicitly invoking /bin/bash instead of
just assuming it's what will process the commands, for instances where users
are using something else.  Ksh is a superset of bourne shell as is bash so
that's probably why it has enough in common to work.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 5 May 2015, Mihai Moldovan wrote:

> Date: Tue, 05 May 2015 00:55:54 +0200
> From: Mihai Moldovan <ionic at ionic.de>
> To: nanook at eskimo.com
> Cc: "x2go-user at lists.x2go.org" <x2go-user at lists.x2go.org>
> Subject: Re: [X2Go-User] Keyboard Translation Mac/OS
> 
> On 05.05.2015 12:48 AM, nanook at eskimo.com wrote:
>>      That's unfortunate, however it works fine with ksh, and remmina which
>> uses nx works fine with csh however it's not available for Apple, so it
>> looks like Apple users are just pretty much screwed.  Not the response I
>> was hoping for but if that's what it is, that's what it is.
>
> Well, there isn't a real technical reason why we support bash only, it's just
> that the current code kind of relies on it to work and has never been testing
> with anything else but the bash-like dash and maybe the POSIX-compatible
> dash/bash sh-emulation.
>
> ksh is bash-like enough to by chance "just work".
>
> You'll see weird behavior with csh and others, though.
>
> Besides making all remote calls POSIX sh-compatible, I wouldn't know how to fix
> the problem. And I'm not even sure csh and friends *are* POSIX sh-compatible,
> without looking it up first...
>
> That wasn't meant as a "bash or die" statement, but given the current state of
> affairs, it comes close to that.
>
>
>
> Mihai
>
>