Another Squeekboard version is out! This one will be big to most users, because a mistake prevented the two previous versions from reaching Amber. Introducing 1.14.0.
Hasnāt come through for me (amber). Iām still on 1.11.1 and, yes, I have done apt update and apt upgrade, in addition to letting the PureOS Store do its thing.
Iām not sure but I think when @dcz writes that the new version is āreleasedā that means the source code for the new version is officially available at https://source.puri.sm/Librem5/squeekboard but then there is a delay of a maybe two or three days (?) until it reaches the amber (and/or byzantium) repos.
Not sure exactly what is happening during those few days that it seems to take, I guess some automated building and testing is going on but I donāt really know. If anyone knows then please explain, I would like to understand more about how the release process works and why it is setup like that.
Iām not sure exactly the reasoning behind the delay, but I think itās a period for testers to raise any red flags before itās pushed out to everyone.
Just an idea for now. Iāll try to learn more (when I have time), if itās possible and how to do it.
Iām using the command line frequently, and the terminal view lacks some important keys for that, like Tab, ā-ā, ā.ā, or ā/ā. You have to do a lot of view switches to get those.
So Iām thinking to replace the thin arrows keys, and also the current Shift, like this:
make the current Shift into a Tab key
change the current thin keys row (Ctrl, Alt, Up, Down, Left, Right) to be: Ctrl, Alt, ā-ā, ā.ā, ā/ā, Shift (edited: the order of ā.ā)
Also I would like for the Ctrl and Alt keys not to stay sticky after Iām pressing a ānormalā key and finishing the combination.
Iāve noticed some of the same issues. I have also pined for a more readily accessible | key.
However I use Up Arrow a heap, so I wouldnāt want to sacrifice that (or, to a lesser extent, the other arrow keys).
I guess I would make two comments:
no one keyboard layout will suit everyone
it is an open platform, so if you need a different keyboard, you can make one.
Like you though, I have no idea how to do that, how easy or difficult it would be, whether there is any documentation to help with that.
I think the terminal emulator should come up by default with a keyboard that is optimised for shell use (rather than a more generic one for use with GUI applications).
I donāt quite understand the logic of Shift not being able to be sticky (but now at least it does have the sticky version i.e. Caps Lock) and Ctrl being sticky. I canāt quite see the use of having Ctrl sticky i.e. when you would key lots of Ctrl characters in a row. Maybe an editor where most things are done with Ctrl characters. It usually just catches me out typing rubbish because I left Ctrl on.
In the meantime I offer three workarounds, all of which work, if you have a lot of typing to do:
attach a USB keyboard
pair a Bluetooth keyboard
SSH in from another computer that has a more comprehensive keyboard
The third option has limitations due to the process context e.g. GUI applications probably wonāt work (and I am also SSHing in as a user other than purism so settings donāt really work either).
If you need to press Up more than one time, then I think itās ok to switch views. You can also use Ctrl-R to search back in the history for previous commands and avoid repeating pressing Up.