Cmus and .m3u files

[Storm Dragon]

Hi,
Does cmus support .m3us if not, I would like to make a feature
request :)
Thanks
Storm

[gt]

Post by Storm Dragon
Hi,
Does cmus support .m3us if not, I would like to make a feature
request :)

It does support m3u. It's even documented in the man page.

[Storm Dragon]

Hi,
Somehow I completely missed this in the man page. The real problem
though, and what caused me to send a completely pointless email
requesting a feature that was already in place was a mistyped rm
command. It's really hard to find a use an m3u if you have deleted it
before attempting to use it :)
Thanks
Storm
--
Vinux Publicity Coordinator: http://www.vinuxproject.org/
Registered Linux user number 508465: https://linuxcounter.net/user/508465.html
My blog, Thoughts of a Dragon: http://www.stormdragon.us/
My last.fm profile: http://www.last.fm/user/stormdragon2976
"Shine glorious we ride, we stare into the blackened sky. Save the last command, the virtue blinding."
DragonForce - The Last Journey Home

Post by gt

Post by Storm Dragon
Hi,
Does cmus support .m3us if not, I would like to make a feature
request :)

It does support m3u. It's even documented in the man page.

[yawfle]

[Gregory Petrosyan]

Well, since the subject line fits something that's been on my mind, but didn't really feel strongly enough about to start a disscussion, maybe I'll just toss it in here and make the thread possibly useful anyway... ;)
I was thinking that it might be nice, when viewing the contents of a playlist file in the file browser screen, if the flow of mc-style navigation could be maintained by adding a ".." (or something different to distinguish from an actual directory listing) at the top of the list so that hitting "Home, Enter" takes you back to the parent directory. I always seem to do this before remembering that it doesn't work, and it's not immediately obvious that you need to hit Backspace if you're not familiar with the program yet. Does anyone else think this makes sense?

I've posted a patch that implements this behaviour; the patch is
pushed to the pu branch of the git repo. Thanks for the suggestion!

       Gregory

[yawfle]

One other thing that I've encountered in the file browser view is the fact that when hitting the "y" or "a" or "e" keys (to add to playlist, library, or queu respectively) on the "../" entry in the directory listing, the entire contents of the parent directory are recursively added to the appropriate list. This is "correct" behavior, but:

- it's easy to do accidentally
- the results can be extreme and difficult to revert
- it doesn't really have a practical use in most situations

so I wonder if anyone has a good reason why it might not be a good idea to disable this functionality, at least by default? Or at maybe prompt first? It's just a thought...

[a.l.e]

hi

Post by yawfle
- it's easy to do accidentally
- the results can be extreme and difficult to revert
- it doesn't really have a practical use in most situations
so I wonder if anyone has a good reason why it might not be a good idea to disable this functionality, at least by default? Or at maybe prompt first? It's just a thought...

happened to me a couple of time... and i agree: it could and should be
disabled.

ciao
a.l.e

[yawfle]

[ale rimoldi]

hi yawfle

Post by a.l.e
happened to me a couple of time... and i agree: it could and
should be disabled.

I've implemented this, posted the patch to the mailing list (but it
appears to be a bit lost), and pushed it to the pu branch — hope it
is working fine :-)

Just now had a chance to build and try out the pu branch, and the
improvements to the browser view work well, the "../" in playlists is
especially nice.
After purposely attempting to add the "../" in directory views to
library, playlist, etc a few times and seeing the helpful message in
the status bar, it occurred to me that maybe the best behavior for
this case would be to simply enter the parent directory, with focus
on the previous directory, just as if the user had hit "Enter"? It
seems like this would be benign (and fairly intuitive as to what had
happened) in both the case of hitting it accidentally, as well as if
the user actually wanted to add the parent directory, since they
would be one step closer to doing so... :)
Anybody else think this would make sense?

not in my case...

in my case, the few times that it happened, it was because i was typing
in the wrong terminal or when i typed the wrong command.

i wouldn't ever press a or l (or whatever is the key to add to the
library) instead of hitting the enter key...

but i can live with cmus going to the parent directory, since it's just
a small effect for a wrong hit key :-)

and, really, i don't see a reason why somebody would want to add the
parent directory...

just my --.02

a.l.e

[Jason Woofenden]

Post by a.l.e
happened to me a couple of time... and i agree: it could and should be
disabled.

I've implemented this, posted the patch to the mailing list (but it
appears to be a bit lost), and pushed it to the pu branch — hope it is
working fine :-)

Just now had a chance to build and try out the pu branch, and the improvements to the browser view work well, the "../" in playlists is especially nice.
After purposely attempting to add the "../" in directory views to library, playlist, etc a few times and seeing the helpful message in the status bar, it occurred to me that maybe the best behavior for this case would be to simply enter the parent directory, with focus on the previous directory, just as if the user had hit "Enter"? It seems like this would be benign (and fairly intuitive as to what had happened) in both the case of hitting it accidentally, as well as if the user actually wanted to add the parent directory, since they would be one step closer to doing so... :)
Anybody else think this would make sense?

No. I think guessing what the user meant to press is a bad idea.
There is no way to guess accurately, and even when we do, many
users will me mad that we didn't do what they said.

Also, in this case changing directories would be very distracting,
and many people wouldn't notice the error message.

- Jason