Re: how to handle multi value tags?

=E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9 S=
ameer Singh <[email protected]> writes:

I dug into the diffs a bit. It all looks good. I'd like to play=20
with it some
and see how it goes.  I also need to refresh my memory of the code=20
so I can
remember if there are any corner cases.

Erica

> On Fri, Feb 20, 2026 at 5:29=E2=80=AFPM Erica Qi <[email protected]>=
=20
> wrote:
>>
>> Oh dear, yes you have found a mess.
>> I've been working on a better formatting system for the=20
>> 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=20
>> one.
>
> What if someone intentionally wants to add a track multiple=20
> 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=20
> to add
> a single track we add it as it is?
>
>> There could be a field format for artist which concatenates=20
>> them.
>> That would give one track, but if the order is different=20
>> 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=20
> may
> take a look at it.
>   - In emms-info-native.el defcustomed a list of info fields=20
>   which may
> have multiple values, if these are ever encountered while=20
> parsing,
>     then append the values into a list.
>   - Added an emms-track-format-field func which is a wrapper=20
>   over
> emms-track-get, this func checks if a value is a list,
>     if true then concatenate the value into a string using a=20
>     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=20
>   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]...