branch: externals/mpdired
commit 2ac5d2f759a57170721f834d491e57a5cc227e88
Author: Manuel Giraud <man...@ledu-giraud.fr>
Commit: Manuel Giraud <man...@ledu-giraud.fr>
more text
---
mpdired.el | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/mpdired.el b/mpdired.el
index e12a7e45ab..c2d16f92d8 100644
--- a/mpdired.el
+++ b/mpdired.el
@@ -31,6 +31,14 @@
;; In those view, most of the interactions are mimic after Dired mode
;; with marks and action on them. For example, in the queue view, you
;; could flag songs for removal with `d' and then execute with `x'.
+;;
+;; MPDired connects to a MPD server using two customs: `mpdired-host'
+;; and `mpdired-port'. Once connected, the handle to the server is
+;; saved in a buffer local variable into the MPDired buffer. From now
+;; on, the customs are just used by global MPDired commands to connect
+;; to the user defined server. All commands used inside a MPDired
+;; buffer will connect to the buffer local server. This way, you can
+;; manage more than one MPD server with multiple MPDired buffers.
;;; Philosophy:
;;
@@ -46,10 +54,10 @@
;; into directories and with meaningful filenames, I prefer to use
;; this interface rather then to rely on files' tags.
;;
-;; If your music collection consists of just a set of not well named
-;; files into one big directory and that you rely on tags such as
-;; Genre, Album, Artist to find your way through it then, maybe,
-;; MPDired is not the right client for you.
+;; If your music collection consists of just a set of not very well
+;; named files into one big directory and that you rely on tags such
+;; as "Genre", "Album", "Artist" to find your way through it then,
+;; maybe, MPDired is not the right client for you.
;;; Bugs & Funs:
;;
