Re: ratpoison under XQuartz?
Re: ratpoison under XQuartz?
- Subject: Re: ratpoison under XQuartz?
- From: Jeremy Huddleston <email@hidden>
- Date: Fri, 06 May 2011 11:16:49 -0700
On May 6, 2011, at 10:46, Bayard Bell wrote:
> On 6 May 2011, at 18:24, Jeremy Huddleston wrote:
>
>>> Just to check on the concatenation of the two previous items, when I duplicate XQuartz and modify the bundle ID, I notice that Spaces can't work out what the application name is (is that bug in there?). I don't suppose this further data point somehow arrives at adequately convincing evidence of what you already suspect, if not know, which is that copying code to introduce a config change the application really should be able to handle anyway is broken, even if it isn't necessarily a bug (or *sigh* going to be fixed)?
>>
>> What config change are you trying to make that you suspect should be handled in XQuartz.app directly? You want to run more than one server, right? XQuartz.app currently supports only one X11 server. Supporting more than one server in the same process is not likely something that will change soon (if ever).
>
> It doesn't need to be in the same process, just that when I run a second server, something like X11_PREFS_DOMAIN as an environment variable coming from a launchd definition should be sufficient to establish a second identity.
It is.
> Copying the application image on a filesystem level and modifying the bundle ID seems a long way around that ends up with unintended and unnecessary complications.
No, that's how X11_PREFS_DOMAIN gets set in the first place.
> I appreciate that there's a need to support this off via bundle IDs to run different code with different configs, but it doesn't follow that a different config should require a different copy of the same code, meaning that bundle IDs shouldn't the only way to do this.
If you want to differentiate between two configs, you're free to do it however you want. If you prefer another approach, you can write a launcher that will toggle between sets of preferences then launches the real application if you want. That's just something that most people aren't interested in.
>>> To my mind, the fact that auto-updates don't work is just a further inconvenient consequence of an attempt at being clever that didn't really pan out and still deserves a solution.
>>
>> What is the root problem that you are trying to solve?
>
> If I want to run something that's using a separate user window manager, I need a separate server instance.
yes.
> I'm just trying to minimise the result overhead to managing configuration differences and nothing else.
Just use ~/.xinitrc.d then. Create a launcher that manages the permissions of those files and have it run as ~/.xinitrc.d/00-setperms.sh or similar
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden