-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
allow additional options to X server invocation #3553
Comments
Would an environment variable be acceptable? xpra start-desktop --env=XPRA_XVFB_EXTRA_ARGS="-query 127.0.0.1 -once"` |
That would be fine with me. |
Done. Tested with the commit above and
I assumed that it wouldn't be a problem if the extra args aren't right at the end. Works for me(tm). |
Thanx much. Looking forward to the beta *.rpm. |
Are xpra's XPRA_WHATEVER environment variables documented anywhere? |
This question comes up regularly. No, they are not documented. A quick grep on the codebase reveals over 500 locations where such variables are looked up. Some may duplicates or mostly irrelevant, but still, that's a big number. |
This update works, but only so long as one is executing the That is, I use a local wrapper shell script that takes a few options to simplify what I want to do, constructs an
The problem appears to be convincing the extra args content to survive the underlying
The only -o present is part of -once. I've tried extra levels of quotation ( Turning the command around, to make it an
The local shell sees double-quotes to preserve the content as one shell token, including its single-quotes, and when that arrives at the remote, its shell sees the single-quotes which again preserves everything in Further, for testing in the original generated command, when I remove "-query 127.0.0.1" leaving just "-once" (which makes no sense, but it would let me address the whitespace problem), so that I wouldn't need quotation at all, I get an inconsistent diagnostic:
The whitespace problem seems a general operational issue of how to reference |
Can you please file separate bugs for these issues:
|
Is your feature request related to a problem? Please describe.
Not a problem per se. Rather, something I would like to be able to do.
Describe the solution you'd like
When starting, I would like to be able to specify more server options to be added to Xorg invocation. My specific case is that I'd like to use
-query 127.0.0.1 -once
when usingstart-desktop
in order to engage XDMCP, providing for a typical login screen in the new desktop.Describe alternatives you've considered
There really aren't any substitutes for this particular kind of use, as there's no mechanism by which to get XDMCP involved without the X server itself asking for it.
Additional context
The realm of consideration for me is quite specific, but it would be a nice generalization to allow the user to specify any desirable new options.
The text was updated successfully, but these errors were encountered: