summaryrefslogtreecommitdiffstats
path: root/audio/pianobar/README
diff options
context:
space:
mode:
Diffstat (limited to 'audio/pianobar/README')
-rw-r--r--audio/pianobar/README18
1 files changed, 10 insertions, 8 deletions
diff --git a/audio/pianobar/README b/audio/pianobar/README
index 8127637653..bc77db48e7 100644
--- a/audio/pianobar/README
+++ b/audio/pianobar/README
@@ -1,11 +1,11 @@
pianobar is a console client for the personalized web radio pandora
(http://www.pandora.com).
-- Play and manage (create, add more music, delete, rename, ...) your stations
+- Play and manage (create, add music, delete, rename, ...) your stations
- Rate played songs and let pandora explain why they have been selected
- Show upcoming songs/song history
- Configure keybindings and text output
-- Remote control and eventcmd interface (send tracks to last.fm, for example)
+- Remote control and eventcmd interface (send tracks to last.fm, e.g.)
- Proxy support for listeners outside the USA
Included with this SlackBuild is a helper script called pianobarctl that
@@ -14,12 +14,13 @@ this a FIFO must first be created by the user:
mkfifo ~/.config/pianobar/ctl
-Please see man pianobar and pianobarctl --help for more information. The
-documentation also includes a few example scripts you can use with pianobar.
+Please see man pianobar and pianobarctl --help for more information.
+The documentation also includes a few example scripts you can use with
+pianobar.
NOTE:
-If you are getting an error stating your TLS fingerpring is incorrect you need
-to configure pianobar so that it has the correct one.
+If you are getting an error stating your TLS fingerprint is incorrect,
+you need to configure pianobar so that it has the correct one.
You can execute the following script to get a new TLS fingerprint:
@@ -30,5 +31,6 @@ Then open your pianobar configuration in your user's home directory
tls_fingerprint = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-If for some reason you receive an error about the TLS fingerprint again, just
-execute tls_fingerprint.sh again and ammend your user's configuration file.
+If for some reason you receive an error about the TLS fingerprint
+again, just execute tls_fingerprint.sh again and ammend your user's
+configuration file.