Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.main.lekno.ws!not-for-mail
From: Louis Epstein <le@lekno.ws>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: X launch hijack?
Date: Tue, 7 Jan 2025 00:41:37 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vlht81$k76$1@reader2.panix.com>
References: <vl7n3t$5ks$1@reader2.panix.com> <ydttaggxpe.fsf@UBEblock.psr.com> <vl9pfo$jkp$1@reader2.panix.com> <ydpll3gjal.fsf@UBEblock.psr.com>
Injection-Date: Tue, 7 Jan 2025 00:41:37 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="main.lekno.ws:12.144.5.2";
	logging-data="20710"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.4-20241224 ("Helmsdale") (FreeBSD/13.4-RELEASE-p1 (amd64))
Bytes: 2585
Lines: 44

Winston <wbe@ubeblock.psr.com.invalid> wrote:
> Louis Epstein <le@lekno.ws> posted:
>>>> When I want to play OpenTTD full-screen,I have launched
>>>> "xinit openttd" and had this bring up the game full-screen, ...
> 
> to which I replied:
>>> man 1 xinit says:
>>>    "Both the client program name and the server program name must begin
>>>    with a slash (/) or a period (.).  Otherwise, they are treated as an
>>>    arguments to be appended to their respective startup lines."
> 
> Louis Epstein <le@lekno.ws> replied:
>> Is this a recent change to functionality?
> 
> An xinit man page from 1990 that has copyright 1988 says the same thing,
> so not what I'd call recently.
> 
>> I know "xinit openttd" worked before.
> 
> Don't know.  "xinit `which openttd`", which isn't much longer, should

Takes me into the program (with error message saying it can't find
graphic files that it's just not looking for in the right place)
BUT THE CURSOR DISAPPEARS.

(on exit...this is not unique to openttd...I get a list of
xkbcomp keysym errors).

> work, I would think.  If you define openttd as an environment variable,
> you could even do "xinit $openttd".  :)
> 
> The other thing I don't understand is why you need to do that at all.
> X11 programs are entirely capable of having their window be full-screen
> size even after a standard xinit/startx startup, so I would think you
> wouldn't need to do a special startup to get full-screen, unless that's
> an openttd issue.

X-window managers I've used have top/bottom bars that windows can't cover
and full-screen OpenTTD uses that space for key menu/status stuff.

>  -WBE

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.