Should a file have a file ID?

How To
1

I have a question about the expectations that we have on Roam and whether something I found is a bug or a feature.

I started removing the file level ID. I figured that if I have a first level node (one asterisk), I don’t need a file level node too.

However, I do use :filetags:

The issue I have discovered is that filetags are not propagated by roam when there is no file ID.

So my question is: is the file level ID of a roam file a requirement or is it optional?

I am not asking about what it does now, but what do you think it should do.

Depending on that is whether I’ll create a patch for upstream.

2

It should be optional, if I understand the design principle of V2. My reading of what Jethro was saying is he wanted to treat files and headings in a uniform way. Org-ID would let Org-roam code achieve this. The org file section before the first heading should be treated as if it was level zero heading.

The Tag Inheritance section of Org manual says this below:

You can also set tags that all entries in a file should inherit just as if these tags were defined in a hypothetical level zero that surrounds the entire file.

So, you set variables org-use-tag-inheritance and org-tags-exclude-from-inheritance according to your needs, right?

1 Like
3

A big thank you. I had forgotten about org-tags-exclude-from-inheritance. The tag I was using for testing was in this variable.

Tags do work as we expect.

Thank you again, I really appreciate the time you took to reply to my email.

1 Like