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 have no heading or use a "body text" for heading #54

Open
sotakal opened this issue Nov 2, 2022 · 8 comments
Open

Option to have no heading or use a "body text" for heading #54

sotakal opened this issue Nov 2, 2022 · 8 comments
Labels
feature request New feature or request
Milestone

Comments

@sotakal
Copy link

sotakal commented Nov 2, 2022

I've had my output format set to
- Edited [[link]]
and I've liked this minimalist format. The new version of the plugin forces me to use a heading, and this is cumbersome. I rarely use headings in my notes because I find them huge and don't want to tinker with themes, CSS or styling.

If headings really are mandatory, I'd prefer to only a heading formatted as bold body text that says Modified today:, without being forced to use an actual h1/h2/etc. heading. Unfortunately when I tried to specify my heading as
**Modified today:**
the plugin ignored my setting.

@franciskafieh
Copy link
Owner

The reason I force the user to use headings is because they are easily cached by obsidian. I may add the option to choose something else once i figure out how caching "blocks" (as obsidian calls them) works. There are a few more features I have to finish before releasing 2.1, so I'll have to put this on the backburner.

As a temporary workaround, you can try copying and pasting an invisible character (https://www.editpad.org/tool/invisible-character) into the settings. Make a small heading (h3, h4, whatever level you want) with just the invisible character as the name. This should appear invisible in reading/live preview mode. Give it a try and let me know :)

@sotakal
Copy link
Author

sotakal commented Nov 3, 2022

Okay, understand the limitations but this still feels cumbersome.

Maybe one more piece of feedback: I expected that if I change the "Heading" setting, when there is no appropriate section in the daily note, the "default" value will be created using my configuration. But I was wrong, and every time the plugin does not detect the specified Heading, it re-creates the default "(h1) Modified Today" and reverts my configuration back to the default value.

@franciskafieh
Copy link
Owner

That's unintentional. I'll work on getting this fixed, thank you. gonna open a new issue for that.

@franciskafieh
Copy link
Owner

Just wanted to mention that (because this feature requires a lot of change to implement) anyone else who would like it should heart the original post. I just want to see how urgent and necessary of a feature this would be.

Currently back to working on the 2.1 rewrite, and the easiest solution for now is to have a "primary" / h1 header that can have content replaced under it.

N.B. an empty header (a space character) should still work, as it would simply appear as an empty line in the file (under live preview mode)

@franciskafieh
Copy link
Owner

franciskafieh commented Feb 15, 2023

Although making the primary heading optional would be hard, making the "modified" h3 optional would be easy ^^

Ideally, a primary heading wouldn't be necessary, but I still need to look into how to use cache to pinpoint this "block", and how to get it to work with #71

@franciskafieh
Copy link
Owner

Some functionality was added in release 2.1.2. Now the plugin does not create the "modified" heading unless the separate created or deleted options are toggled on. Now there is no heading redundancy in this manner

@jfgrtsn
Copy link

jfgrtsn commented Feb 16, 2023

Now the plugin does not create the "modified" heading unless the separate created or deleted options are toggled on. Now there is no heading redundancy in this manner

This worked great for me—thanks!

@franciskafieh
Copy link
Owner

Feel free to look at #90

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

No branches or pull requests

3 participants