firenvim VS gitlab

for leetcode specifically, i use firenvim to start a neovim session in the text area that would normally be leetcode's area and then have an autocmd that looks for "leetcode" in the filename and prompts me to select a filetype.

Yea worth it. As far as good for certain languages over others: text is text. Once you’re more experienced with how (neo)vim works, you won’t want to type anywhere. Like in the browser or obsidian

It's just the popular firenvim system: https://github.com/glacambre/firenvim

In that case give firenvim[1] a try. It uses your existing config (keymaps, plugins, autocmds, etc).

[1] https://github.com/glacambre/firenvim

You propably could use https://github.com/glacambre/firenvim inside of overleaf webpage. Althought I haven't tested it.

https://github.com/glacambre/firenvim is the correct link.

If by everywhere you mean everywhere, then take a look on this https://github.com/glacambre/firenvim

In general, for "rich text editors", firenvim needs to add special handling. For example firenvim supports CodeMirror (or used to): https://github.com/glacambre/firenvim/pull/623

> Can you make Firefox's form inputs use Vim keybindings?

Do you mean something like this: https://github.com/glacambre/firenvim?

Since the relevant code appears to be in the "ee" directory <https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.0-ee/ee/l...> and is not present in the foss repo, I'm guessing the answer is no, at least for now. They do have a history of "releasing" features from EE back to CE but my suspicion is not for LLM stuff

(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)

and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...

and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)

This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...