I have Qt Creator 4.1.0 ubuntu 16.04. And I have problems with completion and code highlighting. I need to wait 3-4 secs(or more) for completion code and highlight key words.
What is wrong?
Qt Creator 3.6.0 is working normally.
I can confirm I observe the same problem on Windows 7 after upgrading from 3.6 to 4.1. I used to be able to tab complete function signatures and that no longer works which is annoying. Haven't tried 4.2RC yet to see if its fixed but I'll update this post once I do.
Related
I'm using Ubuntu Xenial (yes I know it's out of date, I'm going to upgrade it soon), neovim 0.6.0 (which apt tells me is the latest version), and vscode 1.60.1. Until recently could save files with the :w command, but all of a sudden when I use that command nothing happens. It probably happened when my version of vscode was updated, but I'm not sure. Is there a setting somewhere that controls this, or could something have overridden it? Googling it shows fairly old results, and since it was working a few weeks ago I'm not sure how helpful those ones are.
Ctrl + s works but I'm so used to using :w that I do it automatically and it takes me time to remember to do it the other way. Also, since :w works in all other vims that I use, I'd like to get vscode working the same way again.
I was running into this problem too and I found that the solution is to use neovim stable, not the prerelease 0.6.x version. Now all the editor commands work fine.
I found this solution via this GitHub issues link: https://github.com/asvetliakov/vscode-neovim/issues/736
using the latest vs code, on a new installation, with only 1 plugin (which i know not to be causing the problem, since i have repeated the whole thing with another plugin; same issue) on a mac also using the latest catalina os.
issue:
writing a couple of pages (2 or 3) to the terminal, either from the terminal itself or from within the plugin, the terminal becomes unbearably slow, scrolling up or down freezes it entirely.
i found some previous links talking about this issue, but they are with older versions of vs code, and the responses have always been "this is now fixed in version xxx".
question:
is there some general setting in vs code that will prevent this?
or do you just have to wait for the next "updating", the next "breaking", the next "updating", etc?
Try this, now my terminal works faster also in Big Sur:
codesign --remove-signature /Applications/Visual\ Studio\ Code.app/Contents/Frameworks/Code\ Helper\ \(Renderer\).app
I am using clion latest version 2020.2
Build #CL-202.6397.106, built on July 28, 2020
Autocomplete suddenly stopped working even though clion can build and complie my code just fine.
To make sure the issue is not project dependent, I started a new project. However, the problem still presists. As you can see in the attached image below. Whenever I explicity press (ctrl+space) I get this empty suggestion dropdown and the icon keeps rotating forever. (Note: If I don't press ctrl+space, the dropdown menu never shows up)
I made sure that PowerSaveMode is disabled.
I also tried File->Invalidate Cache/Restart->Invalidate and Restart
Did anyone face a similar issue? Any suggestions to what could be the cause of this problem?
Additonal information
gcc version: gcc (Ubuntu 4.8.5-4ubuntu8) 4.8.5
g++ version: g++ (Ubuntu 4.8.5-4ubuntu8) 4.8.5
I am posting this answer in case someone comes across this issue in the future.
The issue was definitly caused by the new update to clion. So I installed an older version. There is a tool named "JetBrains Toolbox" which is very convient when it comes managing multiple versions of any JetBrains software (clion in my case).
An additional note, if you want to run clion (or any other solution) as a superuser do not do that through the JetBrains toolbox. The toolbox will have the installtion location for each installed version, use it to run as a superuser from the terminal.
I'm making a vscode extension for my personal use. I'd really like to use a more recent node version. However, I'm not sure how does VSCode chooses which node version to use.
The only node.js that I have installed is 8.1.3. But when I debug the extension, I see that VSCode uses 7.*.* (via process.version).
I've been searching documentation for an hour, so far, without luck. Any help is appreciated.
This is not possible. Quoting the reply of one of the team members (Andre Weinand) in #18253:
VS Code runs extensions on the node version that is built into electron (on which VS Code is based). This cannot be changed.
I'm following these instructions to remotely debug a python script http://pydev.org/manual_adv_remote_debugger.html
Using breakpoints and stepping work without a problem, but after resuming the script (without any other further breakpoints) the script executes the remaining instructions, and then hangs instead of exiting normally. Even closing the server from pydev does not help, I have to Ctrl+Break the script
I am sure I've done this a while ago with an older eclipse+pydev, and the script resumed and exited normally (and it's very important for me not to mess the rest of the execution).
I've tried this with both Eclipse Luna and Liclipse pydev_4.0.0.201504132356, pydev_4.0.0.201504092214 on Windows 7 x64, same behaviour
Is this an intended behavior or a bug? How could I make pydev let the script end normally?
I can't reproduce this here... please report that as a bug adding details on how to reproduce it (i.e.: ideally, create a project on github and add a step-by-step on how to reproduce it so that it can be fixed... without being able to reproduce it properly, it may be pretty hard to fix).
Also, please give details on the OS and Python version used in the report (https://sw-brainwy.rhcloud.com/tracker/PyDev/)