I am trying to figure out why I cannot send anymore emails in Emacs and mu4e package and gnupg tools for encryption. Although it worked flawlessly for a while it suddenly stopped. I have this error now:
apply: Searching for program: No such file or directory, /usr/local/bin/gpg1
To save an answer for other users. I installed gnupg21 following all instructions on unlinking other versions of gpg versions on my machine, and killed an agents with this gpgconf --kill gpg-agent this seems to fix the problem.
Related
I wanted to update my Visual code studio theme I've created when I went to my terminal to update my theme. I put in the words. Yo code is showed an error that it couldn't be installed or found. I have installed the generator a few weeks ago. When I tried to reinstall it it told me to install it as an administrator, I did that when the process is complete I entered the same word. Yo code did not work so I decided to delete it all together, then reinstall it, but it didn't work. I have node installed and MPM I did the procedures correctly, but the generator does not work at all.
I tried reinstalling the generator, through node and NPM both as an administrator, but it did not work at all. I did a lot of research regarding that is shell, but there is no solution that kind of fix that issue I'm having.
I have just installed debian 10 as well as vscode. I have been struggling with this for 3 days now.. I installed texlive from terminal with the following command:
sudo apt install texlive
I then installed the latex workshop extension in vscode and tried building a .tex file. The following error popped up:
Recipe terminated with fatal error: spawn latexmk ENOENT.
I then preceded to install latexmk from terminal with:
sudo apt install latexmk
The same error kept popping up after that. The output showed this.
[14:59:34] Recipe step env: {}
[14:59:34] cwd: /home/phoenix/Documents/stellies/year4/2021/s&s-414/pracs/prac-4/report
[14:59:34] LaTeX build process spawned. PID: undefined.
[14:59:35] LaTeX fatal error: spawn latexmk ENOENT, . PID: undefined.
[14:59:35] Does the executable exist? PATH: /app/bin:/usr/bin:/home/phoenix/.var/app/com.visualstudio.code-oss/data/node/bin:/home/phoenix/.var/app/com.visualstudio.code-oss/data/cargo/bin:/home/phoenix/.var/app/com.visualstudio.code-oss/data/python/bin
[14:59:35] The environment variable $SHELL: /bin/sh
I then proceded to review the texlive website. I noticed that i did not set the path variable to include the texlive binaries. The texlive website gives the following path to the binary files : PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH
however /usr/local/texlive does not exist on my system for some reason. Where can i find the correct path to the texlive binaries on Debian 10?
I had the same problem. The root cause was: (1) software's bin folder missing from PATH; (2) bad file privileges. Consequently, VSC couldn't access latexmk, which explains the error messages.
In my case, the problem occurred on a mac, and specifically after I installed MacTex, which, in turn, installs Tex Live. I believe the same solution may apply to linux distros too.
Solution:
Claim file ownership (which was originally root) under folder /usr/local/texlive: sudo chown -R <username> /usr/local/texlive, where <username> is the OS-level user name. The fix will work for this specific user. If it is not enough, try instead setting group owner appropriately, and/or consider Step 3.
Add /usr/local/texlive/2021/bin/<software_dialect> to PATH. <software_dialect> depends on the installed software version: in my case it is universal-darwin; on linux it might be x86_64-linux.
If the problem persists, try to change file access permissions under /usr/local/texlive using chmod.
EDIT: As a final step, restart VSC for changes to take effect.
I recently encountered the same problem on MacOS Monterrey (M1 based). I used basictex (just for the context). As required by the installation instruction,
I added TeXLive to PATH,
installed latexmk package to the TeX distribution.
However, still got the same error as OP.
Afte reading the wiki again more carefully, what finally worked for me was as simple as restarting VS Code and MacOS. Everything works as expected after a reboot of the MAC.
I had this same problem on Mac recently, the fix that worked for me was to uninstall and reinstall the LaTeX Workshop extension.
I got the same issue , seems to be a misbehaving from Vscode on MacOS
check if the command is in the path on mac
-which command_you are running example which latexmk
If this output something that means you have your latex installed, otherwise go and installed it and make sure it is accessible via command line.
If latex is installed and you are getting that issue you can just restart your VSCode and everything will be okay.
Had a similar error and came across this post when looking for a solution.
I wanted to use texlive on Vscode with WSL2 on Windows 10. Installing texlive-full in wsl fixed this error for me.
On Mac, this is a way to fix the issue
Step1: reinstall mactex by downloading it from this link: http://www.tug.org/mactex/mactex-download.html
Step2: In your terminal do cd /usr/local, you should see texlive folder
Step3: In your terminal do sudo vim etc/paths to set the environment. Details are in this link: https://www.architectryan.com/2012/10/02/add-to-the-path-on-mac-os-x-mountain-lion/
Step4: In your terminal do /usr/local/texlive/2021/bin/x86_64-linux at the bottom. check the folder to see if the year is correct. Details in: http://www.tug.org/texlive/quickinstall.html.
Step5: Quit VC code completely, and reopen it.
I am a vim user and completely new to Emacs. My company doesn't support a good python IDE and I decide to change to spacemacs (installing vim tool will require too many access to github.)
The company firewall exists so I also can't find a regular way to install spacemacs without using github. A company firewall exists for most large companies. So a way to setup spacemacs in the presence of a firewall is important.
I have tried several methods of installing spacemacs but none of them work. I am desperate to install spacemacs on my company's linux and the company doesn't have access to github (at least I can't figure out a way to build a proxy to git). I download spacemacs from http://spacemacs.org/ and unzip the file to ~/.emacs.d.
Then I tried emacs --insecure, all the 90 packages cannot be installed：
The error messages are: Packages xx is not available.
If I use emacs --debug-init, then the messages are:
Debugger entered--Lisp error: (No such file or directory "bind-map" require(bind_map) )
I also set the proxy in the init.el so emacs can （May) have access to internet:
(setq url-proxy-services '(("no_proxy" . "work\\.com")
("http" . "proxy.work.com:911")))
I just started using emacs and I am trying to install the package.el and it has trouble with the proxy. When I try to run the commands from elpa install site the "url-retrieve-synchronously" command returns a buffer with a 407 error (I know this because I wrote the what it returns to a file and saw it, if use a www.google.com, which doesn't require a proxy, it returns the page).
I think the problem is with the username for the proxy. It has the form:
STUDENTS\123454
I think it is the "\" character thats giving trouble. I tried doing
STUDENTS\123457 | "STUDENTS\1233467" | "STUDENTS\\1234567"
and it does not work.
My ~./authinfo file looks like this has this
machine proxys.vasity.ac.za:80 port http login STUDENTS\12234 password 012TTjal
I am running emacs23 from the Ubuntu Natty repos. I have no other configurations that I am aware of for emacs.
I have my bash http_proxy set and wget works. So my questions are :
is there a way to tell the url.el package that emacs comes with to use wget instead of what its using now?
can I specify my username so that url.el works?
is the username the issue or have I missed a configuration?
package.el is now part of vanilla Emacs. Consider filing an Emacs bug report: M-x report-emacs-bug. Also, there are now a few variants of package.el out there, and it seems to evolve fairly quickly as well. If you use Tom Tromey's version of the file, consider contacting him directly about the problem.
I recently had to reimage my windows laptop, and emacs is now giving me a strange error:
"Starting new Ispell process [default]
Enabling flyspell mode gave an error"
I have aspell installed, and it is accessible via emacs. I have attached a picture to show this. I also have (setq-default ispell-program-name "aspell") in my emacs configuration. This same configuration works properly on my other windows machines. What might be the problem here? Image: Aspell in emacs-shell http://img145.imageshack.us/img145/4497/emacsaspell.jpg
You can add the line:
(setq flyspell-issue-welcome-flag nil) ;; fix flyspell problem
to your personal emacs initialization file (~/.emacs.d/init.el, ~/.emacs, ~/.emacs.el, whatever...) and that should bypass the problem for you.
EDIT: This it seems is not the best solution: see the comment below and see Dennis' answer for a better alternative.
EDIT2: As the comment below indicates, deleting the files recommended in this post causes problems when upgrading. If you followed the advice on this post and now regret it (sorry), then to reinstall the deleted files you want to type:
sudo apt-get --reinstall dictionaries-common
You should now be able to upgrade and follow Dennis' solution.
Google sent me here first so I thought I would add another common reason for this error message (at least on Ubuntu systems)
My ubuntu 10.10 fresh install had the following bug:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/619015
which is fixed (as indicated in the link) by deleting
/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el
/usr/share/emacs/site-lisp/dictionaries-common/flyspell.el
/usr/share/emacs/site-lisp/dictionaries-common/ispell.el
and all the .el .elc files in
/usr/share/emacs23/site-lisp/dictionaries-common
The reason it seems is the above files are already installed in the emacs23-common,
and the .el and .elc files retain the conflict on live systems (from reading the bug report).
I think there are other problems that can cause this error message, but this solved it for me, and I felt ubuntu is common enough for this to mensioned as another answer.
EDIT: There seems to be a less intrusive solution - see Dennis Sheil's answer
Blessings,
Tom
Writing an answer in order to mark this as accepted:
paprika's comment helped me track the problem -
"Did you check if aspell works outside of Emacs, i.e. something like cat foobar.txt |aspell -a -l en?"
Turns out aspell-en had not been installed. my bad.
I ran into this problem as well when upgrading to emacs24. My aspell was working fine. I tried some of the techniques here with dictinaries-common and settting flyspell-issue-welcome-flag to nil as above but running emacs24 kept hanging on ispell.
I ended up purging my previous emacs23 install (making sure all their .el/.elc files were deleted in the uninstall), making sure there were no emacs processes in the background, and removing my cruft collecting ~/.emacs.d directory (taking care to save code in there I still needed).
I then freshly installed emacs24 (24.1.50.1 as it happens) and ran it and flyspell worked flawlessly.