I am using the latest PhpStorm 2016.3 on Windows. While editing a markdown file, I noticed there is a preview window (that I am fairly sure is new, but it has been awhile since I edited markdown). Unfortunately, it looks like this, where the right side preview is unreadable:
I have set up Settings->Editor->Colors and Fonts->Font to be Source Code Pro, size 28 long ago to handle my 4K monitor. And I found Settings->Editor->Colors and Fonts->Markdown where I can change the look of the left side, but not the right. So I have two questions:
Is anyone else seeing this (standard or 4K monitor)?
Is there a setting that I can change?
OK, so I found out that JetBrains has a plugin named "Markdown Support", so it is important to make sure only that plugin is installed by checking Settings->Plugins.
I was using a third-party plugin before and I believe it was turned off automatically during upgrade. When I tried to turn it back on, and restarted PhpStorm, a prompt appeared indicating the two plugins were incompatible and I had to choose one, so I chose the JetBrains plugin.
Then, Settings->Language & Frameworks->Markdown->Preview, change the Preview browser field to JavaFX WebView. And the preview pane is back to the land of readable fonts.
Related
I tried to follow these guidelines — https://github.com/Adobe-CEP/Getting-Started-guides — to build an extension for Adobe InDesign 2021 (macOS Big Sur). I was able to make my panel (EvoDesigner) show up but no contents appear in it. I also tried to install a sample extension — https://github.com/Adobe-CEP/CEP-Resources/tree/master/CEP_9.x/Samples/CEP_HTML_Test_Extension-9.0 (also tried it with CEP_10) — but it happens to have the same problem. Any thoughts on how to solve this problem?
Thanks a lot!
I solved the problem by activating debug mode for the other vesions of CSXS I had installed (9 and 10). Turns up, at the time, I had only activated debug mode for version 8, just as exemplified in this tutorial.
So, to solve it, in the terminal (Mac) I typed:
defaults write com.adobe.CSXS.8 PlayerDebugMode 1
defaults write com.adobe.CSXS.9 PlayerDebugMode 1
defaults write com.adobe.CSXS.10 PlayerDebugMode 1
Trying to create a Live Template in PhpStorm by highlighting a block of text, going to Tools > Save as Live Template.
When I do this, nothing happens. The Live Template dialog does not open and there is no other indication of an error. I can manually open the Live Template menu and add one there.
Is there a setting or configuration that is needed for this to be enabled?
PhpStorm 2017.1.4 on Windows 10
You can turn a highlighted block into a live template, but you need to make sure that there is no leading whitespace in your selected text, or it won't do anything, as explained in the original question.
This is likely a bug, see the issue in the comments to track resolution.
My chrome browser is zoomed in for no reason. I tried added /high-dpi-support=1 /force-device-scale-factor=1 at the end of C:\Program Files (x86)\Google\Chrome\Application\chrome.exe however I am getting an error saying high-dpi-support=1 /force-device-scale-factor=1 in the target box is not valid. Make sure the path and file name is correct.
If your target is not valid, you probably forgot the quotes when using a path containing spaces (like program files) and the slashes:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /high-dpi-support=1 /force-device-scale-factor=1
Zooming out is just a workaround - not a solution !
I had the problem too, and I tried those solutions listed on this site:
http://techdows.com/2016/10/fix-chrome-54-looks-zoomed-in.html
However, I could not set the compatibility mode since all options are greyed out (probably company policy) and so I had to use the command line option.
Using both /high-dpi-support=1 and /force-device-scale-factor=1 did not work, my guess is that I am using a laptop and the default DPI level is set to 125 in Windows 10. If set to 100, most programs were too small to use.
Using only /force-device-scale-factor=1 worked for me (keeping my 125 DPI in Windows and 100% Zoom level in Chrome)
Recently, I am also facing the same problem when updating the latest version of google chrome. Do it again because this the only solution.
Delete your old shortcut code and create latest version shortcut code. And Follow this steps.
For Chrome:
Right Click the chrome icon or chrome shortcut icon, go to the
properties.
Then in the "Target:" field, Click the field and press end button.
Now you are seen this "chrome.exe" at the end.
copy this text : chrome.exe" /high-dpi-support=1
/force-device-scale-factor=1 and paste on chrome.exe"
Then Restart chrome or close the browser and double click the
shortcut icon.
For Firefox: here
I have been having the same problem thanks to the most recent Chrome update, tried a number of solutions but nothing worked, so looked for a way to go back to the previous version - which I have done an now everything is back to normal :)
So the insructions to roll back to a previous version can be found here: https://productforums.google.com/forum/#!topic/chrome/UFSYuIr1-80
However they are a bit long winded, so here is what I did.
Go Chrome's file location, should be something like C:\Program Files (x86)\Google\Chrome\Application.
Once there you should hopefully see a folder containing the previous version of Chrome - it should be something like 53.0.2785.143.
However, what's missing is the Chrome.exe, so we will need to get hold of this by downloading the older version of chrome again.
To do that you will need to go to this website http://www.chrome-portable.com/index.php/google-chrome-offline-installer and download the corrosponding installer, in my case i clicked on the link for the 53.0.2785.143 32-bit version.
Once it downloaded, right click on it and use WinRar (or similar) to 'extract here" - once extracted you should be left with another compressed file called "chrome". Again click on it and choose "extract here". This time you should get a file called "Chrome-bin".
Look inside "Chrome-bin" and you should see chrome.exe, now all you need to do is copy chrome.exe back to your older version folder (from step 2).
Double click on your newly copied chrome.exe and all going well Chrome should open back to how it was!
One final step, you will need to copy the entire 53.0.2785.143 folder to somewhere safe, other wise chrome will overwrite it again as it updates.
NOTE: So what you now have is two versions of chrome, the older version, version 53, which should look fine. And you have an the most recent version, version 54, of chrome which will continue to update etc. Any bookmarks you have will still point to the current version 54 chrome, so you will need to create new bookmarks pointing back to the old one!
Hope this helps, as I said I just followed the instructions in the link at the top of my post.
Good luck!
You can fix it by Holding ctrl and scrolling back
Or hold ctrl and press -
You could also change it in settings
Open Google Chrome.
Click Customize and Control Google Chrome >
Settings.
Click on "Show advanced settings" and scroll to the "Web
Content" section.
Use the menu next to "Page Zoom" to make your
selection:
Here is how to do it in the registry:
Add --force-device-scale-factor=1 to the registry keys
HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command
HKEY_CLASSES_ROOT\Applications\chrome.exe\shell\open\command
Note: The first key may be reset sometimes. I assume this happens with either a Chrome or Windows update; I can't tell.
Currently, when editing HTML files, I preview them using the following mapping: nnoremap cc :w <CR> :!open -a /Applications/Google\ Chrome.app %<CR><CR>. However, this always opens up a new tab. Is there any way of mapping such that a new tab is only opened if the currently edited HTML file has not been opened in your browser yet, and refreshes the page in which your HTML file has been loaded otherwise? Thanks.
There is AFAIK no way to tell Chrome to refresh the current tab from the outside.
But, you can try one of the many extensions that provide automatic reloading:
LiveReload
That one never worked for me and requires too much fiddling.
Tincr
That one used to be fantastic but suddenly stopped working a few Chrome versions ago. Worth following, though.
LivePage
That one has a simpler design than the two above. It has been working perfectly for me as a replacement for Tincr
You can also deal with the situation from the other end with Prepros, a great HTML/CSS/JS preprocessor that, among many other useful features, does live preview.
Due to various reasons I'm unable to use Prepros everywhere so my current workflow involves Koala for the pre-processing — which runs everywhere I need it to run —, LivePage for live refresh and… no mapping in Vim.
--- edit ---
Your question is about Chrome, but I thought it would be useful to also mention Auto Reload, a Firefox extension similar to the ones listed above that works beautifully.
--- end edit ---
Every other website I visit, the inspector works as expected:
But in many of the sites I'm editing within apache server (using xampp) somehow they doesn't show the "filename.css:lineNumber" data
Also, every change I try to do in the inspector in thse sites, doesn't do anything to the code shown in the source tab.
I've tried refreshing, hard refreshing with cache, closing and opening the tab, closing and opening chrome again. The same problem occurs.
In other sites the inspector works well, but not in many of the localhost sites.
Has someone experienced this before? Is there a way to fix this?
If you are using a client-side CSS generator library such as Lea Verou's excellent -prefix-free or client-side Less, you will not see source information as it has all been processed and reinjected as style elements.
Client-side Less has a property [dumpLineNumbers] to include source line info as a comment in the generated source. (I'm not sure if this will display in Chrome's inspector - but I think it might)
The only "fix" I know of for -prefix-free is to temporarily remove it, obtain the source info for reference, then put it back in.
I have had the exact same problem (not using a css generator), and it appears to be a known bug with the current version of Chrome, the solution is to use the more up to date Beta version known as Chrome Canary - Here's the link :)
https://www.google.co.uk/intl/en/chrome/browser/canary.html
Try to check what the format of your CSS file is. I had the same trouble with the UNIX and Macintosh formats. For example, try to open you CSS file in Notepad++ and in the bottom right corner of the window you'll see your current format. If you see UNIX or Macintosh there, click it with the right button of your mouse and change to DOS/Windows. Then save your file and refresh your page in Chrome. It definitely helped in my case.enter image description here