i've been using VS-Code for years now. And i've been loving the One Dark Italic theme.
Now i've switched to IJ. And the first thing, i did, was installing the theme... however. It is not working correctly.
Code in IJ
It should look like this
Code in VS-Code
Anyone who can help?
Regards
You have to reinstall the IDE. You can save the config file, to keep your settings.
If you dont know how, here is the link (for windows and linux)
https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs
I have seen many people using this type of fonts..
I always wanted to use this fonts in my vs code..
If you want to use this type of font. You can choose two style which are (Operator mono iirc or Fira Code).
I will just show you how to download and setup Fira Code which will give you experience like the image that mentioned in your question.
Go to Google Fonts then download Family and a zip file should be
downloaded on your Machine.
Unzip the downloaded font zip file. Then Click on
install to install into your Machine.
In your Visual Studio Code
Go to File > Preferences > Settings and search for downloaded font which is Fira
Code.
Notice : If you did not see effect of the new font. You might need to restart your Machine to see effect.
Tip : You might want to enable font ligatures. it also makes font looks better.
A big Thanks for #solexy79 in (https://dev.to/solexy79/installing-a-new-font-for-vs-code-in-three-3-simple-steps-13a5).
A Big Thanks for #somerandomdev49 in comments.
Sorry if the question is bit silly, but on Ubuntu 16.4 I am trying out code editors for Angular 2. VS Code appeals because of TypeScript. But when I open a location the directory name in File Explorer is in ALL CAPS even though I don't use CAPS in directory names? Googling didn't help. Perhaps I am missing something.
How can I change it show my directory name exactly as it is in Ubuntu please? I have tried to look into settings.json etc but no joy.
Cheers.
if you mean this (see the image below), that would be a standard behaviour and has nothing to do with actual size of the letters. As far as I can tell, you cannot change this.
Well I went to GitHub as suggested but they have sadly declined (click) to do anything about this as some "as designed" thing, whatever that means. Pretty bad, but okay whatever.
Use this to customise. https://gist.github.com/Hendrixer/7a250a2be529cda8939de8305c9a85a1
It's just another chromium based renderer. Open developer console and customise anything you like.
I'm currently trying to set up my working environment in Ubuntu 12.10, and I'm currently lost with the styling of Javadoc in Eclipse. The tooltips, and the Javadoc shown in the Javadoc perspective are not rendering the HTML correctly at all.
This is what it looks like on my Windows 7 installation of Eclipse:
On Ubuntu, it looks completely broken and is not rendering anything correctly, which gets especially distracting when there is lots of text, code or other things included into the Javadoc:
Has anyone experienced this kind of issue before or might be able to help otherwise?
Note: I also changed my gtkrc up a bit to change the tooltip color, as it used to be just really dark text on black background, but that should have only changed the general font and background color, not the rendering of HTML.
I just found this very related question:
Eclipse is formatting javadoc tooltips very poorly on Ubuntu
However, noone there was able to answer the person asking the question
Had the same problem- Solution is easy: Install the libwebkitgtk-1.0-0 package available in the default ubuntu repositories.
(If you're not using Ubuntu find out how that component is called on your distro and how to install it)
The challenge:
Provide dynamic web fonts that render acceptably across all major browsers, devices and Operating Systems
The story:
So I had used cufon or sifr in the past and had since abandoned both in favor of #font-face. After using #font-face in production for some time, I made a horrifying discovery. Many fonts (most?) look like crap in Windows XP, regardless of browser. Even in google chrome, XP renders the fonts unacceptably jagged and ugly.
I am aware of why this is happening. After reading many excellent posts on ye olde stack overflow, I understand the issue is NOT of font hinting, but of XP having clear-type set to off be default. So ALL fonts are jagged in XP by default regardless of application.
So... if #font-face works great everywhere BUT XP with clear-type off, and is still superior to cufon what should we be doing?
Possible solutions:
#font-face as default, Cufon with user agent sniffing for windows XP.
(currently using, and very much not loving it)
#font-face alone with yet unknown method of forcing clear-type
Cufon alone :(
Another paradigm all together
Failed solutions:
Adobe Typekit (jagged in XP on their own website!, even though they show a smooth specimen jpeg)
Google Webfonts (same problem with XP)
#font-face alone (same problem with XP)
Cufon so far works everywhere, but just sucks, and offers additional challenges if you are animating anything, or wish to update the text after the fact.
Do you have a solution that works completely cross browser and cross OS? What is the best way to handle this?
I'm pretty sure the web-fonts, which look ugly, are missing some hinting (edit: Nope, even though hinting is still required to make a font look good on windows, the real problem here was the disabled ClearType in XP. However, this answer has a solution anyway).
Unlike font renderers on other operating systems the windows engine relies on hinting information shipped with the font. If the hinting is missing, bad or broken the font will look ugly - simple as that. Luckly there's a way to add some automatically generated hinting to a ttf-font using ttfautohint. After adding the hinting you can generate the different web-font-formats (eof, woff, etc) you need from the enhanced TTF. Additionally you should try to use SVG fonts if font-smoothing is disabled, since they are always rendered with antialiasing.
I've written an article on how to create web-fonts on Pixels|Bytes, which explains how to add hinting to a font and how to use my Font Smoothie script to enable SVG fonts when necessary. Hope this helps :)
PS: I'm aware that linking to my own blog won't be appreciated here, but I think my post describes a good solution to the problem, so I posted it anyway. Please leave a comment if you want me to remove the link and I'll do so.
http://www.useragentman.com/blog/2009/11/29/how-to-detect-font-smoothing-using-javascript/
This is what I have found works so far. This solution detects jagged fonts, so then we can do something like this: #font-face as standard, and Cufon as fallback.
In my case, I found that the answer does not in fact center on enabling Clear Type in WinXP. Whether Clear Type is enabled or disabled, I find that some of my #font-face English fonts (especially BLACK, SANS-SERIF) look bad in IE7 and IE8. It's sometimes more than just being jagged or having bad anti-aliasing. The big problem I see is that the shape of the font itself (some fonts, not all) seems to squish into something quite unattractive. I found an acceptable solution by following the advice of Torben. Font Hinting was all I needed, and again, that solution has nothing to do with Clear Type being enabled. To get the font hinting app up and running, read the instructions here:
https://gist.github.com/davelab6/3783491
(I used the "ttfautohint-0.95.tar.gz" file here): http://sourceforge.net/projects/freetype/files/ttfautohint/0.95/
You should also review the documentation, and you need to also install MacPorts (or you will get an error in the Terminal during your build), but since my rep score prevents me from posting more than two URLs, you'll have to Google for that.
Better hinting doesn't mean your #font-face fonts will now look as perfectly smooth and great on IE in WinXP as they do on Macintosh browsers. But I found that the font hinting prevents nasty distortions in the shape of some fonts within IE7 and IE8. To me, that is an acceptable solution.
I can only add that it's rather troublesome to build the ttfautohintGUI on OSX. You have to installed hundreds of MB of software, downloading from multiple locations too, just to build the GUI app. But once done, the app allows you easily to hint your #Font-Face fonts and resolve many WinXP display issues. Just be sure to tick "Windows Compatibility" in the GUI (it's unticked by default). I also unticked the "Add ttfautohintinfo" and "Pre-hinting" options, leaving everything else as their defaults. Click "Browse..." to add your Input File (the font you want to hint), and then copy and paste that path in the Output File, changing the filename to whatever you want it to be. You won't enable the "Run" button unless there is something in both the Input File and Output File fields.
Best wishes.