CTRL + A
: Move the cursor to the beginning of the line
CTRL + E
: Move the cursor to the end of the line
OPTION + Left Arrow
: Move the cursor one word backward
OPTION + Right arrow
: Move the cursor one word forward
Left Arrow
: Move the cursor one character backward
Right Arrow
: Move the cursor one character forward
Discover gists
import Quill from 'quill'; | |
import {TaskerFigure} from './TaskerFigure'; | |
import Parchment from 'parchment'; | |
export class FigureOptions { | |
quill: Quill; | |
figure; | |
overlay; | |
linkRange; |
// ==UserScript== | |
// @name 哔站直播全裸2233娘 | |
// @description 哔站直播间的2233娘挂件替换为全裸版本 | |
// @description:zh-TW 嗶站直播間的2233娘掛件替換為全裸版本 | |
// @namespace https://github.com/journey-ad | |
// @author journey-ad | |
// @include *://live.bilibili.com/* | |
// @require https://cdn.jsdelivr.net/jquery/1.12.4/jquery.min.js |
I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve
, dotnet watch run
, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.
That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull
on my "windows" project folder, and do a production build there
// ==UserScript== | |
// @name Jigidi Magic Stripes | |
// @namespace me.danq.com.jigidi.magicstripes | |
// @match https://www.jigidi.com/solve/* | |
// @grant GM_getValue | |
// @grant GM_setValue | |
// @version 1.1 | |
// @author Dan Q <https://danq.me> | |
// @description 23/03/2023, 14:32:30 | |
// ==/UserScript== |
There is a bug in Safari when using border-radius
and overflow: hidden
. Especially when applying transform
to a child.
In this case, overflow: hidden
does not always work. The child ignores the border radius and overflows.
It's a very old bug. And sadly it seems that it will never be fixed. Anyway, we can't wait for it.
There are some workaround. We need to place the element with the overflow attribute into a stacking context.
I've tested the following workarounds on the latest version of iOS (14.4).
You can choose what you want. But you should search the web for the particular attribute. (e.g. will-change
should be rarely used. See docs)
Use this on the element with overflow: hidden
and border-radius
:
#!/bin/sh | |
# Install Zsh + Oh My Zsh + Powerlevel10k theme (macOS & Linux) | |
# run: sh -c "$(curl -fsSL "$(echo "$(curl -s "https://api.github.com/gists/254e58bd87009963b3f58405d75cbe6c")" | grep -o '"raw_url": *"[^"]*"' | cut -d'"' -f4)")" | |
# Remove installations + configurations | |
rm -f ~/.p10k.zsh | |
rm -rf -- ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k | |
sh ~/.oh-my-zsh/tools/uninstall.sh -y | |
sudo chsh -s $(which bash) |
import axios, { AxiosError } from "axios"; | |
import { GetServerSidePropsContext } from "next"; | |
import Router from "next/router"; | |
const isServer = () => { | |
return typeof window === "undefined"; | |
} | |
let accessToken = ""; | |
let context = <GetServerSidePropsContext>{}; |