Replies: 1 comment 2 replies
-
This is related to the discussion in #1399. If you use the custom category extensively, you can solve most of this by just prefixing your tags. I'm planning a revamp of the tag/reference system down the line, but I haven't decided what would be the best approach yet. I'll certainly keep this in mind. You could perhaps also post this as a feature request. Your text is pretty clear, so feel free to just copy/paste it. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There's the
custom
tag. However seeing that you can rename its label, wouldn't it be better to have the custom tag follow the label of whatever it's renamed to? People could have multiple custom tags, each with their own name. This could cause confusion for them if I had the custom tagsfoo
andbar
, they would both be consideredcustom
tags by NovelWriter, being cause of confusion.What I would like to see:
Create new custom tag, and name it "foo", from that moment onward I would address it with
@foo:
in my documents/notes.Then I'd create another custum tag, and name it "bar", from that moment I would address it as
@bar:
in my documents/notes.They would show up in the project tree as "foo" and "bar", and so they need to be able to be referenced as such.
I hope I am clear enough. Sorry if I'm unclear about what I mean.
Beta Was this translation helpful? Give feedback.
All reactions