Option to make title uppercase/lowercase

[mhulse]

First of all, thanks for this plugin, it solves a very real pain point for me in Obsidian.

I had a question / feature request about how filenames are generated from the first line.

Right now, the plugin already replaces characters that are forbidden in filenames and can strip Markdown syntax, which is great. In many setups, though, it is also useful to have a full “slugified” filename, for example:

• My first note title! → my-first-note-title
• Crazy/characters & stuff → crazy-characters-stuff

In other words, something like:

• lowercased
• spaces turned into hyphens or underscores
• non-alphanumeric characters removed or normalized

My questions:

1. Is there a specific reason the plugin does not currently provide a fully slugified mode?
2. Would you be open to adding an option in settings to “slugify filenames” (with a simple, documented algorithm), while preserving the original first line as the note’s heading/alias?

The current behavior is already very useful, but for vaults that treat filenames as stable IDs, a slugified option would be extremely helpful.

Thank you for considering it, and thanks again for the work on this plugin.

[greetclammy]

Is there a specific reason the plugin does not currently provide a fully slugified mode?

Because I made this plugin for myself and have no use for a slugified mode ¯\_(ツ)_/¯

Interestingly, there was a very similar FR just a few days ago requesting snake case: #98, see my reply.

What would think about a simple option to make all titles uppercase/lowercase? This + a custom rule would achieve what you need.

[mhulse]

Ahhhh, nice! Custom rules will do what I want as well (I like the dashes instead of spaces).

… and this:

Seems to work pretty great!

A lowercase/uppercase option would be icing on the cake! 👍

Thank you!!!

Closing in favor of #98.

Thank you!

[greetclammy]

I see that you replaced all forbidden chars with an empty string. Instead, you could simply disable char replacement outright via the master toggle:

Was that not clear from the description? (I'm genuinely asking whether the wording is clear or not, not being passive aggressive!)

Renamed to scope the request to the option I would add. Reopening to keep track.

[greetclammy]

Added title case setting in 3.9.0.

[mhulse]

Ah, thank you!

Was that not clear from the description?

I might just be dense, but it was not fully clear to me 🤣

I think I first turned on the toggle because I was getting this output when escaping a square bracket (not sure if that is a bug?):

I asked GPT for help clarifying the wording, and its explanation matches how I understand the feature:

• Toggle off: forbidden characters are removed from the filename
• Toggle on: forbidden characters are handled using the table below

Based on that, it suggested the following copy tweaks …

Main section

Current:
Replace forbidden characters
Replace characters which are not allowed in filenames. Forbidden characters are stripped entirely if disabled.

Suggested:

Replace forbidden characters
When enabled, replace characters that are not allowed in filenames using the rules below. When disabled, these characters are removed from the filename

“All OSes” subsection

Current:
All OSes
Replace characters that are forbidden in Obsidian filenames on all OSes.

Suggested:

All OSes
Characters that Obsidian forbids in filenames on every operating system. Configure how each of these is handled when replacements are enabled

“Windows/Android” subsection

Current:
Windows/Android
Replace characters that are forbidden in Obsidian filenames on Windows and Android only.

Suggested:

Windows/Android
Characters that Obsidian forbids in filenames only on Windows and Android. When “Replace forbidden characters” is enabled, choose how each of these characters is handled

🤷 YMMV.

Thank you so much for all of your help and this awesome plugin!

[mhulse]

Note that if I don't escape the square bracket in my heading, Obsidian will try to link it:

[greetclammy]

Fixed bug and updated wording in 3.10.1.