CTRL-C Quit insert mode, go back to Normal mode. Do not check for
abbreviations. Does not trigger the |InsertLeave| autocommand
event.
^[ however is. Personally, I use ^[ to avoid reaching to actual ESC and ^C to exit any weird states entered by misclicks.They just aren't that useful for many people, and so the muscle memory never forms. (They are also really far from home row on some keyboards)
I'd be surprised if the majority of touch-typists on Windows don't have muscle-memory for Alt-F4, at a minimum.
> They are also really far from home row on some keyboards
Fair enough; helps that I exclusively use and prefer laptop keyboards, to the point of having a USB ThinkPad keyboard/mouse combo on my desk.
That and option-shift-volume buttons to move volume up/down quarter ticks which is super helpful with earbuds that get way too loud otherwise.
Really sad to see them go, as well as the esc button.
I'm still on a 2008 macbook, and it was just kicked off from new OS updates (just updated to El Capitan) and the "next" device I look at and like is like 2013 model or something.
The small resolution, no battery life, slow processor are only minor annoyances to me. It is fast enough for me, I do iOS development/browsing/movies.
reload: cmd+r
jump to browser bar: cmd+l
I have no idea what Esc does, I never use it.
I've also gotten worse at the number row now that few games use more than the first 3-4 for quick slots or weapons.
1. Questionable utility. Sure, there's an icon for 'copy' and 'paste', but I cannot imagine it being easier for anyone to hunt along a non tactile touch surface located in an awkward position to hit that icon rather than just using Ctrl + C (or the mouse, which you've just made your selection with). That's a shortcut almost everyone knows.
2. Poor/Non-existent third party software support. Basically works for IE and Windows Explorer and that's it.
3. Software that drives the screen is poorly made and crashes occasionally.
4. The strip is a 2 bit/pixel B&W screen that is hard to read and is not backlit.
Function-key shennanigans reminds me of an apple laptop from years and years ago, well before the unibodies came out, where the function keys were hard up against the screen - hit a function key, and you bang your fingers against the screen (well, most of the time).
Every personal computing device is either a) a rough prototype for some Apple product or b) a shameless knockoff of one. The Carbon touchstrip was the former.
The former is visible without looking down at your hands the latter is easy to press. I believe this combines the worst of both worlds.
I don't know how to address your last sentence it sounds clever but it means virtually nothing. If apple does it first its a knockoff if someone else does it first its a rough prototype of something apple will ultimately do better. Heads I win tails you lose?
I don't know about the boundary between keys thing, but for tactile feedback: Force Touch?
"The "context bar" seems like a huge win for people who look at the keyboard (who do comprise a huge fraction of the market), and a huge loss for touch-typists."
I don't think so. I touch-type, but I hardly ever touch-type the function bar. Doubly so on a Mac, because the function bar is, by default, used for brightness and media controls.
I've (briefly) used a device with Force Touch. It doesn't come anywhere close to replacing the depress-and-release of a physical key. It's better than nothing, barely. But I don't want to use a tablet with an on-screen keyboard as my primary productivity device; I want to use a laptop with a physical keyboard.
> I don't think so. I touch-type, but I hardly ever touch-type the function bar. Doubly so on a Mac, because the function bar is, by default, used for brightness and media controls.
That seems like a self-fulfilling prophecy. I also know many Mac users who don't know why anyone would need a right mouse button, let alone a middle mouse button. If you design your interface to not need it, and you know people will never run third-party applications that do, then sure.
Macs have effectively had right mouse buttons for around a decade. Two finger click on the trackpad, or a literal right click on an Apple mouse (there just isn't a physically separate right button).
The right click thing is astounding to me... Everybody uses right click. Mac or not.
If you've trained yourself to only need one button, then yes, you only need one button. But look how well that's worked out on the iPhone, with a heavily-overloaded one button, with hard-to-discover functionality.
#!/bin/bash
synclient TapButton1=1
synclient TapButton2=3
synclient TapButton3=2
This gives a minimally usable touchpad, with two-finger-tap right-click, side-scroll and tap-select.I am still scratching my head at the absence of right-click and the key layout. I have no actual Mac OS experience to compare to, but Imagine they've done it all well when it's used as intended. Otherwise, it's working great and the build quality is solid. I am already fantasizing about Linux on a newer model, maybe with a PC mouse or external touchpad though.
On, and control next to the a,and caps lock something that requires two people to turn keys at the same time from separate bunkers.
It's also a bit odd to generalise this to European keyboards as some layouts vary wildly on the continent based on the lack of or added letters to their alphabet. Also, UK is in Europe so would count as a European layout.
F2 - rename
F4 - jump to the address bar (explorer, elsewhere)
F5 - refresh in the browser, execute/debug in various places
F9 to F12 - Visual Studio debugging and navigation
F11 - full-screen toggle (browser)
F8 - Step into
Shift F8 - Step over
F9 - inspect symbol
F10 - execute to cursor
I remap function keys for global purposes like window tiling with Divvy. Seems like context-sensitivity will delete what I consider to be key functionality.
The "context bar" seems like a huge win for people who look at the keyboard (who do comprise a huge fraction of the market), and a huge loss for touch-typists.
That said, I also don't use that many function keys, and I've slowly started remapping the keys I care about to other key combinations. In practice, I care about a few sets of function keys, most notably F11/F12 (commonly used for fullscreen, which I've now remapped to Super-F), and F4 (Alt-F4 to close applications, for which I've now trained my fingers to use Ctrl-W or Ctrl-Q and report bugs on the occasional application that doesn't accept those).