I put my code in and compile it but then it shows up in word pad with no output just the whole code. is something wrong with Emacs?
It sounds like compile mode is misconfigured, or you're putting in the wrong compile command when it prompts you. You're on windows, where attempting to execute a file that isn't itself executable will instead launch the program registered to view or edit that type of file. You must have wordpad configured as the default viewer for the files you're editing.
Related
The reason for me asking is that Im working with a build tool that doesnt forward compiler colorization, causing everything to be single colored in the terminal task output view ( and I happen to know that the output window supports automatic colorization of log files).
I am sorry if the question doesn't make sense, I didn't really know how to phrase it properly.
What I am trying to achieve is similar to how it works in the command prompt when running a python file. When I run a python file from the command prompt, the command prompt window will jump to the last outputted line during the running of the program, so what is currently being outputted is always visible. However in my current VS Code set up, the output window will not jump to the last line as it is printed, and I have to scroll through the output window to see what is happening with the program.
I am currently using the latest version of VS Code and using the code-runner extension as well. Please let me know if what I am asking does not really make sense.
Thanks
As far as I understand your question, I would like to answer it.
To Auto-Scroll to the last output, you can just click on the Lock Icon near the Clear Console icon.
I would like to change few things in my .emacs configuration file. The problem is that I cannot find it.
Does anyone have any idea where it could be on Windows bash?
Is it even called .emacs on windows Bash? Do I have to create it myself?
Thanks in advance
After some researches, here is what I understood :
As Varro said in the commnent, .emacs file will not be created by default, since it will only contain cuztomizations you want. So you have to create it yourself. By the way, apparently it is a good practice to call it init.el. To find where to create it, type env in the terminal and look for the HOME variable. This value will show you the path considered as the home directory, where emacs created .emacs.d/ folder. You must create init.el file in this folder, and emacs will load it automatically.
This is not related to the question but it might help you :
I needed this file in order to change the cursor on emacs. At first, I thought that emacs was not loading the file correctly, because the cursor was not changing. I made some tests, and I was able to change background color, so it was not the problem. But, in fact, you can NOT change the cursor, since it is defined by the terminal itself, not emacs.
When I'm debugging code in a framework, it usually goes through a bunch of different calls in different files before actually getting to the file I want to investigate. Is there a way to open the file I want when I start geben, put the breakpoint in that file then tell geben to run (press g)?
Otherwise I have to keep stepping over/into until geben finally get's to the file I want, at which point I can then go to the line I want and set the breakpoint.
C-cf runs geben-find-file
IIRC, geben must already be in an active debugging session for that function to work; but once set the breakpoints are persistent, so it's not too onerous.
geben-breakpoint-menu menu is very convenient for setting conditionals, if you hadn't noticed that.
In MATLAB, why does the file have to be saved prior to running ?
I often try quick snippets of code, which I could also easily run also on the Command Window line by line. So, why when I run them through the editor, I have to save them first ?
Can this behaviour be changed, maybe ?
You can use cell mode in the editor placing %% before your code. See also Cell menu in the editor. Once you create cells, you can run them one by one pressing Ctrl-Enter. You don't need to save the file. However you cannot use editor's debugging features (breakpoints, etc).
Video tutorial
my guess would be that when you run your program, the matlab interpreter run it from the disk and not from the IDE buffer. so if you don't save the file it wouldn't run the correct code.