- What do you like best about working there?
- What do you like least?
- How would you describe this company's culture? engineering culture?
- What causes the most conflict among employees here?
- What would you change if you could?
- How has the company changed in the past five years? How do you think it will change in the next five?
- How long has the longest serving team member been there?
- What's the average or median tenure?
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.
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill
) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
Wayland proponents make it seem like Wayland is "the successor" of Xorg, when in fact it is not. It is merely an incompatible alternative, and not even one that has (nor wants to have) feature parity (missing features). And unlike X11 (the X Window System), Wayland protocol designers actively avoid the concept of "windows" (making up incompr
More info on: https://cemkeylan.com/blog/20200828-wpa-add-script.html |
require 'webrick' | |
require 'open3' | |
server = WEBrick::HTTPServer.new :Port => 8000 | |
server.mount_proc('/') { |req, res| res.body = Open3.capture2(ARGV[0], :stdin_data=>req.body)[0] } | |
trap('INT') { server.shutdown } | |
server.start | |
# server: | |
# ruby webify-webrick.rb "wc -c" |
Disable all telemetry and privacy breaching settings on initial setup. (voice search, location services, etc...)
$hexified = "00,00,00,00,00,00,00,00,02,00,00,00,1d,00,3a,00,00,00,00,00".Split(',') | % { "0x$_"};
$kbLayout = 'HKLM:\System\CurrentControlSet\Control\Keyboard Layout';
Adapted from Arch wiki
The extrnal monitor has to be attached to eGPU, not laptop. Otherwise this won't work.
Install virt manager:
sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils
Various search databases and backends as alternatives to Elasticsearch.
- Sonic - github.com/valeriansaliou/sonic - lightweight & schema-less search backend
- Tantivy - github.com/quickwit-oss/tantivy - full-text search engine library inspired by Apache Lucene
- Toshi - github.com/toshi-search/Toshi - search engine built on top of Tantivy
- Bayard - github.com/mosuka/bayard - search engine built on top of Tantivy
- Meilisearch - github.com/meilisearch/meilisearch - fast and full-featured search engine
#compdef maddr magrep mbnc mcom mdeliver mdirs mexport mflag mflow mfwd mgenmid mhdr minc mless mlist mmime mmkdir mpick mrep mscan msed mseq mshow msort mthread | |
_mblaze_colon_separated_headers() { | |
_message 'headers (colon separated)' | |
} | |
_mblaze_message() { | |
local ret=1 expl tmp curmsg | |
local -a mseq mseqnums mshortcuts mshortcutdescrs | |
setopt localoptions extendedglob |