I just upgraded to Windows 11, and I'm experiencing an issue with PhpStorm's Vim emulator. When I hit certain key combos (E.g. Alt + Left Arrow twice) my Backspace, Delete and Arrow keys stop working. I checked my selected Keymap, and I was using the default Windows one.
What I've tried:
Reverting to default Windows keymap from my custom keymap
Using another keymap (like Visual Studio)
Turning off Vim emulator
None of these resolve the problem. The keymap normalizes for a bit, but then the issue occurs again and the keys stop working.
Anyone knows how to fix?
Related
I searched on Google, but nothing found , please how can I get the cursor format back on PhpStorm, now it is bold and large,
I'm using Mac Osx 10.11
Your answer is appreciated
In Preferences (Cmd-,) go to Editor -> General -> Appearance and uncheck "Use block caret"
I'm building a mobile application with Visual Studio 2013, using Ripple Emulator and Cordova.
Every time that I try to inspect an element (hitting Ctrl + Shift + I, F12 or right clicking the page and selecting Inspect element) the Google Chrome closes and Visual Studio stops running the application.
Has anyone know why I'm unable to inspect elements inside the browser using Ripple Emulator?
Ps: Visual Studio 2013 has his own DOM Explorer but the experience is not the same as the Chrome Developer Tools.
A simple workaround is to start your project without debugging (Ctrl+F5) from Visual Studio. This will allow you to use the Chrome dev tools (F12 and so on) without killing the VS debugger process and therefore stopping your Ripple session.
I've been having the same issue since upgrading to cordova tools update 3 with visual studio 2015 community edition - it was working fine before "upgrading"
I haven't found a reason why, but there is a workaround which is to start your debugging session (F5.. or whatever) then hop back to visual studio, then select "Detach All" from the debug menu. This, or use a different browser (Edge works fine in Windows 10, but I'm not used to it's interface).
Hope that helps.
There was a change in the chrome debugging API that prevents VS from inspecting the elements and changing the style. Chrome version 43 will work. You have to take some steps to keep it from auto updating. The installer for chrome 43 is here:
https://dl.google.com/chrome/win/4ED6DD719811795B/43.0.2357.134_chrome_installer.exe
You will need to uninstall chrome, update the registry, then install chrome 43. When you go to the about screen it should say updates have been disabled by the administrator.
Here are the registry changes:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
This thread has more information on the changes needed to the registry to prevent the auto update:
cannot stop Chrome from updating from 43 to 44
NOTE: this means you are not getting security updates on that install, only use this until the issue has been resolved in an upcoming patch.
I'm using PhpStorm 8.02. On Windows, it's ok, but on my mac, it's freeze 10 seconds when I click on a file for exemple (or even when I click on some menu).
I updated java JRE, but nothing change.
Solved.
It was a plugin (git-flow plugin). When I disabled it, all was fine.
I'm running tortoisehg 2.1.3 (and now 2.1.4) on a win7 x86 system upgraded from 2.1.2. When I click on the context menus (e.g. workbench) nothing happens.
I enabled shell debugging: [HKCU]\Software\TortoiseHg\ value DebugShellExt="1"
Which yielded: [THGx86] RunDialog: THG root is empty in DbgView.
I've manually checked that \Software\TortoiseHg\ default is "C:\Program Files\TortoiseHg" for both [HKCU] and [HKLM]. Though I'm having some problems where installing TortoiseHg seems to make these registry keys empty and unreadable and I have to manually change ownership on them to even delete them.
Anyone else having problems with these context menus in this version of TortoiseHg on windows? Anyone know if something has changed in the installer? Anyone know of something that could cause these registry keys to become inaccessible even to the application that created them?
It looks like the issues are resolved in more recent versions of TortoiseHG (2.2.1 and later). So, I'm marking this question answered.
I installed TortoiseHg (Mercurial) in my Vista 64-bit and the context menu is not showing up when I right click a file or folder.
Is there any workaround for this problem?
Update: TortoiseHg 0.8 (released 2009-07-01) now includes both 32 and 64 bit shell extensions in the installer, and also works with Windows 7. The workaround described below is no longer necessary.
A workaround to getting the context menus in Windows Explorer is buried in the TortoiseHg development mailing list archives. One of the posts provides this very handy tip on how to run 32-bit Explorer on 64-bit Windows:
TortoiseHG context menus will show up if you run 32-bit windows explorer; create a shortcut with this (or use Start > Run):
%Systemroot%\SysWOW64\explorer.exe /separate
(Source: http://www.mail-archive.com/tortoisehg-develop#lists.sourceforge.net/msg01055.html)
It works fairly well and is minimally invasive, but unfortunately this doesn't seem to make the icon overlays appear. I don't know of any workaround for that, but file status can still be viewed through TortoiseHg menu commands at least. All other TortoiseHg functionality seems intact.
The icon overlays are now working with TortoiseHg 0.6 in 32-bit explorer! Not sure if this is a new fix or if I had some misconfiguration in 0.5; regardless this means TortoiseHg is fully functional in 64-bit Windows.
In order to be able to use an extension in Explorer, the "bitness" of the extension needs to match the bitness of the operating system. This is because (at least under Windows) you can't load a 32-bit DLL into a 64-bit process -- or vice versa. If there's no 64-bit version of HgTortoise, then you can't use it with Explorer on a 64-bit Windows OS.
I upgraded to Windows 7 RC and the 64bit workaround seems to have stopped working
You could always install the command line hg and use it in a pinch. It's a bit faster, too.
I can verify that xplorer2 does show the HG tortoise context menu in 64bit Vista.
As detailed in the TortoiseHg FAQ, you need to run a 32-bit Windows Explorer instance for the context menu and overlays to work under 64-bit Vista.
My personal preference is to create a shortcut similar to the following for each project I'm actively using with TortoiseHg:
%windir%\syswow64\explorer.exe /separate /root,C:\projects\frobnicator
This launches explorer with the C:\projects\frobnicator folder already opened. (You can omit the /root option and just use the same shortcut for all projects if you don't mind clicking your way to the target folder every time you launch it.)
According to the TortoiseHg FAQ the context menus will work in 64-bit Vista if you start a 32-bit instance of explorer by creating a shortcut with the following settings (as suggested in the answer above):
Target: %windir%\syswow64\explorer.exe /separate
Start In: %windir%\syswow64\
I've just noticed that the context menu and icons work from a file open dialog from some apps (on Vista). I now just use Notepad++'s file open dialog, since I use Notepad++ all the time.
It seems to have to be the simple open dialog, not the new one Notepad has, for example.
Maybe someone can check if this trick works in Windows 7.