I was doing work on a Latex project and when I closed the emacs at the end of the day and opened it again. It appeared that the font had heavily separated by what I believe are spaces. I am very intrigued about where this sudden change to fonts could have come from, I have been using emacs for about 2 weeks or so, and when I started working on Latex projects today the fonts became like this after closing the client, and then reopening it again.Picture of the spaced-out font view.
Here's the doom emacs Doctor output:
❯ ~/.emacs.d/bin/doom doctor
The doctor will see you now...
> Checking your Emacs version...
> Checking for Emacs config conflicts...
> Checking for private config conflicts...
> Checking for stale elc files...
> Checking Doom Emacs...
✓ Initialized Doom Emacs 2.0.9
✓ Detected 29 modules
✓ Detected 118 packages
> Checking Doom core for irregularities...
Found font material-design-icons.ttf
Found font weathericons.ttf
Found font octicons.ttf
Found font fontawesome.ttf
Found font file-icons.ttf
Found font all-the-icons.ttf
> Checking for stale elc files in your DOOMDIR...
> Checking your enabled modules...
Everything seems fine, happy Emacs'ing!
✓ Finished! (0.7816s)
The problem was solved by deleting everything inside .fonts/ directory. Though this also leads to my terminal(Kitty) to malfunction since it looks like it depended on that .fonts/ directory.
Related
I'm a noob at setting up LaTeX and I'm completely stuck. I had a broken MikTex + TexStudio setup that the previous owner of my work computer left behind (I also mention that I recently upgraded from Windows 10 to Windows 11). Unable to fix it, I decided to just wipe out everything and start clean. I uninstalled TexStudio and MikTex (also deleted all the files in AppData, etc.) and I installed TexLive (and gave the PC a restart as prescribed) to use it in VS Code (which I already had). All the guides I found say that once I install the LaTex Workshop extension in VS Code, everything should work on it's own (or at least no one mentions that there are problems that could arise).
However, when I try to compile a tex file I get the following error:
11 [0x00002528] INFO latexmk null - this process (19956) started by 'Code' with command line: latexmk -synctex=1 -interaction=nonstopmode -file-line-error -pdf "-outdir=c:/Users/.../texfile_locationfolder" "c:/Users/.../texfile"
It seems that this is a fresh TeX installation.
Please finish the setup before proceeding.
For more information, visit:
https://miktex.org/howto/install-miktex-win
The fact that it mentions MikTex makes me think something messed up and VS Code is trying to use MikTex instead of TexLive. How can I fix this?
PS: I've tried to look at the settings for the VS Code extension, but there are dozens of settings options and, fairly enough, I don't have any idea what most of them do.
I found a fix: I went into the Environment Variables list and found that MikTex was still in there. After deleting everything related to MikTex in the PATH Environment Variables, all was working well. Yeey!
I had the same issue (on Windows). Resolved by deleting a MikTex folder, found by searching for MikTex in File Explorer.
Then, I deleted this folder from the recycling bin and restarted my computer. LaTeX Workshop detected TeXLive and works as expected.
Netbeans 12.1 no longer respects the --fontsize directive in the /etc/netbeans.conf config file.
The menu fonts are way too small on a large screen.
Yet setting Preferences->LXQt Settings->Font->Point size in the Ubuntu control menu, which is normally respected by most Unix app windows, does not carry through either.
And although Netbeans's
Tools->Options->Fonts & Colors->Profile: NetBeans->Syntax->All Languages->Default -> Font
setting changes the font for the code itself inside the editor, it doesn't change the IDE menus.
You would think, after all these years, that there would be a command inside the Options to change the menu font size, but it's still not there yet.
And now editing config to change the --fontsize startup option is no longer respected.
How best to change the size of all the system fonts in the Netbeans IDE display environment?
The best solution I've found so far is to change the Look & Feel.
Invoking aptitude install netbeans currently (Sept '20) gives version 10, which breaks with a jcraft/jsch error, also "could not successfully run the /usr/bin/g++ compiler" on my system even though g++ is perfectly fine and protections cleared, also "Build Host not connected", after C++ is installed from the 8.2 repository. Tastes like some kind of jdk error (I've got /usr/lib/jvm both 8 and 11 jdks installed, hard to believe it can't find them). But if the install doesn't work right out of the box, it's a bad sign. So I tried snap install netbeans --classic . This gets version 12.
Netbeans version 12 comes with the Metal Look & Feel configured by default. Changing this to the GTK+ look and feel, using Tools->Options->Appearance->Look and Feel->GTK+ with a restart, finally got the menus to the correct system size.
Unfortunately, the Help->About popup still does not respect this, having minuscule fonts. Perhaps there is a better way?
Although "Look and Feel" is an improvement, I would still like to see direct control of the IDE menu fonts. From the Options Fonts & Colors menu.
Running netbeans from commandline with an additional argument --fontsize 12 works for me. Open a console and go the bin directory of netbeans and use the command ./netbeans --fontsize 12. Change the font size to whatever suits you.
In Netbeans in Tools->Options->Appearance->Look and Feel, I could solve the problem.
But in my case, the selected option already was GTK+. Changing to Metal solved it.
Install Netbeans 13.
It should help
I am working on a server which uses a really old emacs. The only way to install plugins is by downloading the .el files and adding them to the ~/.emacs/ folder and then sourcing it from the main .emacs file. Would someone know of a C/C++ autocomplete plugin which works with Emacs 21? I tried auto-complete-mode but I get an error.
An error has occurred while loading `/home/sbhalla/.emacs':
Symbol's function definition is void: defvaralias
The same auto-complete-mode works fine on emacs 22.
You might be able to run Emacs 24 without root access:
Download and untar Emacs 24: http://gnu.mirror.iweb.com/emacs/emacs-24.5.tar.gz
./configure && make. It may tell you to disable some options, e.g. I had to compile ./configure --without-jpg --without-png
You should be able to run ./src/emacs
I've done this to get the latest version of Emacs on university machines without sudo access, so it could probably work for you too.
i have a few keys that i prefer to force-bind to keys i'm familiar with, and so i have used this SO Solution .
but i have found recently that it breaks for me.
the circumstances: it works fine when running 24.2.1 in window mode as build 2012-08-27 on bob.parkland.org (i.e. the pre-build emacs-for-mac solution found at http://emacsformacosx.com/).
but then it will not work when run in terminal on lion, which is 22.1.1 (mac-apple-darwin) of 2012-01-12 on b1006.apple.com .
if i comment out the call to add the hook, it works fine.
the problem is partly that i byte-compiled the code found at the other link above into a separate loadable .elc file … and did so with the newer version of emacs.
when i go back to the 22.1.1 version of emacs and byte-compile it with that version, it works in both versions of emacs without problems.
Since some time (but I didn't change anything in .emacs), I have some errors with emacs's behaviour :
Remember mode will not kill the temporary buffer on "Ctl-C Ctl-C"
Orgmode will not refile any entry
Both operations complain with error "Not bookmark format"
I restored an old .emacs to make sure that I didn't mess it up but the error persists.
Where can I investigate to find out the problem ?
I have Emacs 24.2.1 since end of august.
The built in orgmode version is 7.8.11 (I see 7.9.2 is out ...)
It's always best to start debugging problems such as this by seeing if the problem still happens when you ignore your init file altogether - try starting emacs with --no-init-file and seeing if you still get the problem. If you don't then it's clearly something in your init file.
You can also get odd behaviour if you've got a local install of Org-mode in addition to the one bundled with Emacs itself - eg if you pull in a newer one through ELPA. If you have a local install through ELPA then you can try uninstalling the Org-mode package and trying again using the built-in Org-mode.
I have something similar to the following in my init file to make it switch to the ELPA-installed Org-mode to avoid such problems (this variant is untested so forgive me if it's not quite right):
(package-initialize) ; load and initialise ELPA-installed packages
(org-reload) ; restart Org-mode with the ELPA package
I filed a bug to the emacs team and they found out that the error comes from a corrupted bookmark file.
I removed my ~/.emacs.d/bookmark file (it was empty) and everything is fine now.