Sublime 3: Double clicking from find-results page no longer working - sublimetext3

Since build 3080, double clicking from the find-results page to jump to line-in-file directly is no longer working for me.
Has anyone else experienced or have a fix for this issue?

Looks like this plugin was the culprit, removing it fixed the issue.
https://github.com/titoBouzout/FindResultsApplyChanges
Also, the author of the plugin states that this won't be fixed: https://github.com/titoBouzout/FindResultsApplyChanges/issues/9

Related

Is there a way to fix missing icon for Visual Studio Code on Wayland?

I have a problem with vscode if I run it on Wayland natively. Instead of appropriate icon I got a generic icon for Wayland applications as on screenshot.
I have tried to find a temporary solution editing .desktop files of vscode, but without success. As I know, the problem is in the wrong wmclass which sets on startup of vscode.
Upd:
I've got update from the AUR, which fixes all my issues)
I am struggling with this problem too.
I have tried to find solution and find a few issues
https://github.com/microsoft/vscode/issues/129953
Please check last messages at that discussion.
You can try to substitute value of WMClass with visual-studio-code of Code
StartupWMClass=code-url-handler
Also there is solution like this
"The problem can also be resolved by modifying the desktopName entry in /opt/visual-studio-code/resources/app/package.json to "desktopName": "visual-studio-code.desktop"" from that discussion too.

how to remove Loading time focus in etherpad?

My issue is posted on below link
https://github.com/ether/etherpad-lite/issues/2231
if anyone have solution then plz give ans.
click on below link to get answer.
I made one plugin which disable the init time focus.
https://github.com/odoo/odoo/tree/master/addons/pad/static/plugin/ep_disable_init_focus

Dreamweaver Coding Hint won't go away

I've had this issue several times and usually I can just shut down the program and restart it. But this time I have a bunch of windows open and I don't want to restart Dreamweaver.
My problem is that Dreamweaver brought up a code hint, but the code hint box now won't go away. It just sits there floating in the middle of the page. It doesn't matter if I click to Preview or any other tab in Dreamweaver, it still just sits on top of everything.
I'm working on a Mac, Dreamweaver CC (cloud, fully updated). Anyone else have this problem???
This has been a HUGE PAIN for me as well! You can make the code hint disappear though by finishing out an element that is in the code hint box. For instance if the code hint box appears and you can see class in the drop down... create a <div class="xyz"> real quick and the code hit box will dissipate after you close the quotes on the class because you used an element in that box. As to why this continually happens on the Mac version I have no idea, but I hope they fix it soon!
It's a known bug since years as you can read here: https://forums.adobe.com/message/7745689
Someone suggests as a workaround to set the Coding Hint delay to 0 (as said here: https://forums.adobe.com/message/7745689#7745689) but for me, in Dreamweaver CC 2015 Windows fully updated via cloud app, this bug still occurs while I code JS files.
Awaiting for a final fix, I hope this suggestion can be useful for you on Mac. :)

In Visual Studio 2012 - Keyboard suddenly stops working properly

as stated in the questions title, we have an issue with VS2012. The problem is that sometimes suddenly some keyboard-input in VS isn't executed properly, if at all.
When the problem occurs, we are only able to type in characters and numbers, but neither are we able to delete them (backspace or DEL), nor to use the arrow key to jump up down a line or to the next/previous character. Overwriting a text which has been marked with the mouse is working.
I have found a very similar Question but the hints stated there doesn't work here. Those are:
Hitting Alt+Enter
Closing and Reopening Editor Windows
Closing the ToolboxWindow
Restarting VS
Pressing ScollLock
The Problem seems to be related to the Stylecop-AddIn. After uninstalling it, the issue doesn't come up anymore. Is there some known workaround? Thanks in advance!
Apparently StyleCop can be used with out Resharper, I didn't know. Very sorry. However, if you look at the documentation for StyleCop, if you right click on your project, click Source Analysis Settings, you will be presented with a dialog to turn on or off all of StyleCops rules.
Here is a link to the actual documentation which has images which helps describe it. StyleCop Settings

ReSharper Settings Grayed Out

Today I tried to made "Code Cleanup" of single file in ReSharper 6.0 (VS 2010). The Code Cleanup dialog did not show up so I tried again.
I then discovered, that the feature is grayed out and when I press hotkey for Code Cleanup, the notification area shows that the "command is not available at the moment".
Even the Code Cleanup settings are hidden. The panel where settings should be shown says that the settings are solution-specific and thus a solution needs to be opened (although it is, however).
All other solution-specific settings and features work, except for Code Cleanup.
I want to avoid re-installing ReSharper or resetting its settings, because otherwise I would need to set it up again (long and annoying work of setting all the options as before re-install).
I am afraid that backing up settings and restoring it again restores the problem as well.
Any suggestions?
Suggestions:
Ensure that the file that you're trying to cleanup is included in your solution.
Try to reopen solution (close and then open again).
Upgrade to 6.1.1, maybe its fixed there.
File a bug report at http://youtrack.jetbrains.com
Both ReSharper 7 and 8 seems to work OK.
I know this is an old answer, but I found a little more insight on this. According to Jerrie Pelser in this blog post from last year, this may have to do with the file being part of a NuGet package. In my case, this was definitely it!
In case of link rot, basically the post mentions that ReSharper will avoid refactoring/code cleaning for files it detects were added as part of NuGet packages. This is similar to how it will not allow code cleanup for generated code.

Resources