Option to exclude document from global search



I think it might be really helpful if possible to have a right click option on each document to hide it from global search results.

The obvious use case for this is to hide archived materials in all their forms from global search.

However there are many others also - For example I use red, orange, yellow to denote urgency globally but I have some very large projects which have their own internal colour system and which I would like not to show up on my general urgency search - I have noticed similar stories from a few people on the forum.

Thank you!


Search for is:checklist but exclude certain documents?
Customize Search Option (Omit Folder From Global Search)
Allow search operators to work at the document level
Disable search on a document
Search operators to exclude certain documents/folders?

Yep that would be very Handy especially for Template / Reference Documents


Mmm yes another good example


Exactly !!
Exclude a document or folder


Do you think global search in a folder can be a workaround for this (it’s not implemented yet, I’m just talking about the idea).

Marking the document as hidden adds some hidden information, and search is so critical. What if some day you forget you hid some document and panic that you can’t find it? That’s pretty bad and in my opinion not worth it if there are other alternatives to solve this problem.


Mmm, I see your point. ‘Search folder’ could potentially replace it but there are issues I see with this. Mainly, this search we are talking about would need to be accessible by a keyboard shortcut just like global search is now. I’m not sure this would be possible because you might have folders within folders, so if you had a ‘search current folder’ shortcut (e.g. Shift and enter) then how would dynalist know which level of folder you were trying to search?

This means for this feature we wouldn’t be able to click a tag then press ctrl and enter like now, we would have to open up the file manager, presumably right click on the correct folder and run a search, which is far more clumsy / slow. Perhaps if you could set a keyboard shortcut for each folder in the folder options, but this seems tricky too …

Personally I don’t see the hidden folder thing as a major issue. The document is still there in your file manager. Also you could add a statement at the bottom of any global search that ‘There is hidden content pertaining to this search, click here to see it’, or something like that? Alternately you could make the fact that the document is hidden quite salient in the file manager itself by e.g. making it red


No, it’s more like a special syntax for global search. For example: -folder:[folder-unique-name] search term.

I see your point. They do both have pros and cons.

One point that I think it’s important when discussing this is to know that some users will not read what we write or understand what the red icons mean. Even now many people don’t understand that the blue icon means it’s shared. Worst part is that when something is missing and can’t find, writing in to complain is the best case. In many other cases they just leave Dynalist and writing it off as an app that loses data.

Not saying this will definitely happen but it’s a factor when considering changing any existing behavior. Maybe there’s a better way that meets both needs…


Ahhh yes, a search term which excludes specific folders would work perfectly fine for me at least as I can always turn this into a keyboard shortcut with a macro program.


Hmm what about the case you said you want to click a tag and then press Ctrl+Enter right away?


Actually even that can be done - after clicking the tag the cursor is in the search box so the macro can just spit out the correct text to exclude the ‘hidden’ folders and press enter (I could even repurpose ctrl and enter). However this does make me realise that this might be more tricky for people who don’t use macros - but no more so than other searches I suppose …


The standard for excluding a document, folder, tag, or anything else from a search is generally through exclusion in the search:

coffee -notebook:recipes

The only time an exclusion setting is used is with something like Indexed Search in Windows, for example.

If a search with an exclusion in the term is very popular, then you can bookmark the search, make it a hyperlink in a “searches” notebook, etc., just like you would in Evernote or so.

ps: an added benefit of the exclusion is that we would right away have a folder search where we can say the inverse:

coffee folder:recipes


This would be nice.

I could have 2 documents then

One with deprecated workflows (removed from global search)

One with current notes & workflows


Note that one big problem is that folders and documents do not have a unique name (aka slug) right now, so it might be hard to say which ones you want to exclude.

The only unique id of a folder of document is that 24-character-long id, which is definitely not going to be used in the search syntax.


Ah yes that’s a pretty fatal problem at this stage! :confused:


Yeah, the most straight-forward way seems to be letting you set a unique name for the folders you’re interested in excluding. If you don’t want to exclude it, you don’t have to set a unique name for it.

Not sure if that’d work well… Maybe there’s a better way.


Maybe by expanding the search. As we’re also looking at things like search with parenthesis.

coffee (folder:thisone AND notebook:recipes)


coffee (-folder:thisone AND -notebook:recipes)


Maybe forcing folder’s name to be unique could be another way…

Existing duplicate folders’ names would be automatically renamed to, say, folderName, folderName-1 etc.


Wouldn’t make logical sense but on the parent level.

In any file system you can’t have 2 identically named parent folders – but within each of those 2 parent folders you can have folders/documents with the same name because they’re not living in the same namespace.

So folder1/coffee and folder2/coffee should be able to exist – which means we would be back to square 1.

My 2 cents is that this is how it works everywhere. If you do a search in Windows and you exclude something, it too doesn’t bother:


From the looks of it it just excludes all files whose name contains “coffee”?


Yes. It would work with full-text search too but this is to illustrate the principle that, in general, search in file systems would work precisely how it would in Dynalist:

  • items can have identical names
  • including or excluding a name will in/exclude that item in search
  • no reliance on unique folder/file ID’s