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

#7 XDG Compatibility #26

Closed
wants to merge 2 commits into from
Closed

#7 XDG Compatibility #26

wants to merge 2 commits into from

Conversation

zsedem
Copy link

@zsedem zsedem commented Feb 27, 2016

add support for configure from ~/.config/xmonad folder

Signed-off-by: Zsigmond Adam Oliver <zsedem@gmail.com>
@@ -1,8 +1,10 @@
== Configuring xmonad ==

xmonad is configured by creating and editing the file:
xmonad is configured by xmonad.hs the paths are searched are:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

drop the first "are"

@zsedem zsedem mentioned this pull request Feb 27, 2016
Signed-off-by: Zsigmond Adam Oliver <zsedem@gmail.com>
@geekosaur
Copy link
Contributor

I still want to see proper XDG support, not chuck-all-the-files-under-$XDG_CONFIG_HOME which violates XDG and is not compatible with network home directories.

Additionally, there's a number of open issues that all touch the same xmonad core code and really need to be done together, unless we plan to rewrite that code completely for each change. See https://github.com/geekosaur/xmonad.hs/blob/master/new-startup-config for an outline that addresses all of:

  • XDG (and proper OS X --- yes, people use xmonad on OS X) support
  • sandbox support (cabal and stack)
  • a proper fix for the xmonad-on-$PATH issue, plus other mechanisms to work around XDG sessions essentially requiring a full session manager
  • more flexibility in order to support e.g. testing configurations (this is not discussed in the above but the design is actually based around working code I've used for that; I still need to work out interactions with the sandbox support)
  • handling the xmessage problem (this part is still subject to change, as the current spec is very definitely a hack based around accommodating existing contribs' usage of xmessage instead of rewriting them)

Some of these actually conflict rather badly, notably naïve sandboxes are incompatible with XDG. I don't expect to be able to resolve that, but I can make it possible for the user to resolve it if they need to instead of forcing them into noncompliance.

@geekosaur geekosaur closed this Mar 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants