3 ms·

I have almost entirely switched to using an editor which supports real-time preview for Markdown editing. There is a plugin for my editor (VSCode - but I'm sure

by JoBrad 6y ago

I have almost entirely switched to using an editor which supports real-time preview for Markdown editing. There is a plugin for my editor (VSCode - but I'm sure that something similar exists for most other editors that support plugins) which has keyboard shortcuts for marking content as a given type (e.g. Alt+c will mark selected text as inline code). Perhaps this would address the problem you're talking about?

cptskippy 6y ago
> Perhaps this would address the problem you're talking about? He's talking about physical keyboard layout, nothing you suggested will help with that. https://en.wikipedia.org/wiki/Keyboard_layout https://en.wikipedia.org/wiki/Keyboard_layout
- JoBrad 6y ago
  I understand that. If you don't have a # readily available, but your editor allows you mark a line as Heading 1 by pressing Ctrl+1, then it does in fact address their problem.
tomcooks 6y ago
Surely there are workarounds, one could also just switch to an US layout (an instantaneously become a faster, less tired developer, since the same problem happens with commonly used symbols such as / [ ] etc. which are easy to type on anglophone keyboards). It's probably a unsolvable problem unless: - everyone adapts to using common, more difficult to type, characters such as " or ? (but then how does the system differentiate between common figures of speech and formatting?) - everyone switches to US/ENG layouts, but we already had enough US-centric systems in the past and I don't know how many wouldn't see this change as a personal/national attack - the creation of a Fn keys standard, but that means all hardware producers would have to comply to eat (yeah) and mobile typing would become problematic, along with extra strain from having to press the "fn" modifier - your solution, which i find elegant, but adopted OS-wise instead of just inside an editor plugin. but then what if ctrl-1 is my shortcut for switching desktops, or closing windows? Maybe the only cure is to accept defeat, create localized versions and create translators - after all this seems how languages work.

by JoBrad 6y ago

cptskippy 6y ago

> Perhaps this would address the problem you're talking about? He's talking about physical keyboard layout, nothing you suggested will help with that. https://en.wikipedia.org/wiki/Keyboard_layout https://en.wikipedia.org/wiki/Keyboard_layout

JoBrad 6y ago
I understand that. If you don't have a # readily available, but your editor allows you mark a line as Heading 1 by pressing Ctrl+1, then it does in fact address their problem.

tomcooks 6y ago

Surely there are workarounds, one could also just switch to an US layout (an instantaneously become a faster, less tired developer, since the same problem happens with commonly used symbols such as / [ ] etc. which are easy to type on anglophone keyboards). It's probably a unsolvable problem unless: - everyone adapts to using common, more difficult to type, characters such as " or ? (but then how does the system differentiate between common figures of speech and formatting?) - everyone switches to US/ENG layouts, but we already had enough US-centric systems in the past and I don't know how many wouldn't see this change as a personal/national attack - the creation of a Fn keys standard, but that means all hardware producers would have to comply to eat (yeah) and mobile typing would become problematic, along with extra strain from having to press the "fn" modifier - your solution, which i find elegant, but adopted OS-wise instead of just inside an editor plugin. but then what if ctrl-1 is my shortcut for switching desktops, or closing windows? Maybe the only cure is to accept defeat, create localized versions and create translators - after all this seems how languages work.