Hacker News new | past | comments | ask | show | jobs | submit | ossusermivami's comments login

nice idea but i get that error when i try to use the docker image (on a nixos env)

NameError: name 'SRE_FLAG_TEMPLATE' is not defined. Did you mean: 'SRE_FLAG_VERBOSE'?

(using the mentioned docker command on README $ docker run --rm -v `pwd`/nginx.conf:/etc/nginx/conf/nginx.conf getpagespeed/gixy /etc/nginx/conf/nginx.conf)


:! itself has not been stripped from neovim, it's the "interactive" :! that has been stripped (as the OP said)

i.e if you do :!bash in vim you enter bash in neovim you won't


Thanks for the clarification. That makes sense and seems like a reasonable change to me.


I wouldn't say that `:!bash` is the most illustrative example of its impact. It bites you when you run any command that spits out a prompt, most commonly a [Yn] prompt. You can't use `:!` for these in nvim.


it's interesting to see how emacs have seen a renaissance lately with AI there is so many good modes to interact with LLM not the way the other editors does it but more of a Emacs way. for example gptel https://github.com/karthink/gptel


there is no way in hell i would sell my soul to use Oracle....


or you can do =cat on zsh


it's built-in emacs as well now!


ai generated blog post (or reworded, whatever) are kinda getting very irritating, like playing chess against the computer, it feel soulless


How can you tell this post was ai generated? I’m curious.


Is it related to the mojo language work? would that affect how they track the language features?


I use devenv.sh and generate oci containers out of it, which give me kinda the best of both worlds!

(nobody in my team use vscode or devcontainers but enjoy using docker)


This is old, but wondering if you had any publicly available project setup this way. Thanks


just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts writing their nvim config)

[1] https://www.lazyvim.org/


Clearly you didn't read any of the threads as it is sometimes even lazyvim that causes these incompatibilities:

https://old.reddit.com/r/neovim/comments/1dgtyzw/lazynvim_do...

https://old.reddit.com/r/neovim/comments/1dp47gi/lazyvim_own...


One of those threads is about lazy.nvim, not lazyvim. The other is a question about what to do after accidentally installing lazyvim with the wrong shell on windows, not about plugin updates breaking things.


Lazyvim is powered by lazy.nvim, at some point it'll break. These are example posts, you can feel free to go through reddit for more examples but yes Neovim does routinely break more for me than VSCode ever does, which is basically never.


it never has been my experience! i have used lazyvim distro for the last year or so and run some :Lazy update for time to time and usually i just need to close neovim and restart and it will all be working well..

I think i had an issue when they moved to conform.nvim from the deprecated language server based method but that's maybe about it (I deleted the nvim cache and it was all good after)


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: