TAB key only indents, not makes script block

Help
1

Please make this as an option! Nearly all notetaking non-md programs (OneNote, Roam, Evernote, …) use TAB for indents. Here using it entails getting ugly red text afterwards :frowning: It is so bad, real deal-breaker for me :frowning:
Ah! And please make this indents visible in preview mode! :slight_smile:

6 Likes
2

What preference have you set for indenting? Spaces or tabs? See Obsidian’s preferences.

3

Also, note that Obsidian uses markdown. Those other editors you mention are rich text editors. In Markdown, four spaces is a specific syntax that indicates that you’re writing a code block. This is standard across most markdown applications.

2 Likes
4

My setting is “Use tabs to indent”

5

I know it is markdown, but Roam somehow can use “tab” in indentation ok and still use other markdown features without problems, right?
I definitely won’t press space bar 4 times every time I want to make an indent, it is very uncomfortable for me. Obsidian already CAN use tab key for that. All I ask is to find a way NOT to make it code-block somehow. I believe it is possible. I’m sure a lot of people that come from other programs will have the same problem.
For all programmers out there make it just switchable option in Settings. Besides, there are other md ways to mark a code block, if I’m not mistaken :slight_smile:

3 Likes
6

Apparently, Typora can make indents, somehow. I think Typora uses a ​ in front of four spaces.

2 Likes
7

Roam might use markdown syntax in some ways, but it is not a markdown editor. Markdown editors edit plain text markdown-formatted files. Roam is a rich text outliner with a proprietary data structure.

This is not just semantics. The difference allows both apps to do different things.

Sure, but your primary complaint is therefore with Markdown conventions and standards, not with Obsidian.

You should submit a feature request for this. Though, because you are asking for Obsidian to adopt non-standard markdown, I’m not sure it’ll gain much traction. All you can do is try, though!

4 Likes
8

I am completely agree with topic starter. Even though code after tab is standard markdown syntax, people need a setting to redefine it to be non-standard, but comfortable.

9

Then as Ryan said above, you’ll need to open a feature request. And search first to make sure no one else did yet.

I’ll close this old thread now.