Yep, I understand. I was just sharing what I think it should do.
1 Like
I’ve added it to the current version, you can expect it in the next update.
This we are considering. We’re a bit concerned about a hotkey that changes behaviour depending on context, but we’re discussing it internally.
2 Likes
Yes, I completely agree. That’s also exactly what I would intuitively expect.
2 Likes
Sorry. I got completely buried with life and work stuff for a while.
So from what I can tell, the TLDR is that myself, Noleli, and krssno are roughly aligned on how we expect Cmd+N to behave, correct? That being: New headless doc when outside of a project context, new doc in the project folder when in a project context.
And the team is considering a change to the default Cmd+N behaviour but remains skeptical to having Cmd+N behaviour be different depending on context, correct?
FWIW, for my use case, I will NEVER have a need to have Cmd+N behave in the “project” type context. I don’t want Bear. I want Panda. The direction Lettera seems to be taking is something in between, which, as an avid Panda user for many years, I truly lament. I’ve been using Panda as my daily driver for drafting emails, for opening Obsidian notes in a WAY nicer editor, for ALL my writing work, the list goes on and on. I’ve even written a Markdown-derived scripting language and parser for my game engine, and do all my dialogue and scripting for my game in Panda. The second Panda stops working, my entire productivity life will grind to a halt 
For now, while all this stuff gets figured out, I continue to use Panda as my daily driver. I really hope that a good solution can be found before the current Panda beta expires and we’re all forced to switch to Lettera (or something else).
For now I can really only plead to the developers to consider the folks who have been using and advocating for Panda all this time, and take our use cases into account.
If you truly want to prioritise making a project-based Markdown notes app above the use case of Lettera being a document-based Markdown editor, I really hope you can at least give us some kind of toggle to disable the project-centric workflow. Or find some other elegant solution that allows us to use the app in a document-centric way.
Thank you! 
I agree. I just want a simple editor that I can double click a markdown file, edit it in wysiwyg (never seeing any markdown code) and closing it. I don’t want the editor to clutter up with “project” stuff because I use Finder for that.
You can open markdown files in obsidian in the default app in the right click menu, when I do this it opens it on it’s own without the folder sidebar.
I acknowledge this is might be different from other editors, but isn’t the simple solution that you adjust your workflow to use CMD+Shift+N?
The dev has shared his thoughts and supplied a very valid alternative?