Given these preferences within the extension:
Be sure that IBus Preferences (ibus-setup) around Emoji won't intercept/override <Super>period
Remove the bindings that you don't prefer/need over the Emoji Copy picker and enjoy 👋
| //@ts-check | |
| // ⚠️ UPDATED https://gist.github.com/WebReflection/291357aa6bbbd97d54a971ce5f5aae4e?permalink_comment_id=5952616#gistcomment-5952616 | |
| //@ts-ignore | |
| import custom from 'https://cdn.jsdelivr.net/npm/custom-function/esm/factory.js'; | |
| /** @typedef {'marker' | 'start' | 'end'} MarkerType */ | |
| if (!('MARKER_NODE' in Node)) { |
| let p = 0; | |
| const fetchp = (url, ..._) => new Promise((resolve, reject) => { | |
| const src = new URL(url); | |
| const callback = `__json${p++}`.replace('-', '_'); | |
| src.searchParams.set('callback', callback); | |
| document.head.appendChild(Object.assign( | |
| document.createElement('script'), | |
| { async: true, onerror: reject, src } | |
| )); | |
| globalThis[callback] = value => { |
I am recently re-branding my libraries as µ (micro), refactoring these when necessary, dropping IE < 11 support, improving the logic where possible, or providing a better, more robust, or faster, API.
In few words, on the right there is the modern version of libraries I've used for the last ~5 years in production or for side projects, and I suggest anyone having one of the earlier dependencies, to have a look at their modern, micro, counterpart.
All sizes are minified, brotli compressed, and representing these two files, when possible:
| /** | |
| * so here the thing ... you go in your github page | |
| * as example I go here: https://github.com/WebReflection | |
| * you open your console | |
| * you copy and paste this shit | |
| * then you write and execute in the console | |
| * write("Hi There!"); | |
| * NOTE: Pixel Font from a 2006 project of mine :-) http://devpro.it/pixelfont/ | |
| */ | |
| function write(text, color, start) { |
There are various shenanigans around the Proxy API, including issues with Array.isArray and Object.ownKeys so that this gits purpose is to describe all the undocummented caveats to help anyone dealing with all possibilities this half-doomed API offers.
apply and construct traps won't work with it. If the object somehow wants to represent an array without being one, it's impossible to survive Array.isArray brand check (it will be false) and with ownKeys the target needs to have a non configurable length property or it will also fails once reachedCreate a $HOME/.config/systemd/user/speakers.service file with the following content:
[Unit]
Description=Force Speakers Audio
After=pulseaudio.service
[Service]
Type=oneshot
ExecStart=/usr/bin/pactl set-card-profile alsa_card.pci-0000_bd_00.6 "output:analog-stereo"I've found it quite "disturbing" in 2026 there are APIs that wouldn't use Promise and accept a last argument as function to retrieve data, see: https://doc.qt.io/qt-6/qtwebchannel-javascript.html#interacting-with-qobjects
Here an easy way to workaround that, where equality of the method is preserved and things would look more modern or easier to reason about.
const { apply } = Reflect;
const { create } = Object;
const wm = new WeakMap;OK, the amount of gotchas with unigine-superposition 1.1 benchmark is too damn high, which is a pity because it's awesome!!!
chmod a+x qt-opensource-linux-x64-5.9.0.run./qt-opensource-linux-x64-5.9.0.runpakku -S --needed unigine-superposition and I suggest you do that after a sudo mount -o remount,size=20G,noatime /tmp. If it ends with an error, just sudo pacman -U the-big-tar-file-in-tmpThis gist comes after my comment left in the original post.
The pattern is great but the way it was presented not too great: