Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.
You've got two main options:
# If you use bash, this technique isn't really zsh specific. Adapt as needed. | |
source ~/keychain-env.sh | |
# AWS configuration example, after doing: | |
# $ keychain-env-add AWS_ACCESS_KEY_ID | |
# and | |
# $ keychain-env-add AWS_SECRET_ACCESS_KEY | |
export AWS_ACCESS_KEY_ID=$(keychain-env-get AWS_ACCESS_KEY_ID); | |
export AWS_SECRET_ACCESS_KEY=$(keychain-env-get AWS_SECRET_ACCESS_KEY); |
Here is the best setup (I think so :D) for K-series Keychron keyboards on Linux.
Note: many newer Keychron keyboards use QMK as firmware and most tips here do not apply to them. Maybe the ones related to Bluetooth can be useful, but everything related to Apple's keyboard module (hid_apple
) on Linux, won't work. As far as I know, all QMK-based boards use the hid_generic
module instead. Examples of QMK-based boards are: Q, Q-Pro, V, K-Pro, etc.
Most of these commands have been tested on Ubuntu 20.04 and should also work on most Debian-based distributions. If a command happens not to work for you, take a look in the comment section.
Older Keychron keyboards (those not based on QMK) use the hid_apple
driver on Linux, even in the Windows/Android mode, both in Bluetooth and Wired modes.
As configured in my dotfiles.
start new:
tmux
start new with session name: