I have a .doc file include math equation and open by Libreoffice 5.0 in Ubuntu 16.04 but some equation (integral sign) display incorrect:
Incorrect display integral sign:
Incorrect display other equation
I also open by Libreoffice 5.0 in Windows 10, it worked correctly.
I also copy all font from Windows 10 to /usr/share/fonts/FontsWindows in Linux
Could you please help me to find any solution for that.
Thank you so much for your support.
Do your new fonts show up on the system?
Eg
fc-list
If not
sudo fc-cache -fv
OR
sudo fc-cache -fv <new font dir>
Also check your
~/.fonts.conf
All the best
Related
I'm trying to use customtkinter. i downloaded the examples and when i try theme, all the elements have a strange shape enter image description here which don't look like the screens of the examples on github.
I searched on google but didn't find a way to solve this.
I use
Ubuntu 22.04
Anaconda
tested on Python 3.8 and python 3.10
the customtkinter (V5.0.3) was installed using pip
I tried two different versions of python, tried reinstalling the lib
was expecting elements with this kind of shape https://github.com/TomSchimansky/CustomTkinter/blob/master/documentation_images/image_example_dark_Windows.png
Well apparently it's a known bug with anaconda and there is no proper solution yet. You can find the bug report here https://github.com/ContinuumIO/anaconda-issues/issues/6833
An ugly workaround wich actual works is to replace your conda env libtk8.6 by a symlink to system libtk8.6:
cd [Your_conda_env_path]/lib/
mv libtk8.6.so libtk8.6.so.old
ln -s /usr/lib/x86_64-linux-gnu/libtk8.6.so .
I'm trying to integrate zsh on my VSC setup but apparently arrows are not recognized by it.
My zsh theme is agnoster and I've already tried adding "terminal.integrated.fontFamily": "Meslo LG M DZ for Powerline" with no success. Anyone experienced something like this and can give me a hand? Thanks.
Following this little guide solved the issue making-powerline-work-in-visual-studio-code-terminal.
IMPORTANT: if you already have a powerline font installed (e.g. it looks fine inside your system terminal), skip step 1.
Install a patched version of your desired font directly from https://github.com/powerline/fonts. Apparently doing the "quick installation" (e.g. sudo apt-get install fonts-powerline) does not work in this case. So you can install manually downloading the .ttf file directly or running the install script ./install.sh provided. For instance you can do the following:
Clone the repository:
git clone https://github.com/powerline/fonts && cd fonts
Run ./install.sh to install them all or install one specific font by going inside its directory and opening the .ttf file. For instance, manually installing DejaVu Sans Mono for Powerline:
cd DejaVuSansMono
Open DejaVu Sans Mono for Powerline.ttf
Install the font
Add the terminal.integrated.fontFamily to your User Settings settings.json in VSCode specifying the powerline font to use. For instance, if I want to use DejaVu Sans Mono for Powerline:
{
[...]
"terminal.integrated.fontFamily": "DejaVu Sans Mono for Powerline",
[...]
}
Restart Visual Studio Code
For me it worked for linux and as well as manjaro (i don't know why others solution weren't working for me).
Download this font download font from here , Then create a folder named "Meslo" and extract all the fonts inside it.
Move this folder to /usr/share/fonts/truetype/
Run this command:
sudo fc-cache -vf /usr/share/fonts/
In settings.json of vscode add this line:
"terminal.integrated.fontFamily": "MesloLGM Nerd Font"
Save and Restart if necessary, it should work. Done.
Finally made it work after going through many blogs and GitHub comments. The below steps works for macOS.
Clone the Menlo for powerline font
git clone https://github.com/abertsch/Menlo-for-Powerline.git
Open this folder in finder. Double click on Menlo for Powerline.ttf file.
Click on Install Font
Open the settings.json file in VSCode and add the below line.
"terminal.integrated.fontFamily": "Menlo for Powerline"
If you still can't see the fonts in the terminal try restarting VSCode.
You can use the above steps to use any font you want.
I had the same exact issue on my Macbook. The problem was that the font I was using in Iterm was not added in the Terminal of VSCode.
Fix
fix was simple, you have to go to open Iterm -> Preferences -> Profiles -> Text and copy the Font Name
now head over to VS Code:
Open settings
In the search bar, type Terminal Font
Paste the font name in Terminal > Integrated: Font Family
and that will fix the issue for you!
If you already have a font installed which is looking fine in your terminal app (for example in iTerm2) and the font is just messed up inside VSCode, you don't have to install any additional fonts. Just add:
{
...,
"terminal.integrated.fontFamily": "YourFontName"
}
to your settings.json
where YourFontName is the name of the font you would like to use. On macOS you can see what fonts you have installed in your font book (search for font book in the spotlight Command + Space) which looks like this:
In my case my settings.json has the following entry:
{
...,
"terminal.integrated.fontFamily": "MesloLGS NF"
}
Yey! This works for me... Ubuntu 20.04
Key: Shared fonts think.
https://cloverinks.medium.com/oh-my-zsh-agnoster-theme-not-showing-correct-font-on-vscode-ubuntu-47b5e8dcbada
Most of the other answers didn't solve the issue for me in Manjaro Linux (KDE).
I eventually found a solution that made the Powerline glyphs visible in my VS Code zsh terminal:
https://forum.manjaro.org/t/kde-powerline-glyphs-missing-in-vscode-integrated-terminal-only/63742/3
Just set the font to NotoSansMono Nerd Font. This font was already installed on my system. I did not need to download any additional fonts.
There are two ways to change the font in VS Code:
Change the following line in settings.json:
"terminal.integrated.fontFamily": "NotoSansMono Nerd Font"
Alternatively, go to Settings -> Features -> Terminal and set Terminal > Integrated: Font Family to:
NotoSansMono Nerd Font
You may need to restart VS Code.
I had the same problem with my VS Code, WSL terminal (PowerLevel10K) on Windows 10. It looked exactly like yours. I found that my Terminal>Integrated:Font Family was named incorrectly. I use "DroidSansMono Nerd Font". I had entered it as "Droid Sans Mono Nerd Font".
That is not the way the font name shows up in programs like Word, Notepad or Photoshop. When I entered as it was shown in notepad,
I closed and reopened my VS Code terminal and everything rendered as expected.
So check your installed font name in your operating system's word processing software and see how it is listed. Enter it likewise into Terminal>Integrated:Font Family and your VS Code terminal should render correctly also.
In manjaro, install MesloLGS fonts and change the setting to"terminal.integrated.fontFamily": "MesloLGS NF"
in settings.json
while the font path is ~/.fonts
I am trying to use RStata in order to run Stata from R. I first did:
options("RStata.StataVersion" = 14)
That didn't cause an error.
But I also need to set the binary path. I have a Mac, and Stata is contained in a folder in the Applications folder. Here is what I have tried:
options("RStata.StataPath" = "/Applications/Stata/Stata")
Unfortunately, this causes an error. What should I do?
With no knowledge of RStata, I can say that on macOS 10.12.6 with Stata/SE release 15 installed, in the terminal window
open /Applications/Stata/StataSE.app
is what's required to launch Stata. It is possible that in looking for the Stata executable, your Finder Preferences does not have "show all filename extensions" set in the Advaced pane, so you weren't shown the .app extension.
From the README, better rendered here
Mac users are a notable group: at this stage they should set the path
for the command line executable (not the GUI app). Eg for a Stata13 SE
installation in El Capitain (with default options) the path is
'/Applications/Stata/StataSE.app/Contents/MacOS/stata-se'. In other
cases (Stata licenses, installation path and so on) the path could be
slightly different (BTW, i've found the path 'exploring' the
filesystem with a terminal, not the graphics explorer since it 'stops'
at 'StataSE.app').
(yes, putting something in the manual as well is in my TODO :) )
hth, best, Luca
I haven't been able to find the help I need on (on dummie level) for installing a new dictionary (danish) in emacs. To be honest I somewhat confused about ispell vs aspell. When typing "M-x ispell-buffer" a spelling control starts using english as default. I can change directory typing "M-x-ispell-change-dictionary" it suggest "dansk" but I get an error saying that the file /.../aspell/dict/danish" can not be opened for reading. I can deduct that the dictionary is not installed - but I cannot seem to finde a guide (step by step) on how to do this.
And then I have a bonus question. I have managed to install flyspell (or is that actually 'installing' as I have just addet the .el file to my emacs load path and loaded in my .emacs file?). This seem to work (wauw), and as I understand it flyspell is using the same dictionaries as ispell/aspell hence solving my probleme above would enable me to use flyspell in danish?
Any help is appreciated.
/Kira
If you are on Ubuntu or Debian system you can install the Danish aspell package from the commandline with
sudo apt-get install aspell-da
Where does the Arduino IDE save the binaries on Mac OS X?
In the Arduino software: go to File -> Preferences and then select Show verbose output during -> compilation.
Finally, when you are compiling, the program will show you lots of data. At the last lines, you will find the path1 to the .hex file.
1Every time the path changes!
Arduino 1.6.5 has a new command: Under the Sketch menu, select Export compiled Binary, then Show Sketch Folder. There it is.
Arduino IDE uses the mktemp command to create the temp directory on Mac and Linux. However, on Mac the default $TMPDIR env var is not /tmp/ as it is on Linux. On Mac it's under /var/folders and it is randomly generated on boot. That complicates things a little, but here are tricks you can add to your toolkit (as aliases, functions, shell scripts, etc.) to help you find what you need.
To find the hex files
find $TMPDIR -name \*.hex -exec ls -lrt {} \; #<-- you need that backslash before and space after the semicolon
To find build directories
ls -ldrt $TMPDIR/build*
NOTE: The ls flags of r and t cause the listing to be "reverse" sorted by "time" respectively. This means that the newest will be on the bottom.
What UDalillu said. The trick also works on Windows. On XP it ended up in C:\Documents and Settings\Your_User_Name\Local Settings\Temp\buildxxxxx\ (the xxx number changes for each build, pick the most recent).
The arduino web page http://arduino.cc/en/Hacking/BuildProcess
described
During a "Verify" the .hex file is written to /tmp (on Mac and Linux) or \Documents and Settings\\Local Settings\Temp (on Windows)
I am using fedora19 64bit, and when i check my /tmp the build directory created is
/tmp/build8102....tmp/
I made a simple tutorial here with images
It is very beautifully explained in the following blog
Where to find Arduino Hex files or Output Binaries
I hope this helps :)