I usually have an h1 that is the same as the file name so no I will not keep this setting on. Iāll also use a snippet to make the file info header less prominent.
I use the Filename Heading Sync plugin, so every one of my notes has a H1 that matches the file name. This led to exactly the situation in @TRUās first screenshot for every note until I figured out how to disable the inline title.
Now I also toggled Appearance ā Advanced ā Show Tab Title Bar to hide the path, so now Iām back to only seeing the file name/heading 1 as I like it: Once vertically on the spine of the stacked tab, and once at the top of the file name.
I really like the feature, but it weirds me out that I canāt hit the up arrow to move up and edit it. Like, I expect it to be part of the document, but itās not. So for now, Iām writing headings manually.
I also have a few note filenames that are shorter than the h1 I write, so sometimes letting them be different is useful.
Itās the first thing I turned off. Canāt see the point of it, as I can already see what the file is called.
I like to see my pages (planner pages, specifically) the way Iāve designed them, with a certain amount of info showing on the screen before I have to scroll. The inline title is a very large, superfluous distraction to that.
Iām the OP of the question in the thread @Craig mentions because I was too in doubt what to do.
Having read the replies (in my question thread) I thought, I will remove my inline H1ās and use the āShow inline titleā function but after having read all the comments of deactivating it here Iām in doubt again . How to build a sustainable PKM?
I have a h1 named ā(Body)ā which is automatically generated in almost all of my note. So that i can always embed [[note-name#(Body)]] if i needs for almost all notes.
However, if I want to export the note to a PDF, Iād like to have a H1 named as same as the note title.
So, generally speaking, iām not a big fan of this feature. However, i cannot deny the fact I somehow create my note in the same way as the feature does.
A reliable, transportable, readable Markdown file should be fully contained within itself. The filename is irrelevant. If there is a title for the file, it needs to be inside the file as an H1 element.
This brings up one of the issues I have been trying to resolve for a very long time. My problem stems from the need for very long file names. Sorry for the discussion divergence, but this feels like a meaningful place to bring it up.
Unfortunately the problem with very long file names is that there is a character limit. But, unlike any other feature in Obsidian, the actual text within links can actually be updated when that file is. Without having to rely on embeds or fiddling with alternative link display text via | characters, the ability to simply rename a note and have the actual link text within notes be automatically updated is a very unique and powerful ability. But, it is heavily limited by note name length limits.
Especially now that Obsidian has this option to show note names inline as H1 headings, I see potential for some functionality that outsmarts the character limit and lets you compose a few hefty sentences right in that H1 heading and have it auto update all links to the note regardless of the actual note name. Like @AlanG said āThe filename is irrelevant.ā Of course, he said this in a different context. Anyways, after writing all this out, I decided I will simply create a feature request so as to avoid further distracting from this discussion. Note name length unlimited
Edit: Below @alain1405 kindly suggests using aliases. However, aliases are simply used to help find the link within the auto-suggester, and they automatically add the | character so that the link is displayed as alias. The issue with goes back to my whole goal of being able to update the note name and have the change update all instances of links to that note. Aliases do not update when they are changed. There are multiple discussions about this in other threads. Iām right there with you. This would be an elegant solution if it updated. Anyways, hereās a link to one topic that clearly describes this: Automatically update links when aliases are renamed. I appreciate the response, I will mention it over in my new request as a possible workaround that would rely on another feature request being implemented first.
For now I am keeping the inline H1 titles on. I like their ability to line wrap and their bold appearance. Since text size and interface zoom are separate values, it can be useful to sometimes zoom out the interface until tabs are quite tiny, knowing that the inline titles can stay large and readable as well as being adjustable with the ease of a ctrl roll. This allows for some heavy multitasking (or at least the ability to have many notes open and have their titles relatively quickly and easily read).
I am sorry that my previous reply is quite an anomaly in the conversation here. I hope it doesnāt distract. I feel even worse that, in my excitement, I totally forgot to actually respond to the very thoughtful question that @Karjala posed. Thanks for making this topic! I very much appreciate it!
Iām in the ānot sureā category. I havenāt included an H1 in all my notes (especially older content), but like an earlier respondent, portability guides my recent thinking to include it now. However if I do, then I need to go back and add the H1 to older notes and then turn off the setting. Sighā¦
But one thing I am sure about is the ability to hide the inline title on a per-note basis ā can anyone suggest a way to do it, using a plugin or CSS snippet? The use case here is that I have a handful of notes that I use in sidebars, and screen real estate is essential.
I think the inline note title is a good idea and the way it is implemented is very good in my opinion.
I donāt share the opinion of several authors in this thread that this wastes valuable screen space. I would rather like to remind that white space is important to improve the readability of a text.
In my opinion, my notes not only look good with the inline note title but are also easy to read. Also, the use of a level 1 heading is now limited to only very long notes where a title seems appropriate to improve understanding of the content.
I only quickly skimmed through this post and I am not sure why you might need very long file names @I-d-as but have you tried the āAliasā field in the frontmatter?
It can be used to link a file by using one or multiple aliases and perhaps those donāt have a limited length.
It works for me.
File with a short name and an alias:
---
tags: []
aliases: [ Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industrys standard dummy text ever since the 1500s when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries but also the leap into electronic typesetting remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum ]
---