bjeanes
Joined 16 years ago
Joined 16 years ago
Further, because I don't type in QWERTY, I noticed that _some_ shortcuts seem correctly mapped in my layout, but others are not. The Option+N shortcut for a new note just starts the "˜" combining character (expecting a following character like "n" to form "ñ") when using the "n" key in my layout. However it works if I use the physical "n" key (which is my "k").
I feel like that explanation is pretty poor, but yeah basically some shortcuts seem bound to the physical key location whereas others seem bound to the mapped key. I wonder if they are declared differently?
Interesting. I suspect something like this will always be subjective, but I find the opposite to be true. *bold* and _italics_ make the most sense to me and is always what I wished Markdown did.
Probably, this is because I was familiar with Textile[1] before I used Markdown, and this is what it does.
Today, Slack also uses this convention instead of the Markdown convention (though I believe it _used_ to use the latter).
I'm not sure if "horrible" but I did experiment with getting it to refactor some code. I also gave it code with a bug and asked it to fix it (I described the bug), which it was able to do. I didn't test very complicated scenarios though. In the bug fix case, it was code to wrap, indent, and prefix a block of text.
Granted, that was more about mobile devices but it still stuck with me. Effortless and safe concurrency would tip the scales to having hundreds of low power cores instead of a dozen high powered cores. I want that world, esp for mobile devices and laptops.
So good.