savchenko

@moreati , 1. No, the `sudo` is tied to U2F, in `/etc/pam.d/login`: `auth sufficient pam_u2f.so cue userpresence=1 pinverification=1` 2. No. 3. Without mitogen I can execute the playbook without any...

The page above is 404. Also, do you reckon backups are a little out-of-scope for the TODO application?

```lua local capabilities = vim.lsp.protocol.make_client_capabilities() capabilities.textDocument.completion.completionItem.snippetSupport = true -- Jinja vim.filetype.add { extension = { jinja = 'jinja', jinja2 = 'jinja', j2 = 'jinja', }, } require'lspconfig'.jinja_lsp.setup{ capabilities = capabilities...

Magically began working after I have updated jinja-lsp to the latest version:  Strangely, required no changes to nVim config.

There are many, many issues with snaps and AFAIK Ubuntu is the only distribution using them. Appimage would run virtually anywhere as the single binary. Flatpak has its advantages, but...

OK, this might be a simplistic solution, but here are two ideas: 1. Provide appropriate snippets for users of common plugin managers. For example: ```lua { url = 'https://github.com/HiPhish/jinja.vim', submodules...

You still can use virtualenvs. `pipx`, `poetry`, etc. all work as usual.

Here: https://github.com/nwg-piotr/nwg-look/blob/8f63328faa3bb83c546b63fa91c7e89c0163bafb/tools.go#L1254 `dataHome()` returns `$HOME/.local/share` which prevents `nwg-look` from starting. I propose to search the `$PWD` as well.

@alex-courtis, I am observing this as well. Related to https://github.com/linrongbin16/fzfx.nvim/issues/726, seems like it affects other plugins (?!). This particular computer has the following sysctl preference: ``` fs.inotify.max_user_watches=325796 ``` ...which doesn't...

> I already downloaded generated binaries with cuBLAS support. But it is not using BLAS (BLAS = 0 while running. I have noticed that Windows blas-enabled build of v1.4.0 reports...