Identifying the real display server

[Thiago Macieira]

On Monday 13 April 2015 23:08:26 Mattias Andrée wrote:
> Consider the URL parsing code too, and
> the fact that you need in object oriented
> languages need to create an instance of an
> URL class. Additionally, we cannot assume
> that the generic syntax covers all display
> server's syntax. In fact, x11 is not
> covered. There is also the complexity of
> URL encoding the pathnames. In shell scripts.
> Furthermore at least DISPLAY must remain
> for because of legacy programs.

I hadn't considered shell scripts. What's the use you're thinking for them 
here? To use as a wrapper for the front-end application but launching different 
backends or passing different options depending on the display server?

As for x11, it is covered just fine with x11::0.
-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/xdg/attachments/20150413/bc66238c/attachment.sig>