Hi,
I tried applying tags to files in Dolphin, and as I did, I noticed I could add nested ones. However, the GUI is kind of buggy. For example, at first, I added Fonts/Feeling/Sincere, and it worked. Then I tried adding Fonts/Serif/Old Style, but as I started writing “Serif”, the “Feeling” tag disappeared. When I tried to force it to work, it started behaving very weirdly, eg, while exploring tags it showed me a parent folder of a tagged folder in a parent of the nested tag. I am not really sure if the fact that you can create a nested tag is an intended feature, or something that just happened because of GUI integration, or something like that?
Over all the tags are a great thing, but if I can’t nest them, they really lose a lot of value. I would love to have separate tags for images, fonts, music, and text files, and I wouldn’t want them all lumped together.
I came across the same issue, where nested tags only worked properly if it was a single level deep. So, using your set-up as an example, it was possible to have multiple tags nested under “Font”, but anything deeper would somehow conflict, even if both tags would’ve been under “Font/Serif”.
Nested tags themselves should not be an issue, though, since using setfattr -n user.xdg.tags --value="Fonts/Feeling/Sincere,Fonts/Serif/Old Style" <PATH TO FILE> works without issue, and even creates the appropriate tag folders in tags:. I’ve also noticed, that this odd conflict happens (at least personally) only after two characters are typed for the new sub-tag’s name. With that in mind, the workaround I’ve had to resort to for now, is making any new sub-tags only one character long, and then going into the tags folder and renaming it.
So, in short, you could either use setfattr for each file, or temporarily make any new sub-tags one character long and then renaming them by going into tags:. Regardless, this is definitely a bug, so if you haven’t already (and if there isn’t an existing one), I recommend reporting it.
