Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to exclude entries from influx output that are already referred to in a page. #58

Open
FilSalustri opened this issue Jan 25, 2023 · 2 comments

Comments

@FilSalustri
Copy link

Influx currently shows all references (exceptions are based on path or filename only).

However, I think a useful use case is for influx to show only those references that are not already linked into the page.

For instance, say page A is mentioned in pages B, C, and D.
But page A also explicitly refers to page C somewhere.
It would be useful for influx to refer only to pages B and D, so as to bring to the user's/reader's attention those related pages that aren't already referenced.

I have been using the dataview query "list from [[]] and !outgoing([[]])" to achieve this behaviour.
But dataview doesn't show content, only filenames.

@jensmtg
Copy link
Owner

jensmtg commented Jan 25, 2023

Thanks for the support!
I can understand the use case for this.
Would you want to enforce this behaviour globally, or only in page A? Is the best place for a setting like this in Influx settings, or in the frontmatter of page A?

@FilSalustri
Copy link
Author

Hi!
Thanks for the quick response.
Personally, I think having this option relates to supporting how individuals think, which is probably uniform across an entire vault. (Gotta admit though that I'm basing this on my own thinking style, which may not reflect the broader audience.)

Put another way, I would certainly find it jarring to see all references on some pages and not on others - especially pages I haven't looked at in a while.

So I'd go with having the setting in the global influx settings for consistent presentation throughout a vault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants