One simple and reasonable answer is Ctrl-F. One of Minimak's stated goals is to not move common control key combinations if possible. That list includes:
Cut/Copy/Paste (X/C/V)
Select all (A)
Save (S)
Find (F)
Ctrl-D is the only left-handed home-position key combination which doesn't have a strong use like A, S and F (even though I happen to use it all the time to close Linux shells since it's the Unix end-of-file character).
That's a good reason, but it's not the primary driver though. The real reason is that the D position scores better on the keyboard layout analyzer (
http://patorjk.com/keyboard-layout-analyzer/) which is the metric on which I rely. The F position scores well also, just not as well. When you look more closely at the reasons why the D position scores better, I find them convincing.
If you put T in the F position, the one metric which scores better than the D position is reduction in finger movement distance (3.4%). That's an important metric, however you get worse balance of finger usage (15%) and worse same-finger repetition (3.9%). I find the latter two outweigh the former and the control-key argument seals the deal.
By way of explanation, finger movement distance pretty intuitive. It's the amount of moving around your fingers do on the keyboard and presumably the less you do of it, the better. The typical way to achieve less distance is to bring the most frequently-used letters, such as T, into the typing home position (ASDF JKL;) where your fingers rest and don't have to move at all to strike. So putting T in the F position is a win, it's just not a huge win over the D position since it's only a 3% reduction by comparison.
The comparison is between two different version of the Minimak four-key layout. E and K are swapped, so we can see the relative performance of the two T swaps, D and F, as they would perform in the Minimak setting. This is important because the relative performance depends on not only how those keys are situated but also how they relate to pretty much every other key on the layout.
The graph can be a bit tricky to read at first. It lays out the fingers of both hands on the x-axis. Above each finger are the scores for the both layouts. The darker one always on the left is when T is in the D position. The right is it in the F position.
As you can see, every other finger but the left middle is identical in movement distance, as you'd expect. The left middle finger is better (shorter) with T in the F position, the one on the right.
Finger usage is simply the number of times you used the finger while you type. It's like finger distance, except that distance doesn't include when you type a key in the home position since that's "at rest", while usage does. Each key strike counts the same for usage (1), while further keys add more distance. So they're related metrics, but they aren't the same and they both have useful information.
The desirable trait for finger usage isn't reduction, it's balance. You want to spread the load between your fingers rather than over- or under-utilize them. While the ideal distribution is debatable, I generally think it's useful to spread usage as evenly as you can (with an exception for the pinky).
In the picture you see that again, the two layouts are mostly identical. The difference is in the middle and index fingers of the left hand this time. Putting T in the F position (the lighter column over each finger) puts very high usage on the index finger. It's almost as much as the high mark of the right hand. The right hand is a problem as well, just one we can't address in a four-key layout such as this. In addition, the middle finger gets very little usage, tied with the other least-used, the left ring finger. It's arguable, but I'd call these over- and under-utilized respectively.
In contrast, the D position puts most of the usage on the left middle finger, and less on the index. However, the columns are closer in height to each other, which makes this more balanced. If you want to get numeric about it, you can compare the standard deviation of finger usage in each layout and see that the D position reduces deviation (is more balanced) by about 15% compared to the F position.
While finger distance, balance and other metrics are important, I have a particular distaste for same-finger repetition. You don't notice it if you aren't looking for it, but once you're aware of it, it becomes an annoyance. Same finger repetition is when you have to use the same finger twice in a row (for different keys), which slows you down because you can't be positioning a different finger to strike the following key while you are in the process of striking the first key. While it doesn't overshadow the other metrics, I put more weight on it than, say, movement distance.
Ignore the massive right-handed pinky column in the graph, it's skewed by it's responsibility for all of the punctuation and special keys on the right side of the keyboard, which the keyboard layout analyzer dutifully includes.
The rest of the graph maxes out (max being bad) on the right-hand index finger. That makes sense because it's responsible for six keys, second only to that pinky. Most are only responsible for three keys.
If you assign T to the F position (light blue), it's no worse than QWERTY since all you've done is change two keys on the same finger. Still, it shares the title of worst (not counting the pinky) with the right index.
If you put it in the D position however, the index repetition goes down quite a bit. Even if you add back in the increase for the middle finger, it is now less than both the right index as well as middle finger repetitions. That's a win. Overall repetition goes down 3.9%. Not earthshaking, but more than the decrease in finger distance (3.4%) already and as I said, I weight it more anyway.
Add to that the other arguments and that's what capped my decision.
I should mention that there are other important metrics I used in Minimak, such as hand alternation and balance of usage between hands. While you can't optimize for everything, it's interesting to look at them all and see how the layout you're using works. I'd recommend playing with the keyboard layout analyzer and really looking at all of the information it provides.
If you want to reproduce any of my tests, I used the full text of Alice in Wonderland, which seems to align well with the standard key frequencies for English which are referenced in many places. You can find it here:
https://code.google.com/p/nltk/source/browse/trunk/nltk_data/packages/corpora/gutenberg.zip As a shortcut, you can just use the kla's built-in sample of the first chapter of Alice which it makes easy to load, but the full corpus is better.
As for comparing the Minimak design decisions with those of Colemak and company, I wouldn't try to draw a lot of inferences between different layouts. They can't be looked at in isolated pieces, they only make sense in the whole. The utility of every key literally depends on the placement of every other key on the keyboard. Not only that, designers pick out different goals. If one prefers minimizing repetitions like Colemak does, you'll get different design decisions than Workman makes. Besides, if every other layout jumped off a bridge, should Minimak? ;)
Thanks for your question, it really did make me think and reinvestigate before I answered. I even found that the true reasons weren't the first ones I thought they'd be, so I learned something in the process.
Ted