- if both XDG_DATA_HOME and XDG_STATE_HOME directories already exist,

  xdg_compliant will be set to True, even if not set in the
  configuration file (it means an XDG migration has been performed
  in the past; using the non-XDG dirs will lead to data loss)

Author: s-n-g

docs/headless.html

@@ -132,7 +132,7 @@ <h3 id="how-it-works">How it works</h3>
 <li><p>we cannot start a second headless server, and</p></li>
 <li><p>we can get info about the server running.</p></li>
 </ul>
-<p>The “headless server lock file” is saved as <em>~/.config/pyeadio/data/server-headles.txt</em> (or <em>~/.local/share/pyradio</em> if <strong>xdg_compliant</strong> is set to True), and will contain the IP address and port the servers is listening to. This is especially useful in case a user script needs to get this info (instead of parsing the output of the command <strong>pyradio –addr</strong>).</p>
+<p>The “headless server lock file” is saved as <em>~/.config/pyradio/data/server-headles.txt</em> (or <em>~/.local/share/pyradio/server-headles.txt</em> if <strong>xdg_compliant</strong> is set to True), and will contain the IP address and port the servers is listening to. This is especially useful in case a user script needs to get this info (instead of parsing the output of the command <strong>pyradio –addr</strong>).</p>
 <h2 id="installation">Installation <span style="padding-left: 10px;"><sup style="font-size: 50%"><a href="#" title="Go to top of the page">Top</a></sup></span></h2>
 <p>By the term “installation”, we mean that we set up things in such a way, that after we log into the system, we find <strong>PyRadio</strong> ready to accept connections.</p>
 <p>So, the installation can be as easy as adding a line in a configuration file (or the startup section of the <em>desktop environment</em>) or as hard as adding a system service.</p>

docs/headless.md

@@ -123,7 +123,7 @@ It will create a "headless server lock file", though, so that
 
 - we can get info about the server running.
 
-The "headless server lock file" is saved as *~/.config/pyeadio/data/server-headles.txt* (or *~/.local/share/pyradio* if **xdg_compliant** is set to True), and will contain the IP address and port the servers is listening to. This is especially useful in case a user script needs to get this info (instead of parsing the output of the command **pyradio --addr**).
+The "headless server lock file" is saved as *~/.config/pyradio/data/server-headles.txt* (or *~/.local/share/pyradio/server-headles.txt* if **xdg_compliant** is set to True), and will contain the IP address and port the servers is listening to. This is especially useful in case a user script needs to get this info (instead of parsing the output of the command **pyradio --addr**).
 
 ## Installation
 

docs/pyradio.1

@@ -1248,7 +1248,7 @@ Furthermore, if TERM is set to anything like "\fIxterm*\fR", "\fIscreen*\fR" or
 .IP 2. 3
 Terminals that do not support at least 16 colors will not be able to display any of the new themes. The same goes for terminals that do not support changing their colors (through the \fBcurses\fR library).
 
-These terminal will default to the old "\fBdark\fR" theme, displaying whatever colors the active palette dictates.
+These terminal will default to either the "\fBdark\fR" or the "\fBlight\fR theme (determined by the configuration parameter \fIconsole_theme\fR), displaying whatever colors the active palette dictates.
 
 .IP 3. 3
 There are a couple of terminals (that I know of) which will permit changing their colors but will not be able to present the changed color on the fly.

docs/themes.html

@@ -183,7 +183,7 @@ <h3 id="css-color-themes-restrictions">CSS color themes restrictions</h3>
 Furthermore, if TERM is set to anything like “<strong>xterm</strong>”, “<strong>screen</strong>” or “<strong>tmux</strong>”, <strong>PyRadio</strong> will set it to “<em>xterm-256color</em>” as well.</p></li>
 <li><p>Terminals that do not support at least 16 colors will not be able to display any of the new themes. The same goes for terminals that do not support changing their colors (through the <strong>curses</strong> library).<br />
 <br />
-These terminal will default to the old “<strong>dark</strong>” theme, displaying whatever colors the active palette dictates.</p></li>
+These terminal will default to either the “<strong>dark</strong>” or the “<strong>light</strong>” theme (determined by the configuration parameter <strong>console_theme</strong>), displaying whatever colors the active palette dictates.</p></li>
 <li><p>There are a couple of terminals (that I know of) which will permit changing their colors but will not be able to present the changed color on the fly.<br />
 <br />
 This means that, in order for a theme change to take full effect, <strong>PyRadio</strong> will have to be restarted.</p></li>

docs/themes.md

@@ -153,7 +153,7 @@ Furthermore, if TERM is set to anything like "**xterm**", "**screen**" or "**tmu
 
 2. Terminals that do not support at least 16 colors will not be able to display any of the new themes. The same goes for terminals that do not support changing their colors (through the **curses** library). \
 \
-These terminal will default to the old "**dark**" theme, displaying whatever colors the active palette dictates.
+These terminal will default to either the "**dark**" or the "**light**" theme (determined by the configuration parameter **console_theme**), displaying whatever colors the active palette dictates.
 
 3. There are a couple of terminals (that I know of) which will permit changing their colors but will not be able to present the changed color on the fly. \
 \

pyradio/config

@@ -194,7 +194,7 @@ remote_control_server_auto_start = False
 # Packagers should set this paramater as resired!
 #
 # Default value: False
-xdg_compliant = True
+xdg_compliant = False
 
 # The name of the distribution providing the package. If this parameter is set
 # to anything other than "None" PyRadio will not permit updating (-U command

pyradio/config.py

@@ -2343,6 +2343,16 @@ def _read_config(self, distro_config=False):
                     pass
             self._first_read = False
 
+        ''' detect previous XDG Base installation '''
+        if not platform.startswith('win')  and \
+                not self.xdg_compliant and \
+                distro_config:
+            d_dir = XdgDirs.get_xdg_dir('XDG_DATA_HOME')
+            s_dir = XdgDirs.get_xdg_dir('XDG_STATE_HOME')
+            if path.exists(d_dir) and path.exists(s_dir):
+                print('[magenta]XDG Dirs[/magenta] found; enabling [magenta]XDG Base compliant[/magenta] operation')
+                self.xdg_compliant = True
+
     def _make_sure_dirs_exist(self):
         if self.opts['recording_dir'][1] == '':
             self.opts['recording_dir'][1] = path.join(path.expanduser('~'), 'pyradio-recordings')