Note
A more bleeding-edge version of this is available here.
A pretty simple custom LSP hover window that tries to solve the issues I face with the built-in one.
Note
A more bleeding-edge version of this is available here.
A pretty simple custom LSP hover window that tries to solve the issues I face with the built-in one.
| ---Utility for keymap creation. | |
| ---@param lhs string | |
| ---@param rhs string|function | |
| ---@param opts string|table | |
| ---@param mode? string|string[] | |
| local function keymap(lhs, rhs, opts, mode) | |
| opts = type(opts) == 'string' and { desc = opts } | |
| or vim.tbl_extend('error', opts --[[@as table]], { buffer = bufnr }) | |
| mode = mode or 'n' | |
| vim.keymap.set(mode, lhs, rhs, opts) |
This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
| -w, -window, -windowed Run in windowed mode. | |
| -per ?? | |
| -lq Runs game using low quality/low vision mode; same as Large Font Mode setting. | |
| -gamma <num> Override Gamma. Default: 0 | |
| -vsync <num> Override VSync. Default: 255 | |
| -aftermath <string> ?? 23 chars max. Default: unset | |
| -s <string> ?? 23 chars max. Default: unset | |
| -gametype <num> ?? Default: 0 | |
| -arena <num> ?? Default: 0 | |
| -joinid <num> ?? Default: 1 |
tl;dr: If you want to just know the method, skip to How to section
Clangd is a state-of-the-art C/C++ LSP that can be used in every popular text editors like Neovim, Emacs or VS Code. Even CLion uses clangd under the hood. Unfortunately, clangd requires compile_commands.json to work, and the easiest way to painlessly generate it is to use CMake.
For simple projects you can try to use Bear - it will capture compile commands and generate compile_commands.json. Although I could never make it work in big projects with custom or complicated build systems.
But what if I tell you you can quickly hack your way around that, and generate compile_commands.json for any project, no matter how compilcated? I have used that way at work for years, originaly because I used CLion which supported only CMake projects - but now I use that method succesfully with clangd and Neovim.
| javascript: fbid = /share_fbid":"(\d+)"/g.exec([...document.getElementsByTagName("script")].filter(x => x.innerHTML.includes("share_fbid"))[0].innerHTML)[1]; alert(location.href.split("/").slice(0, -1).join("/") + "/" + fbid); | |
| // can be used in console / bookmark / address bar (remember to add back javascript if the browser strips it automatically) |
Please see here: contour-terminal/vt-extensions
Synchronized output is merely implementing the feature as inspired by iTerm2 synchronized output,
except that it's not using the rare DCS but rather the well known SM ? and RM ?. iTerm2 has now also adopted to use the new syntax instead of using DCS.
| #!/usr/bin/env python3 | |
| # Copyright (c) 2018 Foundries.io | |
| # | |
| # SPDX-License-Identifier: Apache-2.0 | |
| import argparse | |
| from collections import namedtuple | |
| import struct |