Maxim Kim habamax

Emacs, Python, Treesitter and Eglot

Treesitter (“better”/faster syntax highlighting)

Make sure you have Emacs with treesitter support:
M-: (treesit-available-p) RET should return t
Make sure you have installed python treesitter grammar

How to use clangd C/C++ LSP in any project

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.

In the last years I've been asked multiple times about the comparison between raylib and SDL libraries. Unfortunately, my experience with SDL was quite limited so I couldn't provide a good comparison. In the last two years I've learned about SDL and used it to teach at University so I feel that now I can provide a good comparison between both.

Hope it helps future users to better understand this two libraries internals and functionality.

Extending Exuberant Ctags

Configuration

Like most CLI programs, Ctags can have its behaviour changed by passing it options like -R, to make it work recursively, or -f badaboom, to make it generate a file called badaboom.

Teaching Ctags about a new language or extending the rules of a supported language is also done with options like --langmap or --regex-<lang>. For example, we could call Ctags with these options:

$ ctags -R --regex-javascript=<regex> --regex-javascript=<regex> [...] --regex-javascript=<regex> .

Quickfix alternative to :g/foo/#

:help :global is an incredibly cool command.

One thing I like to do with :global is to list lines matching a given pattern in the current file and use that to move around. It looks like this:

:g/let/#
 7         let &path .= 'src/**,public/**,static/**'
 31     unlet b:gqview

33 nmap GQ :let b:gqview = winsaveview():set opfunc=Formatg@

My Vim-related gists

Long-form

This is a list of custom pseudo-text objects for Vim.

Note the use of "pseudo", here. Conceptually, text object are "special" motions but there is no proper mechanism dedicated to creating text objects, specifically. We are left with the generic mechanism succinctly described under the easy-to-miss :help omap-info.

Writing one's own pseudo-text objects and motions is a great way to extend Vim without perverting its nature ;-).

My Vim-related gists.

Redirect the output of a Vim or external command into a scratch buffer

Usage (any shell)

Show full output of command :hi in scratch window:

:Redir hi

Show full output of command :!ls -al in scratch window:

	" gq wrapper that:
	" - tries its best at keeping the cursor in place
	" - tries to handle formatter errors
	function! Format(type, ...)
	normal! '[v']gq
	if v:shell_error > 0
	silent undo
	redraw
	echomsg 'formatprg "' . &formatprg . '" exited with status ' . v:shell_error
	endif

	" :[range]SortGroup[!] [n\|f\|o\|b\|x] /{pattern}/
	" e.g. :SortGroup /^header/
	" e.g. :SortGroup n /^header/
	" See :h :sort for details

	function! s:sort_by_header(bang, pat) range
	let pat = a:pat
	let opts = ""
	if pat =~ '^\s*[nfxbo]\s'
	let opts = matchstr(pat, '^\s*\zs[nfxbo]')