समीर सिंह Sameer Singh <[email protected]> writes:
I dug into the diffs a bit. It all looks good. I'd like to play
with it some
and see how it goes. I also need to refresh my memory of the code
so I can
remember if there are any corner cases.
Erica
On Fri, Feb 20, 2026 at 5:29 PM Erica Qi <[email protected]>
wrote:
Oh dear, yes you have found a mess.
I've been working on a better formatting system for the
browser.
If you are grouping by artist I believe that might be correct.
It is just the display.
Yes, I also meant to write that when grouping by artists this is
correct but forgot to type it out.
When adding to the playlist adding the track should only add
one.
What if someone intentionally wants to add a track multiple
times to
the playlist?
Can we do something like if the user mass adds tracks to their
playlist such as when pressing RET on
an artist's name, we deduplicate the playlist, but if they want
to add
a single track we add it as it is?
There could be a field format for artist which concatenates
them.
That would give one track, but if the order is different
between different tracks the grouping wouldn't work so well.
I am doing something similar for the track name display, see the
screenshot attached.
I have also attached all of the work I have done till now so you
may
take a look at it.
- In emms-info-native.el defcustomed a list of info fields
which may
have multiple values, if these are ever encountered while
parsing,
then append the values into a list.
- Added an emms-track-format-field func which is a wrapper
over
emms-track-get, this func checks if a value is a list,
if true then concatenate the value into a string using a
separator
which is user configurable.
- Added support for it in emms-browser and emms-filter.
- we update our metadata from mpv, but mpv stores multivalue
fields
as strings delimited with a semicolon. "VAL1;VAL2",
so handling that.
Please review it too.
Thank You.
[2. image/png; artist-view.png]...
[3. application/octet-stream; diff]...
