Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xpra subcommands should assume current instance where possible #3371

Closed
karlkleinpaste opened this issue Nov 30, 2021 · 3 comments
Closed

xpra subcommands should assume current instance where possible #3371

karlkleinpaste opened this issue Nov 30, 2021 · 3 comments
Labels
client enhancement New feature or request

Comments

@karlkleinpaste
Copy link

$ xpra detach
xpra initialization error:
 there are multiple servers running, please specify

When xpra is run from an xpra-driven window, it should be reasonable to assume that the server in question is $DISPLAY, yes? Is there a good reason not to default to $DISPLAY?

Many subcommands could assume this, like xpra screenshot xyz.png. Perhaps something more precise and xpra-specific than $DISPLAY is in order, like maybe XPRA_SERVER_SOCKET.

When there's a genuine ambiguity, notably when no $DISPLAY exists, sure, xpra should ask for specifics.

@totaam totaam added client enhancement New feature or request labels Dec 1, 2021
@totaam totaam changed the title enhancement: xpra subcommands should assume current instance where possible xpra subcommands should assume current instance where possible Dec 4, 2021
@totaam
Copy link
Collaborator

totaam commented Apr 26, 2022

Done in the commit above for most subcommands: info, id, shell, qrcode, version, detach, show-menu, show-session-info, etc..
This uses XPRA_SERVER_SOCKET because, as you pointed out, that's much more likely to be correct.

@normanr
Copy link

normanr commented Oct 7, 2022

I noticed that control and print both still require the DISPLAY argument, but I discovered that it's allowed to be empty :-)

@totaam
Copy link
Collaborator

totaam commented Oct 8, 2022

I noticed that control and print both still require the DISPLAY argument, but I discovered that it's allowed to be empty :-)

Yes, we use positional arguments so it can't be removed completely but you can use an empty placeholder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants