101–110 of 331 posts
I use similar abbreviations in code editor, for example: r0 -> return false rn -> return null t -> this puf -> public function You can easily find the opportunities for saving typing by analyzing existing code and most used words there.
This is a very clever idea. However, I realize that I would never want to use something like this that would change over time. E.g. if I ran it every 6 months and last year "db" produced "debug", while this year it produces "database". Because talk about messing up my muscle memory and habits. And the language I write changes very much over time. So I'd actually be much more interested in a "universal" version of thi…
I wish there was a way to just repurpose existing operating system support for CJK language IME for English.
Could you elaborate? I'm aware of CJK input methods, but it's not immediately clear how/why you could repurpose them for English. Not to mention there are several types.
You can create a custom user dictionary in any IME, mapping the abbreviations to one or more full words or phrases, either in bulk beforehand, or one by one while you use the system.
During typing, pressing the space bar brings up a list with the substitutes corresponding to the preceding string. You can select with the up/down arrows and insert by pressing space again.
In practice, most of the time you can convert by pressing space twice in quick succession, because either you have a single candidate, or because the default selection, the top candidate is automatically set to your last, or most frequent selection.
If there's no match, you can add a new abbreviation to your dictionary.
You can turn on/off the system by pressing CTRL-space, or some other key combo.
Earlier quoted context omitted.
If that's something you do then obviously this isn't for you. I personally haven't typed on someone else's computer in at least 13 years. Since whenever I got my first laptop.
You've never had to help someone do something on their own computer that required typing something in?
This is a very clever idea. However, I realize that I would never want to use something like this that would change over time. E.g. if I ran it every 6 months and last year "db" produced "debug", while this year it produces "database". Because talk about messing up my muscle memory and habits. And the language I write changes very much over time. So I'd actually be much more interested in a "universal" version of thi…
In the current setup there are too many collisions.
I use similar abbreviations in code editor, for example: r0 -> return false rn -> return null t -> this puf -> public function You can easily find the opportunities for saving typing by analyzing existing code and most used words there.
What editor are you using to do this? I assume it's vim or emacs.
This is what I thought while I was learning Vim too, but now I honestly prefer Vim keybindings everywhere. So maybe this is not too bad. I would definitely try out if one can also build a vimtutor like version for this usecase.
It is a lot harder than I thought it would be. To find aliases that dont misfire too often and provide enough value. Give that I daily communicate in several languages that adds even more trouble.
I have now split it by application. Different aliases for different applications. I still have misfires. Mostly I have found I need delinators.