Content pfp
Content
@
https://warpcast.com/~/channel/meme
0 reply
0 recast
0 reaction

TheThriller ๐ŸŽฉ Adam Miller pfp
TheThriller ๐ŸŽฉ Adam Miller
@thethriller
๐Ÿ“Œ Just made this meme for fellow Obsidian users like @trigs:
1 reply
0 recast
4 reactions

rathermercurial.eth pfp
rathermercurial.eth
@rathermercurial.eth
I feel like this is a feature, not a bug. Obsidian is already super lenient on page titles (too much so, IMO. Just use a title ffs)... It needs to enforce some basic norms to ensure files are portable across contexts and file systems.
1 reply
0 recast
1 reaction

TheThriller ๐ŸŽฉ Adam Miller pfp
TheThriller ๐ŸŽฉ Adam Miller
@thethriller
I don't want to ask my software to be "lenient" on me. Let me do what I want and have been doing for decades with other software!
2 replies
0 recast
1 reaction

blaynem pfp
blaynem
@drilkmops
The problem is that itโ€™s just a file system under the hood. It saves everything in plain text for you even. The whole point is they want you to keep your data, never be vendor locked. So they canโ€™t โ€œbe lenientโ€ because itโ€™s fundamentally an OS problem
2 replies
0 recast
2 reactions

rathermercurial.eth pfp
rathermercurial.eth
@rathermercurial.eth
You totally can though! Obsidian is markdown, so the correct place for arbitrary file names is the page title ("# <your title here>"), or the metadata ("title: <your title here>"). They both support slashes, colons and other punctuation. The first line is the *filename*, not the title. So it needs to conform to your various systems' filename conventions. Notice that your filesystem won't let you add marks like slashes or colons to filenames, either. If you don't like seeing the filename on your page, you can disable "Show in line title" in Settings -> Appearance -> Interface
0 reply
0 recast
1 reaction