On Sun, 2014-09-14 at 13:53 -0600, Glenn Golden wrote: > Hi David, > > David Henningsson <david.henningsson at canonical.com> [2014-09-08 15:22:22 +0200]: > > > > If none of the above is present, all of the list below will be is tried, in > > this priority order: > > > > 5) Per-user instance: > > 5a) based on PULSE_RUNTIME_PATH > > 5b) based on XDG_CONFIG_DIR (if no PULSE_RUNTIME_PATH) > > 5c) based on ~/.pulse (if no XDG_CONFIG_DIR) > > 5d) based on XDG_CONFIG_HOME (if ~/.pulse does not already exist) > > 5e) based on ~/.config/pulse (if no XDG_CONFIG_HOME) > > > > In 5b-c, is it possible that XDG_RUNTIME_DIR was intended? I can't find any > doc for envar XDG_CONFIG_DIR in the XDG Base Directory Spec (although there > is an XDG_CONFIG_DIRS, but that seems like that's intended for configuration > stuff rather than for locating runtime files like the socket or pidfile...) > > If XDG_CONFIG_DIR was intended (or perhaps just a typo, intended to be ...DIRS) > then how/where does XDG_RUNTIME_DIR itself come into the picture? David meant XDG_RUNTIME_DIR when he wrote XDG_CONFIG_DIR (I'm sure, because I checked the code). -- Tanu
