Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vscode: cannot edit read-only editor #8

Open
Devin-Pi opened this issue May 9, 2024 · 8 comments
Open

vscode: cannot edit read-only editor #8

Devin-Pi opened this issue May 9, 2024 · 8 comments

Comments

@Devin-Pi
Copy link

Devin-Pi commented May 9, 2024

Thanks for your wonderful sharing!

After installing the files as told by your documentation, I found that I cannot Rename, Create a new directory/file, etc, under Explorer mode. The vscode showed that "cannot edit in read-only editor". Do you have some ideas to solve it?

Thank you!

@mrbeardad
Copy link
Owner

Can you list the steps to repoduce the issue? And will this issue still occur after disabling the vscode-neovim extension? @Devin-Pi

@Devin-Pi
Copy link
Author

Devin-Pi commented May 9, 2024

Can you list the steps to repoduce the issue? And will this issue still occur after disabling the vscode-neovim extension? @Devin-Pi

Of course.
Step 1: Open a folder in vscode
Step 2: spc + e, the contents shown in Fig.1.
Step 3: Type a, as shown in Fig.2, "cannot edit in read-only editor".
image
Fig. 1
image
Fig.2

@mrbeardad
Copy link
Owner

There is no spc+e shortcut in explorer, there is only space to expand folder or preview file. I can't reproduce the issue in Fig.1

image

@Devin-Pi
Copy link
Author

Devin-Pi commented May 9, 2024

There is no spc+e shortcut in explorer, there is only space to expand folder or preview file. I can't reproduce the issue in Fig.1

image

Thanks for your reply!
Now, I have got this ERROR. It seems related to the Buffer Manger. It is strange.
image

@mrbeardad
Copy link
Owner

Thanks for your reply! Now, I have got this ERROR. It seems related to the Buffer Manger. It is strange. image

Actually, neo-tree plugin is disabled when you use in vscode, see lua/user/plugins/vscode.lua

@Devin-Pi
Copy link
Author

Devin-Pi commented May 9, 2024

Thanks for your reply! Now, I have got this ERROR. It seems related to the Buffer Manger. It is strange. image

Actually, neo-tree plugin is disabled when you use in vscode, see lua/user/plugins/vscode.lua

Thanks for your reply!
Actually, I know why there always exists some problems. Because I have downloaded the wrong repo. Now, it woks:).

@Devin-Pi
Copy link
Author

OS System: Ubuntu2204
Platform: VScode
When I select something by "viw" or "vip" and paste them, I met the following errors. Do you have some ideas to solve it?
Thank you!

2024-05-10 10:15:41.443 [info]
14 lines yanked
Error detected while processing TextYankPost Autocommands for "*":
Error executing lua callback: .../share/nvim/lazy/yanky.nvim/lua/yanky/storage/memory.lua:12: attempt to index field 'config' (a nil value)
stack traceback:
.../share/nvim/lazy/yanky.nvim/lua/yanky/storage/memory.lua:12: in function 'push'
.../.local/share/nvim/lazy/yanky.nvim/lua/yanky/history.lua:21: in function 'push'
/home/rdpi/.local/share/nvim/lazy/yanky.nvim/lua/yanky.lua:267: in function 'on_yank'
/home/rdpi/.local/share/nvim/lazy/yanky.nvim/lua/yanky.lua:47: in function </home/rdpi/.local/share/nvim/lazy/yanky.nvim/lua/yanky.lua:46>

@mrbeardad
Copy link
Owner

  1. What is your nvim --version
  2. Which keymap did you use to paste? Maybe a full steps list is helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants