| // ==UserScript== | |
| // @name Smooth Scrolling | |
| // @description Smoothly scrolls the page when a button is held | |
| // @version 1.1.2 | |
| // @author sllypper | |
| // @homepage https://greasyfork.org/en/users/55535-sllypper | |
| // @namespace https://greasyfork.org/en/users/55535-sllypper | |
| // @match *://*/* | |
| // @grant none | |
| // @todo make keybinds easily configurable |
| ;; nano-emacs.el --- NANO Emacs (minimal version) -*- lexical-binding: t -*- | |
| ;; Copyright (c) 2025 Nicolas P. Rougier | |
| ;; Released under the GNU General Public License 3.0 | |
| ;; Author: Nicolas P. Rougier <[email protected]> | |
| ;; URL: https://github.com/rougier/nano-emacs | |
| ;; This is NANO Emacs in 256 lines, without any dependency | |
| ;; Usage (command line): emacs -Q -l nano.el -[light|dark] |
(updated versions of this document, plus more, live here)
This will show you how to get Guix running on WSL2.
We're going to go as "minimal" as possible, without starting off one of the readily available WSL2 distros.
Parts of this guide should help with understanding how to set up any custom distro on WSL, not just Guix.
Disclaimer: I'm a Guix nOOb! (hence going through the trouble of installing it on WSL2)
| " huge thanks to Keshav13142’s https://gist.github.com/Keshav13142 | |
| " (make sure to remove default Obsidian shortcuts if any conflicts happen) | |
| " sometimes we use exmap to make aliases for long commands .. cuz of a bug in | |
| " CodeMirror {it cannot handle many arguements} | |
| " j AND k navigate visual lines rather than logical ones {both n&v modes} | |
| nmap j gj | |
| nmap k gk | |
| vmap j gj |
| """""""""""""""""""""" | |
| " Leader | |
| """""""""""""""""""""" | |
| " let mapleader=, | |
| " can't set leaders in Obsidian vim, so the key just has to be used consistently. | |
| " However, it needs to be unmapped, to not trigger default behavior: https://github.com/esm7/obsidian-vimrc-support#some-help-with-binding-space-chords-doom-and-spacemacs-fans | |
| unmap , | |
| " map ; to : in normal mode, so that I don’t rely on the shift key | |
| " nmap ; : |
Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.
The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.
Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.
