On Thu, Aug 2, 2018 at 11:05 PM, richard lucassen
wrote:
> When being a road warrior you can't do anything with a reverse lookup.
Ok, accepted...
>> What exactly is the reason for the xmodmap stuff? We aim to always
>> ensure a proper keyboard setting. I even have code that replicates the
>>
On Thu, 2 Aug 2018 22:16:19 +0200
Ulrich Sibiller wrote:
> On Thu, Aug 2, 2018 at 4:12 PM, richard lucassen
> wrote:
> > Ok, I already looked at the SSH_ environment variables but I cannot
> > use IP :-(
>
> Just do a reverse lookup of the ip.
When being a road warrior you can't do anything
Am 02.08.2018 um 22:16 schrieb Ulrich Sibiller:
> What exactly is the reason for the xmodmap stuff? We aim to always
> ensure a proper keyboard setting. I even have code that replicates the
> client's keyboard configuration (unfortunately still not in production
> code).
He explained it in
On Thu, Aug 2, 2018 at 4:12 PM, richard lucassen
wrote:
> Ok, I already looked at the SSH_ environment variables but I cannot use
> IP :-(
Just do a reverse lookup of the ip.
What exactly is the reason for the xmodmap stuff? We aim to always
ensure a proper keyboard setting. I even have code
On Thu, 2 Aug 2018 15:48:26 +0200
Stefan Baur wrote:
> > I use "Custom desktop" as windowmanager, I start the session with a
> > script with the client name as parameter. In this way I'm able to
> > find the client name of the station which /initialized/ the session.
> >
> > But is there a way
Am 02.08.2018 um 15:38 schrieb richard lucassen:
> Hello list,
>
> I use "Custom desktop" as windowmanager, I start the session with a
> script with the client name as parameter. In this way I'm able to
> find the client name of the station which /initialized/ the session.
>
> But is there a way
