Is there a way to delete obsolete Plunker versions, but keep the latest version?
There are a few lines I pasted in the original version of my plunk that I would like to hide.
It is not possible to delete versions of a Plunk without deleting the entire Plunk.
Related
After restarting vscode whenever I try to use an autocomplete suggestion from IntelliCode, it also includes the recommended star thing.
issue video
I have tried switching to an older version of intelliCode, disabling all my other extensions, switching to a new profile, and resetting my vscode settings.
I have also searched google, but was unable to find anyone else with this problem.
A commit has been pushed to fix this already, see https://github.com/microsoft/vscode/pull/172616. I would think it'll be in the next Stable Release next week.
Looks like it is a new reported issue from multiple users. See Committing completion in a TS file inserts a star character.
Just filed 01/25/2023. I suggest you upvote and comment if your use case is different than those already presented. And keep an eye on that issue if there is some sort of a fix posted. It should be a simple fix, someone changed the mapping from the suggestion to the actual inserted completion.
[Also incorrectly reported at https://github.com/microsoft/vscode/issues/172419 - it is an extension issue so the first link is where to respond.]
I am developing mkdocs website. Here I need to add favicon for my website. I tried like this but it is not working.
I added site_favicon in mkdocs.yaml file and using readthedocs theme. But it is not working
site_favicon: img/favicon.ico
Can anyone help me with this?
Simply save your new image to img/favicon.ico within your docs_dir. There is no need to change any setting.
Back in version 0.16.0, the site_favicon configuration setting was deprecated. Then in version 0.17.0 is was completely removed. Therefore, your config is doing nothing.
All of that said, you may be running into the bug reported at #1671, which was fixed in #1672 and will be available in the next release. If so, you will need to wait until 1.1 is released.
My Problem
When I compare two versions of a file with VS Code and the built-in Git features TSLint does not ignore the revisions but marks the errors. Since the diff files are located in AppData\Local\Temp on Windows the path checking fails and other things as well.
However, most annoying is not the red line in the file view but that they are listed in the Problem Panel and I get like 20+ problems just because opening one file revision and they won't go away until I reopen VS Code, so they add up during time.
That makes the panel useless for me, since I see lots of pseudo-problems, I won't notice an actual problem.
What I tried
I tried in my settings.json
"tslint.exclude": ["**/AppData/**"]
but that didn't work out.
Any suggestions would be much appreciated.
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
Using tinymce 3.7 We have a text editor where if one right clicks on a table to bring up table properties and changes the background color the changes are not reflected on the actual table after hitting update.
I tried searching to see if this was a known issue perhaps addressed in a later version of TinyMCE but could not find anything that appeared to discuss this particular issue. Is there a fix or at least documentation of this being a known tinyMCE issue that any of you know of?
There are a lot of issues in TinyMCE with IE11. To solve those issues you'll have to upgrade to at least 3.5.10 version of TinyMCE. Everything works fine in 3.5.10. I tested it on IE11. There's just one thing which will not work, that is searchreplace. For that you'll have to upgrade to 4.x version of TinyMCE.
do you face also the problems with Xcode 4 autocomplete feature that used to work great on version 3.x.x?
I've imported in the Prefix some classes and Xcode doesn't want to help me with the code entry. I have to manually add above #implementation
import "myclass.h"
To make Xcode help me entering the class name, properties, methods, macros defined in the myclass.h. On 3.x.x I could import those important classes once in the prefix and the autocomplete feature worked without any problems anywhere in the project.
Sometimes Xcode goes even more stupid, it doesn't want me to help typing the classes like UIButton, UIView and the common method like
addTarget:action:forControlEvents: for my buttons.
Do you also has the problems I mentioned in the Xcode 4, any solutions?
I was able to correct this issue by setting Precompile Prefix Header to No in the build settings.
EDIT 3: Note that this indexing issues has mostly disappeared in recent versions of Xcode (4.1 for sure, latest pre-Lion 4.0.x I think), and that I do not use this workaround anymore, using pch... And in fact not using Xcode anymore... AppCode ftw! :)
An easy, but quite dirty workaround imho is not using precompiled header .pch file to do global includes, but instead go a global header .h, that you include... everywhere. That way indexing will work flawlessly...
I Know that's dirty, don't downvote me please :) I'll delete this answer as soon as someone propose something better! Which I would love.
Off-topic, but related, read somewhere llvm2 is not supposed to get a gain speed with .pch files. which kind of deprecate them.
EDIT: Just checked to be sure of my answer, latest version of Xcode (4.0.1 when writing this) looks like fixing that bug for me. Did you upgrade to latest version?
EDIT 2: Removed my global import header .h, all its references, and moved my global imports into .pch file... That doesn't work as well I expected, latest Xcode 4.0.1 improved on this part but still have some cases where it fails. (I'm working on a project with hundreds of files). Looks like cleaning index/restarting Xcode fix it. I might consider reverting to my dirty workaround...
I have found that changing compilers, building, and then changing back, and building again works relatively consistently. Wrote a post about it on my blog:
http://rhappsody.wordpress.com/2011/08/03/xcode-4-code-colouring-and-auto-completion/
I found that sometimes the autocompletion gets broken when dealing with stuff defined in the prefix header. One way to get Xcode to index those again correctly is to use the touch command in the Terminal, e.g.:
touch /Users/someguy/Document/Foo-App/Foo-Prefix.pch
Or add a new line to the prefix for the same effect. Xcode then gets busy reindexing and things work again.
I've faced the same issued as soon as I moved to XCode4. What I realised was that I needed to install iOS's documentation to have the code completion fully working.
Go to Xcode -> Preferences -> Documentation and click GET on the iOS 4.3 Documentation. In the iTunes-style status window, the download progress will be shown.