Add packer itself to bootstrapping in README.md #814
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When you copy/paste the bootstrapping code from the README packer will install but try to remove itself again right away. No matter if you answer yes or no to the question you get a 'display_win' error.
|
Are you referring to #750? The bootstrap example should work as is, but it seems there may have been a regression in Neovim core since v0.6.1. |
|
I'm referring to #742. I got the same question, asking if it is ok to remove the packer directory, and then throws the display_win error. Like mentioned in the issue, when adding |
|
Still happens on neovim HEAD 0.8.0-dev-917-gbaaaa1f2b, the README.md should include |
jvcarli
added a commit
to jvcarli/cosmonauta.nvim
that referenced
this pull request
Jan 2, 2023
[packer.nvim](https://github.com/wbthomason/packer.nvim) has some anti-features and bugs that were a deal breaker for me: - Bootstrapping is not straightforward - Snapshots are fundamentally broken, i.e. if I removed a plugin I tried to restore a snapshot packer would not work. - Luarocks install doesn't work on macos - Packer compilation step is annoying and sometimes makes config files out of sync with the current setup, which makes debugging and plugin development awkward [lazy.nvim](https://github.com/folke/lazy.nvim) doesn't have a compilation step, doesn't require [impatient.nvim](https://github.com/lewis6991/impatient.nvim) for speeding up modules initialization, has a straightforward bootstrap process and in general has a better design than [packer.nvim](https://github.com/wbthomason/packer.nvim). SEE: wbthomason/packer.nvim#814 SEE: wbthomason/packer.nvim#1010 SEE: wbthomason/packer.nvim#180
jvcarli
added a commit
to jvcarli/cosmonauta.nvim
that referenced
this pull request
Jan 2, 2023
[packer.nvim](https://github.com/wbthomason/packer.nvim) has some anti-features and bugs that were a deal breaker for me: - Bootstrapping is not straightforward - Snapshots are fundamentally broken, i.e. if I removed a plugin I tried to restore a snapshot packer would not work. - Luarocks install doesn't work on macos - Packer compilation step is annoying and sometimes makes config files out of sync with the current setup, which makes debugging and plugin development awkward [lazy.nvim](https://github.com/folke/lazy.nvim) doesn't have a compilation step, doesn't require [impatient.nvim](https://github.com/lewis6991/impatient.nvim) for speeding up modules initialization, has a straightforward bootstrap process and in general has a better design than [packer.nvim](https://github.com/wbthomason/packer.nvim). SEE: wbthomason/packer.nvim#814 SEE: wbthomason/packer.nvim#1010 SEE: wbthomason/packer.nvim#180
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you copy/paste the bootstrapping code from the README packer will install but try to remove itself again right away. No matter if you answer yes or no to the question you get a 'display_win' error.