[emms-help] Playlist buffer read-only-isms in Emms2

[Yoni Rabkin Katzenell]

Now that we have a real live buffer for a playlist which the user sees
(albeit through the eyes of a playlist-mode) the question of the
read-only-ness of that buffer arises.

The core (rightly) makes no decision as to the read state of the buffer
since as far as the core is concerned the user need never see the
playlist buffer/s.

The decision is what kind of restrictions we put on the user in the
playlist-mode. Do we make it act like Gnus or Dired? Those modes
explicitly set the read-only-ness of actions using local `let'
statements for the read-only flag (as far as I understand how they work).

A number of the input keys have already been taken up by the interface
(RET, "n", "p" etc.) so being able to enter free text at any point no
longer makes sense.

I'm not excluding the ability to enter free text in future, indeed I'm
writing the playlist-mode without the pretence that every line is a
track. But text entry will have to have a special command to enter free
text mode. I think that being able to enter nice labels and titles in
your playlist mode can be a nice thing.

Other than that, what do people think? 

Jorgen, even though you frequently absolve yourself from such UI laden
matters your opinion would be appreciated.

-- 
"Cut your own wood and it will warm you twice"