As the community points out, there are many alternative approaches to using tags.
I’m unfamiliar with Roam, and I’m having a hard time grasping @Shane comments.
CamelCase, hyphen’s, and underscores are practical approaches. While tried and true in programming, their aesthetic and readability is off-putting when reviewing notes. Just my opinion. Furthermore, as Obsidian does not yet have a mobile app, many of the mobile alternatives the team recommends, at least on iOS, do not implement hyphens or underscores in tags. And camelCase is transformed into lower case causing clarity issues.
Overhauling the tag system for one guy is an insane expectation on my part. I get that. One of Obsidian’s most endearing features has been it’s flexibility. Accommodating multiple words in tags would expand the app’s ability to meet different workflows and styles.
@justindirose mentions Bear’s approach of sandwiching multiple words between hashtags. Bear has established itself as a capable writing app. Perhaps the Obsidian team will consider this approach? It seems to be a good trade-off for users that don’t find multi-word tags so strange.
This is somewhat related to my request for extracting tags from YAML front matter. The unsaid assumption there was that multiword tags should be supported.
I’m not sure that having spaces in tags is a good idea. I currently have tags on one line in a YAML header in each file, separated by spaces. So tags with spaces would mess that up.
Hyphens between the words works and using multiple tags is more flexible: #minecraft-building-inspiration #minecraft, #building, #inspiration
In my mind, hyphens already solve this use-case quite well and, I think, better than spaces would.
On another note, I have created another feature request that would greatly enhance the use of multi-word tags, regardless of how the words are separated: Fuzzy matching in tag entry autocompletion
Please backup your vault before trying any of this. Batch regex replacements can irreparably mess up your notes.
If you’re willing to accept the compromise suggested by @ryanjamurphy, and able to perform a regex search & replace on your exported files (using VS Code, for example), the following expressions will replace #multi word tag# with #multi-word-tag.
I think it’s quite natural to have the possibility to put spaces in tag names. Imagine when you take notes on topics which have very long names (like in academia): some have abbreviations, but not always (and having only abbreviations reduces clarity; especially when several names have the same abbreviation, which is common). I find adding hyphens less readable. Also in the same context, typical bibliography management softwares (like Zotero) allow for tags with spaces, so it would be useful for matching when people already have a collection with those softwares.
A possibility would be to enforce keeping space by putting quotes around the tag. Then for people who don’t care (or don’t like) spaces in tags, this would be transparent. This also gives a very clear signal that there are spaces in tags and I guess that it would not complicate too much the analysis.
Somewhere I have seen #[multi word tag] syntax which would be more reliable IMHO. And aligned with markdown style to delimit text spans e.g. for purpose of linking.
#tag This sentence seems to start by tag unless you read it till the end when you realize that acording to some suggestions actually whole sentence is a tag#
Current solution/workaround:
If you need to use spaces for some reason (not hyphens, CamelCase, … suggested in posts above), Then Enclose multi-word key string in double brackets, i.e. create wiki link [[multi word tag]] instead of #multi-word-tag.
I agree with @nixsee here, I think hyphens or underscores are fine once you get accustomed to thinking that way. Usually better to stick to standards whenever possible. I’m starting to heavily use the YAML frontmatter for tagging, and I see the #[some tag] syntax breaking things there.
Just wanted to drop in and lend some more support here, I’m considering switching to Obsidian from Bear but the lack of multiple word tags is a really big deal for me for many of the reasons listed and it might be enough to keep me using Bear.
This may seem like an outlier issue but the number of other productivity applications that support spaces in tags ought to lend a little credence. Off the top of my head here are a few apps and systems that do: Apple’s file system tagging across multiple platforms, DEVONthink, OmniFocus, Hypothes.is, Readwise, 1Password, Drafts, MindNode, Evernote, Keep It, Ulysses, Flickr, Medium and Raindrop.io.
Bear is probably the best example since it also has inline tags within the text of the note, I can’t comment on Justin’s workflow but here is a couple of examples of how I use them:
Here’s an example of my tags navigator, it may be worth mentioning that Bear organizes things exclusively by tags, there’s are no folders/notebooks/groups so flexible tagging with spaces and nesting is especially important.
In my Obsidian testing some of this type of structure is going into folder names and Obsidian seems to manage them just fine; I see little reason the tagging system would need to be any less flexible than file linking but I am new here and still learning my way around the application.
I’d just like to add that coming from TiddlyWiki, we had tags with spaces, as in TW, tags where just other “tiddlers” (obsidian notes).
I think it makes sense to separate out the clear concept: “Tags are just other files”, from the implementation “how do we denote tags with spaces?” Just because we dont yet have a good answer to the second doesnt mean the first one is also bad.
I think of tagging notes with the names of other notes. Anything allowed in the title of a note, should also be allowed in a tag. Otherwise, what is a tag? How is it separate from a note? What if a tag has the same name as a note?
All of these confusions are avoided if we just follow “tags are just other notes”.
Please let’s be reasonable and start allowing tags with spaces in them.
Every single other tool allows it - Evernote, Bear, TIddlyWInk, you name it. Only Obsidian stubbornly refuses to support it. And no - dashes, underscores and other hacks are just that, hacks. They are ugly and unnatural. If you like them go ahead and use them, but don’t force everyone else to think the way you do. We are all different, and judging by the number of hits when one searches for “space” and “tags” there is enough demand for it.
This continues to be the largest friction point to the extent that I’m wondering how difficult it would be to reimplement tags as a community plugin. It’s really a shame tags are arbitrarily limited to not accept a space character like so many other systems and apps do.
Hi! I am new here and trying to move from Bear to Obsidian. Have you found a way to convert Bear’s tags with spaces to Obsidians with ‘-’ symbol instead of space ’ '? Thanks!
I also very much support the suggestion to allow spaces in tags. Yes, quite a few “workarounds” have been named. But for, let us say, “general people” who do not like to adapt their thinking to a tool, but, instead, believe that the tool is there for them, to support their way of thinking, and especially in the light of that Obsidian otherwise allows for so much flexibility, to allow this option would be great - and, I would say, natural. It is quite a difference for someone who loves language to see something like, for example, “Feeling great” and then “Feeling-great” or “Feeling/great”) etc. CamelCase might help a bit, but it is still far from the natural way of language which we all have been accustomed to since birth (“Feeling great”). Of course, one can have two separate tags, one “feeling” and one “great”, but, perhaps, one has that besides the tag “Feeling great” - and, also, when searching for that combination then, it requires a little bit more work. (Evernote has no problem with that.)
Please, be flexible here, too!
Joined the Forum outright just to add my two coppers for multi-word tagging. All my tags from Evernote, Simplenote, and Notion had multi-word tags and now I’ve got a bunch of out-of-context tags that are all but useless, like “about,” “the,” and "in.
I tag like I work for Tumblr. Whole run-on sentences.