Skip to content

Alternative Config Locations? #113

@sfalken

Description

@sfalken

In #66 it looks like you've implemented a -C switch to specify alternative configuration locations, but either it's not working, or I don't understand how it's supposed to work.

Just for example, the reason I want to do so, is that labwc is one of the compositors that lxqt-wayland is supporting. The upstream configuration is putting it's user configs in ~/.config/labwc which is labwc's default configuration location.

The problem is, if you've got users that want to use labwc with, and without lxqt, it means that lxqt's configurations are going to be the same ones that you get in a raw labwc session.

So what we've done on Fedora and openSUSE, is moved lxqt's configurations to ~/.config/lxqt/labwc which will allow the bare labwc session to keep it's configs in the default location, and only use lxqt specific configs when using labwc in conjunction with the lxqt-labwc-session.

So tl;dr I tried launching labwc-tweaks with variations of labwc-tweaks -C lxqt/labwc labwc-tweaks -C .config/lxqt/labwc labwc-tweaks -C ~/.config/lxqt/labwc/ etc.

None of them seem to actually work, so this could completely be me misunderstanding how this works.

(Note: I haven't packaged up the latest git pull, so I still have the qt.svg error, but I don't think that has anything to do with the issue.)

sfalken@fedora:~/Desktop$ labwc-tweaks -C /home/sfalken/.config/lxqt/labwc
warn: fopen(/home/sfalken/.config/labwc/rc.xml) failed
I/O warning : failed to load external entity "/home/sfalken/.config/labwc/rc.xml"
warn: xmlReadFile('/home/sfalken/.config/labwc/rc.xml')
qt.svg: Cannot open file '/usr/bin/labwc_tweaks.svg', because: No such file or directory
qt.svg: Cannot open file '/usr/bin/labwc_tweaks.svg', because: No such file or directory

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions