You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2id="changelog">Changelog <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></span></h2>
216
216
<prestyle="height: 200px;">
217
217
218
+
2024-08-30 s-n-g
219
+
* version 0.9.3.10
220
+
* do not enable xdg compliant if user_config_dir is specified
221
+
* do not create the default recording directory until it is
222
+
actually needed (to save data in it)
223
+
* when saving players' extra parameters reduce the list by removing
224
+
the unused porifles from the list
225
+
* Fixing player_params_file and schedule_file location when XDG
226
+
compliance is ON
227
+
* fixing a pyradio-client crash when no command is specified
228
+
* fixing: MPV Volume resets to 0% when trying to increase
229
+
beyond maximum #251
230
+
* fixing a help crash: adding H_CONFIG_PLAYER help key
231
+
* added a gruvbox variation system theme
232
+
* updating docs and fixing broken links
233
+
218
234
2024-06-04 s-n-g
219
235
* version 0.9.3.9
220
236
* fixing a crash when adding a station to favorites
Two themes by \fBmechatour\fR (\fIhttps://github.com/mechatour\fR), from \fBhyprland_amber_gold\fR (\fIhttps://github.com/mechatour/hyprland_amber_gold\fR) and \fBhyprland_dotfiles\fR (\fI[https://github.com/mechatour/hyprland_dotfiles\fR).
<p>Pre 0.9.3 installations will use ~/.config/pyradio/data/recordings as the recording directory, by default.</p>
88
88
<p>After updating to v. 0.9.3 (and newer), <strong>PyRadio</strong> will move this directory to the user’s home folder and rename it to “<strong>pyradio-recordings</strong>”.</p>
89
89
<p>Then the user can change the folder’s location from <em>Config / General options / Recording dir</em>.</p>
90
+
<h2id="post-0.9.3.10-behavior">Post 0.9.3.10 behavior <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></span></h2>
91
+
<p>Up until <strong>v. 0.9.3.10, Ryradio</strong> would create the “<em>recording directory</em>” upon startup, no matter where it would be located, making it available for the recording and titles’ log function.</p>
92
+
<p>This eventually creates the following problem:</p>
93
+
<p>A user who never wants to use the recording or the titles’ log function, ends up with an empty directory in his home folder, which will be recreated every time <strong>PyRadio</strong> is executed (even if deleted before that), as described in <atarget="_blank" href="https://github.com/coderholic/pyradio/issues/253">issue No. 253</a>.</p>
94
+
<p>The solution is that <strong>PyRadio</strong> will remove the “<em>recording directory</em>” upon execution, if</p>
95
+
<oltype="1">
96
+
<li>the default location is used</li>
97
+
<li>the directory is empty</li>
98
+
</ol>
99
+
<p>As a consequence, both the recording and the titles’ log function will make sure the directory actually exists (and create it if it does not), before trying to save any data to it.</p>
Copy file name to clipboardExpand all lines: docs/rec-dir.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,3 +39,17 @@ After updating to v. 0.9.3 (and newer), **PyRadio** will move this directory to
39
39
40
40
Then the user can change the folder's location from *Config / General options / Recording dir*.
41
41
42
+
## Post 0.9.3.10 behavior
43
+
44
+
Up until **v. 0.9.3.10, Ryradio** would create the "*recording directory*" upon startup, no matter where it would be located, making it available for the recording and titles' log function.
45
+
46
+
This eventually creates the following problem:
47
+
48
+
A user who never wants to use the recording or the titles' log function, ends up with an empty directory in his home folder, which will be recreated every time **PyRadio** is executed (even if deleted before that), as described in [issue No. 253](https://github.com/coderholic/pyradio/issues/253).
49
+
50
+
The solution is that **PyRadio** will remove the "*recording directory*" upon execution, if
51
+
52
+
1. the default location is used
53
+
2. the directory is empty
54
+
55
+
As a consequence, both the recording and the titles' log function will make sure the directory actually exists (and create it if it does not), before trying to save any data to it.
Two themes by <atarget="_blank" href="https://github.com/edunfelt">edunfelt</a> inspired by the <atarget="_blank" href="https://github.com/base16-project">base16</a> project.</li>
109
112
<li><strong>dracula_by_Plyply99</strong><br/>
110
113
A theme based of the Dracula theme by <atarget="_blank" href="https://github.com/Plyply99">Plyply99</a>.</li>
111
-
<li><strong>gruvbox_dark_by_sng</strong> and <strong>gruvbox_light_by_sng</strong><br/>
112
-
Two themes based on the <atarget="_blank" href="https://github.com/morhetz/gruvbox">gruvbox</a> theme.</li>
114
+
<li><em>gruvbox_dark_by_farparticul</em>, <strong>gruvbox_dark_by_sng</strong> and <strong>gruvbox_light_by_sng</strong><br/>
115
+
Three themes based on the <atarget="_blank" href="https://github.com/morhetz/gruvbox">gruvbox</a> theme.</li>
113
116
<li><strong>hyprland_amber_gold</strong> and <strong>hyprland_dracula</strong><br/>
114
117
Two themes by <atarget="_blank" href="https://github.com/mechatour">mechatour</a>, from <atarget="_blank" href="https://github.com/mechatour/hyprland_amber_gold">hyprland_amber_gold</a> and <ahref="%5Bhttps://github.com/mechatour/hyprland_dotfiles">hyprland_dotfiles</a>.</li>
<p><strong>PyRadio</strong> will try to detect these terminals and disable themes (after displaying a relative message). Then the default theme will be used.</p>
181
184
<p>Some of the terminals that work ok, are: <em>gnome-terminal</em>, <em>mate-terminal</em>, <em>xfce4-terminal</em>, <em>lxterminal</em>, <em>terminator</em>, <em>termite</em>, <em>kitty</em>, <em>alacritty</em>, <em>sakura</em>, <em>roxterm</em>, <em>tilix</em>, <em>lilyterm</em>, <em>st</em>, <em>xst</em>, <em>rxvt</em>, <em>urxvt</em>, <em>uxterm</em>, <em>xterm</em>.</p>
182
185
<p>If you want to make <strong>PyRadio</strong> start in one of these terminal, just follow the instructions given at <ahref="#specifying-the-terminal-to-use">Desktop File: Specifying the terminal to use</a>.</p>
186
+
<h4id="workaround-for-not-supported-terminals">Workaround for not supported terminals</h4>
187
+
<p>Thanks to github user <atarget="_blank" href="https://github.com/troyvit">troyvit</a>, it is now possible to use <strong>PyRadio</strong> with full color support on most of the terminals that originally will not display colors correctly.</p>
188
+
<p>Following his <atarget="_blank" href="https://github.com/coderholic/pyradio/issues/254">report</a>, which proposes to execute <strong>PyRadio</strong> within a <atarget="_blank" href="https://github.com/tmux/tmux/wiki">tmux</a> session, a <atarget="_blank" href="https://gist.github.com/s-n-g/2f1ef5c764222d26e5bb0075b2adddb1">bash srciprt</a> has been written to accomplish the task: it is called “<strong>tmux_pyradio</strong>” and comes in the form of a github gist.</p>
189
+
<p>Using “<strong>tmux_pyradio</strong>” on can execute <strong>PyRadio</strong> in any terminal (it has been tested in all the terminals referenced above); one can even run a second <strong>PyRadio</strong> instance throught it. For more info, download it and execute:</p>
190
+
<pre>tmux_pyradio -h</pre>
191
+
<p>There is a catch though; if <strong>PyRadio</strong> terminates prematurely, the output will not be visible to the user, since <strong>tmux</strong> will also terminate and clear the screen on exit. In this case, just add a “<em>-d</em>” before a “<em>–</em>” (or combine it with the custom tmux session name). Yhis will add a <em>pause</em> before exiting <strong>tmux</strong>, so you can observe the output.</p>
183
192
<h3id="css-color-themes-restrictions">CSS color themes restrictions</h3>
184
193
<p>Using CSS colors imposes a couple of restrictions on the type of terminals <strong>PyRadio</strong> will be able to run:</p>
* [Workaround for not supported terminals](#workaround-for-not-supported-terminals)
8
9
*[CSS color themes restrictions](#css-color-themes-restrictions)
9
10
*[Secondary windows background](#secondary-windows-background)
10
11
*[Theme defined secondary windows color](#theme-defined-secondary-windows-color)
@@ -57,8 +58,8 @@ A clasic theme by [The OpenBSD Guy](https://github.com/OpenBSDGuy), originally c
57
58
Two themes by [edunfelt](https://github.com/edunfelt) inspired by the [base16](https://github.com/base16-project) project.
58
59
-**dracula_by_Plyply99**\
59
60
A theme based of the Dracula theme by [Plyply99](https://github.com/Plyply99).
60
-
-**gruvbox_dark_by_sng** and **gruvbox_light_by_sng**\
61
-
Two themes based on the [gruvbox](https://github.com/morhetz/gruvbox) theme.
61
+
-*gruvbox_dark_by_farparticul*, **gruvbox_dark_by_sng** and **gruvbox_light_by_sng**\
62
+
Three themes based on the [gruvbox](https://github.com/morhetz/gruvbox) theme.
62
63
-**hyprland_amber_gold** and **hyprland_dracula**\
63
64
Two themes by [mechatour](https://github.com/mechatour), from [hyprland_amber_gold](https://github.com/mechatour/hyprland_amber_gold) and [hyprland_dotfiles]([https://github.com/mechatour/hyprland_dotfiles).
64
65
-**minima_by_ben_chile**\
@@ -146,6 +147,18 @@ Some of the terminals that work ok, are: *gnome-terminal*, *mate-terminal*, *xfc
146
147
147
148
If you want to make **PyRadio** start in one of these terminal, just follow the instructions given at [Desktop File: Specifying the terminal to use](#specifying-the-terminal-to-use).
148
149
150
+
#### Workaround for not supported terminals
151
+
152
+
Thanks to github user [troyvit](https://github.com/troyvit), it is now possible to use **PyRadio** with full color support on most of the terminals that originally will not display colors correctly.
153
+
154
+
Following his [report](https://github.com/coderholic/pyradio/issues/254), which proposes to execute **PyRadio** within a [tmux](https://github.com/tmux/tmux/wiki) session, a [bash srciprt](https://gist.github.com/s-n-g/2f1ef5c764222d26e5bb0075b2adddb1) has been written to accomplish the task: it is called "**tmux_pyradio**" and comes in the form of a github gist.
155
+
156
+
Using "**tmux_pyradio**" on can execute **PyRadio** in any terminal (it has been tested in all the terminals referenced above); one can even run a second **PyRadio** instance throught it. For more info, download it and execute:
157
+
158
+
tmux_pyradio -h
159
+
160
+
There is a catch though; if **PyRadio** terminates prematurely, the output will not be visible to the user, since **tmux** will also terminate and clear the screen on exit. In this case, just add a "*-d*" before a "*--*" (or combine it with the custom tmux session name). Yhis will add a *pause* before exiting **tmux**, so you can observe the output.
161
+
149
162
### CSS color themes restrictions
150
163
151
164
Using CSS colors imposes a couple of restrictions on the type of terminals **PyRadio** will be able to run:
0 commit comments