Skip to content

The migration script handles filetags in an unexpected manner #1642

@ndw

Description

@ndw

Description

Advice for tags, for example from the org manual shows them as being delimited by colons. I'm not sure what Org Roam V2 uses, but migration appears to have turned all the colons into underscores.

Steps to Reproduce

I had a bunch of V1 files that used tags with colons:

#+FILETAGS :Saxonica:DeclarativeAmsterdam:

they have become single tags with underscores in them:

#+filetags: _Saxonica_DeclarativeAmsterdam_

That's obviously not right at all. It's not a huge problem to fix them, but I thought I should report it.

Expected Results

I expected the tags to be preserved, should they still be using colons as delimiters?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions