First of all, I'm sorry for my poor english.
But I really want to solve this problem.
I'm VIM user in M1 Mac,
and I use coc.nvim
Problem :
^Z is force inserted when I continue typing with coc-suggestion box.
screenshot down below;
Before more typing:
After typing with suggestion box:
I added issue yesterday,
I got answer 2h ago.
It seems like this problem fixed.
Enjoy your vim life;
issue and answer link
Related
This is a bizarre problem that, from searching relentlessly, appears I'm the only one in the known universe to have.
On my Ubuntu 18.04 server I'm trying to do some HTML edits with vim, but regardless of if I type "<" or ">" in vim they all come out like ">".
I'm at a complete loss here, I've never seen vim bug out on me so badly.
It's a problem with Digital Ocean's Web console, not VIM. There's currently no solution. Sorry to bother the VIM community with this issue.
Screenshot
Hey guys, I am new to Sublime Text3, and last week somehow I changed the way ST3 lint my code and show the error information. It looks actually a little annoying and I would like to get rid of these instant error display while I am coding. Can someone tell me how to do that?
In addition, how to setup ST3 so that when you type a function from a package, it could show its meaning and format? I can do it in my Windows PC but failed in MAC.
Really appreciate any help!
Open your package control, for Ubuntu its Ctrl+Shift+P, It may be Cmd+Shift+P, type disable in the package, it would show you Package Control:: Disable Package, press an enter key, now disable the packages that are causing it.
I am using Sublime Text 3 on my Mac (10.13.2)
The Preferences menu is always greyed and not usable. (even on restart)
Any idea to solve that?
Thanks
Paul
On macOS, I deleted the file Package Control.last-run in /Users/cookedapple/Library/Application Support/Sublime Text 3/Packages/User and restarted Sublime Text 3. The problem was resolved.
There have been some suggestions that third-party Mac apps may be causing issues. So you may try restarting Sublime Text – I guess you have already done that before looking for a solution, try to do that again after each of the following steps:
Restarting menu bar Bartender or SecondBar if present
Reinstalling latest installed ST packages
Delete(https://stackoverflow.com/a/48398420/880188) Package Control.last-run, i.e. via Terminal: rm ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/User/Package\ Control.last-run as mentioned in the other Answer
Restarting the computer
A user has figured out a reliable way to reproduce this (see Kronuz' comment from 6/19/18 on the issue tracker).
It seems to be caused by packages containing a large amount of files. There might be other causes as well, but hopefully with at least one reliable way to repro, the devs will come up with a fix.
Heys guys,
I just installed eclipse with e(fx)clipse and got some problems with the exspecially the layout. First of all the cursor does not being visually updated when doing horizontally movements(vertically works just fine). But this is only visually, when I edit the code it is on the correct position.
Aswell I have to click on the error warning at the line numbers to get the code complementation window longer then about 0.1 seconds. But even the it only shows up in the left top corner.
At last I have to close eclipse in the console or it will just freeze.
OS: Arch Linux always updated,
Eclipse: Version 4.5.1, java version,
Java: java-8-openjdk
Installed plugins: e(fx)clipse.
Hope you guys can help me,
Armin
So guys,
I figured out the solution for myself. The problem is GTK. With disabling it all the problem were solved. To do this start eclipse with the command line:
SWT_GTK3=0 eclipse
Sadly I have not yet found out how to do this permanently, but I will edit this answer as soon as I find out.
Armin
I installed clang_complete for vim,but it doesn't work. For example: When I typed std:: in a c++ file with vim, the bottom of vim's window shows that:
User defined completion (^U^N^P) Pattern not found
How can I solve this?
The common solution to this appears to be to add:
let g:clang_user_options='|| exit 0'
to your .vimrc file.
This problem was solved at the issue #178. This was in truth a problem with Clang, I've opened a bug report and it was promptly solved.
Also, I invite you to take a look at my setup.