Closed staycreativedesign closed 1 year ago
Huh! Thanks for the report.
I'm not seeing this on my Mac, but I'm installing with brew install neovim --HEAD :)
I do notice that the current treesitter docs for lazy.nvim don't seem to specify the treesitter-textobjects dependency like we do here. I'll check with folks and see if it makes sense for us to update that bit of code.
Please try deleting the dependency block - lines 167,168 & 169 pointed to by the link I cited above and let us know if that fixes your problem.
Thanks for the report!
I am having the same issue and brew install neovim --HEAD gives me a compiler error :(
@Giulio2002 Great, thanks for the report.
Please try deleting lines 167,168 & 169 and let me know if that fixes it for you.
If it does, I'll publish a pull request.
I published the PR. Please approve it if removing those three lines works for you and we'll get it merged.
getting Not an editor command: TSUpdate
then it just goes to a cyan screen and i need to remove nvim. would gladly install nvim --HEAD but i am getting a compile error, maybe it will get fixed soon as that is the master branch anyway
Forget --HEAD please! :) Let's focus on the problem at hand.
You say "it just goes to a cyan screen". Does that mean there's no modeline? Does it not respond to keyboard input?
it does respond to it, it also prints editor command: TSUpdate
it just gets all cyan and notifies that one of the builds failed and that all other are successful
it responds but it goes to a oldschool blue screen of death like in windows LOL , it has to do with the colorscheme I removed it and it worked.
On Wed, Apr 19, 2023 at 5:33 PM Chris Patti @.***> wrote:
Forget --HEAD please! :) Let's focus on the problem at hand.
You say "it just goes to a cyan screen". Does that mean there's no modeline? Does it not respond to keyboard input?
— Reply to this email directly, view it on GitHub https://github.com/nvim-lua/kickstart.nvim/issues/271#issuecomment-1515411958, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO4XUXCDXVB3P5BLZQBH6DXCBKZRANCNFSM6AAAAAAXEI3UD4 . You are receiving this because you authored the thread.Message ID: @.***>
Agree with Giulio
On Wed, Apr 19, 2023 at 5:35 PM Giulio rebuffo @.***> wrote:
it just gets all cyan and notifies that one of the builds failed
— Reply to this email directly, view it on GitHub https://github.com/nvim-lua/kickstart.nvim/issues/271#issuecomment-1515416670, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO4XUS4Q6FKVZRELZAOGQ3XCBLCLANCNFSM6AAAAAAXEI3UD4 . You are receiving this because you authored the thread.Message ID: @.***>
Extra detail: M2 Chip
lol with no color scheme it is literally just blue screen of death
Extra detail: Not a M1 or M2
On Wed, Apr 19, 2023 at 5:38 PM Giulio rebuffo @.***> wrote:
lol with no color scheme it is literally just blue screen of death
— Reply to this email directly, view it on GitHub https://github.com/nvim-lua/kickstart.nvim/issues/271#issuecomment-1515418778, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO4XUXR3ZO7Q36G5UFWLWDXCBLMNANCNFSM6AAAAAAXEI3UD4 . You are receiving this because you authored the thread.Message ID: @.***>
Can someone maybe post a screenshot please? I feel like we're trapped in the pit of infinite "communication is impossible" despair here.
Thanks.
Hi, can you check the version of neovim? I found that brew install neovim
won't install the latest version of neovim, it's too old for me
that must be the problem
On Thu, Apr 20, 2023 at 6:25 PM WindSoilder @.***> wrote:
Hi, can you check the version of neovim? I found that brew install neovim won't install the latest version of neovim, it's too old for me
— Reply to this email directly, view it on GitHub https://github.com/nvim-lua/kickstart.nvim/issues/271#issuecomment-1517017849, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO4XUSGER3NNOMQXOGXSWDXCGZUDANCNFSM6AAAAAAXEI3UD4 . You are receiving this because you authored the thread.Message ID: @.***>
I think you're right. Closing PR and closing this issue for now. Please ensure you're running the latest release version of Neovim. At least 0.8.0
This issue has already been closed but I would like to share some of my findings.
First, what I am using:
brew install neovim
I was following the steps in this video by TJ de Vries, where he literally copies the init.lua
file from the repo towards the ~/.config/nvim
folder. After copying and running Neovim I got error messages very much alike the person who started this thread.
Tried the steps mentioned in the vid several times but without luck. Then I noticed there are some extra files in this repository. Did some cleanup (the additional files and folders in .config/nvim
, .local/state/
and .local/share/
) and reinstalled Neovim with Homebrew.
After the cleanup I followed the procedure mentioned in the readme of this project and... succes. No errors this time.
So, tl;dr: don't follow the vid but RTFM 😁 .
RTFM? What is this? 1997?
On Thu, May 4, 2023 at 3:43 PM Mark van der Meer @.***> wrote:
This issue has already been closed but I would like to share some of my findings.
First, what I am using:
- Fresh install of Neovim v0.9.0 installed via Homebrew with just brew install neovim
- M2 Macbook Pro
I was following the steps in this video by TJ de Vries https://www.youtube.com/watch?v=stqUbv-5u2s&t=876s, where he literally copies the init.lua file from the repo towards the ~/.config/nvim folder. After copying and running Neovim I got error messages very much alike the person who started this thread.
Tried the steps mentioned in the vid several times but without luck. Then I noticed there are some extra files in this repository. Did some cleanup (the additional files and folders in .config/nvim, .local/state/ and .local/share/) and reinstalled Neovim with Homebrew.
After the cleanup I followed the procedure mentioned in the readme of this project and... succes. No errors this time.
So, tl;dr: don't follow the vid but RTFM 😁 .
— Reply to this email directly, view it on GitHub https://github.com/nvim-lua/kickstart.nvim/issues/271#issuecomment-1535316073, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO4XUR2DB6RPSFRCLLDFWLXEQBGTANCNFSM6AAAAAAXEI3UD4 . You are receiving this because you authored the thread.Message ID: @.***>
Hey, thanks for posting this!
One of the challenges around supporting a projects like this is that when you try to put up a giant "WELCOME" sign for folks to get into Neovim, that means support tickets with RTFM questions and lots of them :)
So seeing someone say "Hey, I RTFM-ed, and it worked great!" is nice to see :)
@coreice can confirm this solution works, thank you very much.
for me it solved module ibl not found
rm -rf ~/.config/nvim
rm -rf ~/.local/state/nvim
rm -rf ~/.local/share/nvim
remove neovim, dependencies and configuration files
sudo pacman -Rcnsu neovim
install neovim
sudo pacman -S neovim
fresh clone of kickstart.nvim
No need to uninstall nvim, for me it worked just by running
rm -rf ~/.local/state/nvim
rm -rf ~/.local/share/nvim
:Lazy update indent-blankline.nvim
fixed it for me. I had v2.20 installed. This command updated it to v3.5.3.
I would advise against doing this without a backup:
rm -rf ~/.config/nvim
rm -rf ~/.local/state/nvim
rm -rf ~/.local/share/nvim
I made the mistake of doing this without backing up and now my whole Neovim installation is broken
Ran the init and