I would like to know how can i disable this red flags warnings (image-link below) to showing and what is this for and which package belongs? I have to be constantly hitting the X and is disturbing the work flow.
This is a built in feature in Sublime; it's controlled by the following setting, which defaults to being turned on:
// Shows build errors just under the line on which they occur.
"show_errors_inline": true,
If you turn this off in your user preferences (right hand pane in the Preferences > Settings window) it will stop doing that.
If this setting is turned off but you still see these appearing when you build, then you're using a third party package that's not properly respecting the setting; in that case you would need to contact the maintainer of said package and get them to fix that for you.
Related
Is there a way to disable Gnome classic desktop hot corner (upper left corner)? I activate it accidentally far more often than I do intentionally which is quite annoying. I have a Fn+whatever key that will do the same thing, so I don't really need the hot corner.
You should be able to do that throught the gnome-tweak-tool... it should be listed there along with your default extensions...
However if your case is like mine, you won't find the default extension there and will have to install one by yourself, I've installed the one below and the "No topleft hot corner" extension started to show up on my extension list...
https://github.com/HROMANO/nohotcorner/archive/master.zip
Also here's the thread where I've found the extension:
https://www.centos.org/forums/viewtopic.php?t=48130
I'm here today because I'm having an issue with Android Studio. I don't know if it existed on previous versions (I don't remember this being an issue, so I doubt it was a problem on a previous version), but currently I am using the Android Studio V2.1 Stable release.
My issue is that if I launch Android Studio (I happen to be on Windows, 64-bit Android Studio) and at the Start Screen/Page, I click Configure>Settings>Editor>Code Styles, and change the default parameters on any of the languages (XML, Java, HTML, etc.), the Default profile is copied to a new profile (Default(1)) and the new settings get applied to each profile.
If I Apply these changes and exit Android Studio, and launch back up and follow the same method...the settings have completely gone back to what they were before I changed them, with the exception of the Default(1) copy profile. But from my experience, Android Studio doesn't build new projects based on this Default(1) copy profile, it builds them on the Default profile. Which means all of my adjustments to using indents and not spaces, keeping indents on empty lines, etc. all do not get carried through to the actual project files, leaving me to have to go back into the settings with the project loaded up and change all of these parameters again. That's just asinine. Please tell me I'm missing something here and that there's a simpler way of achieving the ability to keep a code style template that I can use on all of my projects!
Perhaps it would be better to report or consult on this using the Android Studio feedback site. If that's the better option, I'm willing to do that too.
Thanks everyone!
What I do in that case is
Go to Preferences
Code Style
Select scheme you want
Click Settings cog
Click copy to project
Some OKs and then it works.
After selecting the code style that i want, opened the gradle.properties file in root folder of the project and deleted the following line
kotlin.code.style=official
deleting the above line, prevents the code style resetting to default.
Go to Preferences
Code Style
Set Scheme to Default [IDE]
Click restore defaults
The simplest way I found to reset the default settings is as follows:
In Android Studio, click on File.
Settings (Ctrl + Alt + S)
Under Editor in settings
Select Code Style
Next to Scheme: select the three dots to access the scheme options ()
Select Restore Defaults
A Confirmation Dialog Box will be displayed to confirm if you want to revert back to
the default settings.
I want to disable autocorrect in specific page of Edge Browser.
How can I disable autocorrect in Edge?
But I don't want to disable autocorrect of whole Windows10.
(example...Settings -> Devices -> Typing....This is not...!!)
You can solve this without editing the registry:
It's not about Edge but the whole win 10. Open
Settings from the start menu, then go to devices. There you'll find a
tab named Typing, fifth in the list for me, and the autocorrect
feature is displayed there. If you switch the autocorrect off, edge
will stop bugging your text (i actually wrote this in edge ;) ).
Enjoy. :)
Note: Currently open Edge windows will still auto-(in)correct until Edge has been restarted.
Another article in the link in Etiennes answer.
Apparently the menu is not available by default.
By reading the instructions here : http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/how-to-turn-of-autocorrect-typing-in-edge/6944dcc4-6ef4-4ec6-afaa-5a0ca08c3bd2?auth=1
You can follow this and it should work :
If for some reason the "Typing" tab in the settings is gone (It was for me) you can unhide it through regedit.
Use regedit and search for the following value: "ShowAutoCorrection". Change the value to '1' and you should be able to access "Settings -> Devices -> Typing" to change your autocorrection settings.
Restart your application, log in and out, or reboot your system to make the changes apparent. It worked for Skype at the very least for me.
I have found a solution, friends of Edge! Download the Tampermonkey MS Edge extension from the Windows Store and install the following UserScript:
https://greasyfork.org/de/scripts/39190-disable-spellcheck-globally
This UserScript sets the "spellcheck" attribute to the global element/tag of every website you visit so that Edge MUST obey the rules. This also fixes the issue of auto-correction.
If you want to limit it to a certain website just modify the "#include" tags, for example:
#include https://www.reddit.com/*
To disable spellchecking on reddit only.
You can get Tampermonkey here: https://www.microsoft.com/en-us/store/p/tampermonkey/9nblggh5162s
Works on Windows 10 build 17112.1
What I found to do it disable autocorrect in the new Chromium-based Edge, is to right-click on a word that has been autocorrected. It should list the original word with the option to restore it. Beneath that, there should be an option to either disable autocorrect for that site or permanently. Select your preference and autocorrect should stop bugging you.
Hope to be of help.
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.
To debug extensions, Chrome used to have a "Inspect popup" menu option available when right clicking the extension icon (top right in the browser). I believe this options was recently removed (possibly with the latest Chrome version 20, which I am using) .
The debug console can still be activated by right clicking any element in the extension popup and selecting "Inspect element". The problem I am experiencing however is that whenever I now have the debug console open, typing into form elements in the popup does not work. Even though the form element seems to have the focus (it has a blinking cursor active), all input typed goes straight to the debug console.
Update: It seems focus is not specifically to the debug console, but to whichever window is below. It's like the extension window is a "stay on top" window, without capturing any input.
Update: 2012-07-24: Updated to 22.0.1215.0 (Official Build 147830) dev and the bug is still there. But yay, Youtube full screen now suddenly works on my dual screen system!
Update 2012-05-09: Upgraded from 20.0.1123 to 20.0.1130.1 dev on Linux x64 (Ubuntu 12.04). Problem still there, and makes debugging extensions a lot harder than needs be. Also confirmed behaviour on older Chrome release (20.0.1105.0). Oh well, maybe it's just me...
Update 2012-05-09 2: Assuming this is a bug, consider adding a background page to your popup and log to that page's console instead until bug gets fixed. At least that makes my life easier for now.
Update: 2012-10-19: As omri writes (and points to), the Inspect Popup option is on it's way to be put back into Chrome, which will hopefully solve this problem (finally).
Could anybody confirm/deny this behavior, and/or suggest possible workarounds?
Open the popup
Right click the popup window and inspect.
Its going to be re-added to chrome
http://code.google.com/p/chromium/issues/detail?id=143349
Update: Un-accepting answer as another user confirmed this behaviour for OSX, so at least it will appear as unsolved on the radar, although there's probably a bug tracker somewhere where this needs to be posted.
This bug is still present on google-chrome-beta (Version 20.0.1132.34 beta). I'm guessing that this has to do with window and popup handling on X11 generally, and is obviously not a high priority bug since it's remained this way for quite a few releases. Closing question.
I am seeing the missing "Inspect Popup" option on right click but, I can edit/enter text in the form fields.
I am wondering if you are having an unrelated problem? If you are using or updating to the new 2.0 Extension Manifest you can encounter issues where inline javascript in the popup fails to fire any longer because of the addition of the content_security_policy defaults. Basically this prevents script injection but also seems to kill all JS in your popup. There are ways around this by changing the way events are handeled in your popup or by changing the default policy. Here's a link to the doc on this: http://code.google.com/chrome/extensions/contentSecurityPolicy.html
This is just a guess because I don't know what's going on in your code but I saw similar things while upgrading my extension recently.
Just upgraded to 22.0.1221.1 (Official Build 149058) dev and the problem seems to have been solved, albeit with a workaround. The old way of right clicking in the popup window and selecting "Inspect Element" to start up the console still grabs all input as originally reported.
However, it seems by right clicking the popup icon, the old "Inspect Popup" seems to be back, and when this is used it does not seem to grab input from the open popup window itself.