When I want an ability to use multiple windows in X,
I launch a window manager with startx.

When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen,
but now I am instead brought into Xfce4 with its remembered
windows which I have no intention of launching.

Is the place to correct this to be found in files related
to the X server,the window manager,or the game?

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

Louis Epstein <le@lekno.ws> writes:
> When I want to play OpenTTD full-screen,I have launched
> "xinit openttd" and had this bring up the game full-screen, ...

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."

-WBE

Winston <wbe@ubeblock.psr.com.invalid> wrote:
> Louis Epstein <le@lekno.ws> writes:
>> When I want to play OpenTTD full-screen,I have launched
>> "xinit openttd" and had this bring up the game full-screen, ...
>
> 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."
>
> -WBE

Is this a recent change to functionality?
I know "xinit openttd" worked before.

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

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
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.
-WBE

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.

Louis Epstein wrote:

> 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.

The icewm bar can be hidden with the ">" button if you enable it with
TaskBarShowCollapseButton=1.

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
> 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.
> -WBE

The issue may be with my .xinitrc invoking the window manager,
apparently that was not there before (AND I used a different
window manager).

Will have to explore.

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

I previously wrote in this thread:
>> 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.

[or, as you've correctly pointed out, a window manager issue ...]

to which Louis Epstein <le@lekno.ws> writes:
> The issue may be with my .xinitrc invoking the window manager,
> apparently that was not there before (AND I used a different
> window manager).

I'd be surprised if it has anything to do with .xinitrc, but not
surprised if some window manager has an always-on-top bar of some kind.
twm, for example, does not. As Gerhard indicated, window managers
that have tool bars may also have a way of getting rid of it, or at
least of disabling its always-on-top property.
-WBE

Winston <wbe@ubeblock.psr.com.invalid> wrote:
> I previously wrote in this thread:
>>> 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.
>
> [or, as you've correctly pointed out, a window manager issue ...]
>
> to which Louis Epstein <le@lekno.ws> writes:
>> The issue may be with my .xinitrc invoking the window manager,
>> apparently that was not there before (AND I used a different
>> window manager).
>
> I'd be surprised if it has anything to do with .xinitrc, but not
> surprised if some window manager has an always-on-top bar of some kind.
> twm, for example, does not. As Gerhard indicated, window managers
> that have tool bars may also have a way of getting rid of it, or at
> least of disabling its always-on-top property.
> -WBE

I used fvwm2 before and this time it's xfce4.

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

I previously wrote in this thread:
>>>> 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.

to which Louis Epstein <le@lekno.ws> replied:
>>> The issue may be with my .xinitrc invoking the window manager,
>>> apparently that was not there before (AND I used a different
>>> window manager).

I replied:
>> I'd be surprised if it has anything to do with .xinitrc, but not
>> surprised if some window manager has an always-on-top bar of some
>> kind. twm, for example, does not. As Gerhard indicated, window
>> managers that have tool bars may also have a way of getting rid of
>> it, or at least of disabling its always-on-top property.

Louis replied:
> I used fvwm2 before and this time it's xfce4.

A Google search turned up the following regarding xfce4, which you could
try:

How do I hide the top bar in xfce4?

Right click on the terminal, select preferences. You'll be on the
"General" tab: Lots of features here, including eliminating the
scrollbar. If you click on the "Appearance" tab, in the section
"Opening New Windows" you can select whether or not to see the
menubar, the toolbar or the borders.

It looks like that answer comes from
https://forum.xfce.org/viewtopic.php?id=13350
which discusses the issue in connection with xfce4-terminal. There's
also a suggestion that "--maximize --hide-menubar --hide-borders" might
do what you want.

If that doesn't work, while reading, I got the impression that one can
have multiple panels, that different panels can have different
properties, and thus that you might be able to create a second desktop
panel that has no toolbar that you could switch to when you want that.

HTH, but I don't know xfce,
-WBE