When I try to compile a Coq file using C-c in Emacs, I get this error:
Coq compilation error: ((coqdep -Q /home/****/cs54 DMFP /tmp/ProofGeneral-coqUMWPyn.v) No such file or directory
I'm on manjaro and have installed Emacs and Coq through the command line and don't know what's going on.
_CoqProject only contains these characters:
-Q . DMFP
In case this helps narrow it down, when I type coqc into the terminal, nothing happens and the prompt comes up again.
When I type coqtop the program starts but it does not evaluate anything. When I type something like "2" or "Check 2" it simply pulls up the prompt for the next input.
Related
I downloaded chocolatey and am able to load up ghci and get prelude on powershell.
I then cd into the directory where I have a haskell file I want to run, then I type ghci and then type:
load haskellprogram.hs
but then I get an error about it not being in scope.
Is this not how you run a Haskell program?
The GHCi command to load a file is :load, not load. You should write:
:load haskellprogram.hs
The command can also be abbreviated :l. You can find more information about the available commands in GHCi by entering :help. Also note that the prompt shows the modules you have imported; Prelude is just the name of the standard library module that gets imported by default. You can change the prompt with:
:set prompt "> "
:set prompt-cont "| "
(Where prompt-cont is the prompt for multi-line input, using the commands :{ and :} or the multi-line input mode enabled by :set +m.)
When you entered load haskellprogram.hs, it was interpreted as a Haskell expression: (load haskellprogram) . hs, which tries to use the (.) composition operator and three variables load, haskellprogram, and hs that are not defined.
I have been trying to pip install psycopg2 for some time now
I have just updated to python 3.7.4, before this problem started.
To set my path to a specific python version I used the code below.
nano .bash_profile
I thought that it would now be easy for my system to identify the path of the newly installed python, as to enable it to install psycopg2. Then the below started happening.
The second line of system terminal or python terminal is now always showing:
-bash: zzzzz#: command not found on my terminal
No matter what I type on my terminal, I am always getting command not found
This would mean you literally have "zzzzz" somewhere in the bash_profile. Bash is seeing "zzzzz" as just another command to run at startup like the rest of the profile script. As there is nothing in your PATH matching that string, bash reports the issue back to you.
Either remove the extra line from your .bash_profile. OR use a terribly wasteful work-around!
ln -s /bin/true /bin/zzzzz
This will create a symbolic link to the "true" binary (all it ever does is return true) from zzzzz. Now bash can find zzzzz and run it during start up, which does nothing. No more error and an absurd work around. You should fix the file.
I have a project that uses a bash script to invoke cmake and make. I have successfully used this script from Emacs by using M-x compile, followed by typing:
cd ../..; ./build.sh
in the minibuffer. (The project organization is top/src/various_source_folders and build.sh is in top/.)
I am trying to define a directory variable to specify the default command to use for compile. I have tried the following (both with single or double quotes around the compile command) in .dir-locals.el:
((c++-mode
(compile-command 'cd ../..\; ./build.sh')))
Which gives no errors, but M-x compile still defaults to make -k.
((c++-mode
(set-variable 'compile-command' "cd ../../\; ./build.sh")))
Which gives a warning about unsafe variables. Even if I choose apply, compile still defaults to make -k
Simply using M-x eval-buffer with the second line ((set variable...) in *scratch* correctly sets the compile command.
Is there a different way I can/should be doing this?
Found an answer here.
Two periods and some parenthesis were missing from the syntax:
((c++-mode
. ((compile-command . "cd ../../\; ./build.sh"))))
I have a file at location /tmp/z+b/c
In a shell buffer, if I type at the prompt cd /tmp/z<TAB> and press then completion changes it to cd /tmp/z+b/, because that is the only entry starting with z.
The same thing happens if I type start with ls /tmp/z<TAB>, the text changes to ls /tmp/z+b/.
But another <TAB> results in different behavior:
For cd, the text changes to cd /tmp/z+b/c/, again because c is the only entry in that directory.
But for ls, the minibuffer reports no match. I captured the screenshot below immediately after the message was displayed.
If I instead type ls /tmp/z+<TAB> then neither does completion occur nor is any message displayed in minibuffer. So it seems completion does not handle + character correctly.
Update
Running Cygwin 32 bit Emacs version 24.3.1 on Windows 7.
I'm trying to get flymake to work, but when I run flymake-mode, I get the following error
switched OFF Flymake mode for buffer TdDisassemblerIde.cpp due to fatal status \
PROCERR, warning Failed to launch syntax check process 'make' with args (-s -C ./ \
CHK_SOURCES=TdDisassemblerIde_flymake.cpp SYNTAX_CHECK_MODE=1 check-syntax): Wrong type \
argument: symbolp, (utf-8)
Any clues?
When I have a problem with flymake, I do
M-x set-variable flymake-log-level <RET> 3
And then run flymake again (M-x flymake-mode).
Then look in the *Messages* buffer for a useful error message.
The last time this happened to me, about an hour ago, my check-syntax target in the flymakefile lacked a source module; I had added a module but had forgotten to add it to the list of files that should be included in a flymake compilation. Modifying the makefile corrected it. (This was for C#, but setting flymake-log-level should work to get a diagnosis for you too.)
Answering my own question: the problem was that I had set process-coding-system-alist to contain the symbol utf-8, and apparently flymake does not like that. Setting process-coding-system-alist to nil solved the problem.