Skip to content

Instantly share code, notes, and snippets.

View craigmac's full-sized avatar
hey! :octocat:

C.D. MacEachern craigmac

hey! :octocat:
  • Kingston, Ontario, Canada
View GitHub Profile
craigmac / firenvim.lua
Created May 16, 2023 23:34
if not vim.g.started_by_firenvim == true then return end
vim.o.colorcolumn = '50,80,100'
vim.o.cursorline = true
vim.o.spell = true
vim.o.guifont = 'Iosevka Fixed:h24'
vim.o.laststatus = 1
vim.o.background = 'light'
craigmac / average_dark.lua
Created April 25, 2023 01:24 — forked from echasnovski/average_dark.lua
Experiment with computing "average popular Neovim color scheme"
-- Made with 'mini.colors' module of
if vim.g.colors_name ~= nil then vim.cmd('highlight clear') end
vim.g.colors_name = "average_dark"
-- Highlight groups
local hi = vim.api.nvim_set_hl
hi(0, "@constant.builtin", { ctermfg = 146, fg = "#8ebbd3" })
hi(0, "@constructor", { ctermfg = 110, fg = "#7fbce4" })
craigmac /
Created January 10, 2023 19:43 — forked from MlsDmitry/
MacOs Guide: determine hex code sequence for key combinations
  1. Ctrl + F keys and a lot of other key combinations are hooked by MacOs. You're mostly don't use them, so just turn everything off in System Preferences -> Keyboard -> Shortcuts. If you have another software that handles your key combinations, like Keyboard Maestro, you should turn these actions/macros off, otherwise you won't get right hex sequence.

  2. Enter command below in default MacOs Terminal. (Warning!: shortcuts can also be hooked by terminal emulators, like iTerm. To avoid it use default MacOs terminal. If you are on alacritty, you can enter alacritty --print-events and use poped up terminal).

xxd -psg

then type your key combination and hit enter. (Warning!: if you don't see any output for your combination, then read step 1 again)

craigmac /
Created September 17, 2022 18:26 — forked from mjlbach/
Asking effective questions


The open source community depends on the efforts of a small group of volunteers relative to the number of users. In order to make the most of contributors' time, here is some advice for asking “good questions”. This is largely paraphrased from this article by Eric Steven Raymond and Rick Moen, with edits for brevity and tone. If you have the time (and tolerance), I strongly recommend reading that article over this one. Let's start with the procedure.

The procedure

  1. Try to find an answer by searching the archives of the issue-tracker, IRC, matrix-room, discord, forum or mailing list you plan to post to.
  2. Try to find an answer by searching the Web.
  3. Try to find an answer by reading the manual.
  4. Try to find an answer by reading a FAQ.
  5. Try to find an answer by inspection or experimentation.

Neovim 0.7 User-Facing Features with Examples

More text.

Lua commands

Lua keymaps