After trying to compile my program on Linux, I occasionally get error messages. Sometimes I get a lot needing me to scroll all the way to the top to see where my code broke first. Is there a short cut/faster method to scroll to the first output after I run for example a command like "make file"
I have tried "make file | less", but this chops off the first half of all the error messages, which is the part I am interested in, given that the error messages in the latter half is a result of something not being compiled correctly in the beginning of my file.
Related
im trying to write a bash script and i want it to be able to divide the screen in 2 sections and show a message on one of them and the output of a command in the other without having to split the terminal window just like htop or nvtop. I looked it up everywhere and im not getting a place to start.
top segment:
echo "now we are executing x command"
bottom segment:
sudo apt update -y
#above command's output
blablablablabla updating this and that
updated
your repositories work
blablablablabla
image for reference :
htop divisory lines
i looked everywhere on google and couldnt get a starting point, I also search for a way to leave a static header on the terminal with the command output refreshing underneat but still no luck finding something useful
Your reference image is for bashtop
That github project code would likely give you hints on how to proceed for what you want.
I have a LiveCode app standalone that needs to know if there is a job waiting in the MacOS print queue before printing. If app user 1 prints the 2 page report and just one page prints (out of paper) then user 2 comes along and prints the report, the first page out is user 1's report and this is causing mixups. I would like to check the MacOS print queue and prevent printing if there is a job already waiting.
It's not something I've ever needed to do, but I suspect that this capability is not included in LiveCode natively. Instead your best bet will probably be to use LiveCode's shell() function to run a unix terminal command. For instance, lpstat is a command line utility that allows you to query various things about printers connected to your Mac. The following command, run in the MacOS terminal, shows which printers are available and their current status.
lpstat -p
In LiveCode you use the shell() function to call this command line utility, like so:
put shell("lpstat -p") into tPrinterStatus
To find out more about lpstat, open the Terminal and look up the man page:
man lpstat
Lots of options for that utility will appear. There should be one that gives you the information you need.
This is not the first or only time I face this "issue", but this time I thought to go after an explanation. When retrieving some dummy value from a local machine, there is the corresponding output and immediately after the next prompt starts, no new line and not even a single space in between. I know I did not include a carriage return or a new line command in the output string, but is it wrong of me to assume that bash "resets" to a clean, new line after a complete and successful command?
R2D2-Air:~ kopaka$
R2D2-Air:~ kopaka$
R2D2-Air:~ kopaka$ curl localhost:8080
asdfR2D2-Air:~ kopaka$
R2D2-Air:~ kopaka$
Why does the the terminal behave like this? Is this working as designed and thus, are my expectations wrong? Or is this the result of some erroneous usage I'm not aware of?
How to print only one line of my log file (that is showing the log progress) continuously in present buffer? I could not find tail -f working for me.
Basically, I have made my own command using function call in .vimrc and later on I have opened the quickfix window to show the compilation errors. Presently, i am just echoing the message "running software in background" which seems static and the user may think that the system is hanged if he runs a large design. How can I show my progress simultaneously in the current buffer from the log file which ius updated continuously?
I'm not sure if this question is appropriate here but I have nowhere else to ask. I recently started to typeset some 'mathsy' stuff using Latex and it became a hobby for me. I've been using TeXnicCenter for this, but feeling that I've got familiar with Latex language, I decieded to improve 'efficiency' of typesetting by changing the editor.
So I decided to use Vim (latest version, 7.4) with Suite-Latex. I've just installed Vim and Suite-Latex, following exactly what was instructed here. I made every necessary changes mentioned here, and it seemed to me that installation was successful (I got what was expected on Step 4)
Then I started to work through this tutorial and everything went fine until this section.
When I press F9 for autoreference, I see that Vim is working on something for split seconds and red error message refering to "can't find [some file name]" in my user/appdata/local/temp directory. The "file name" changes every time I do this (so its kind of temporary file as its directory suggests?). And then it produces a new window with title __ OUTLINE __ where 2 empty lines are showing up.
If I press n (in the new window described above) error message saying "E486: Pattern not found: rf" pops up and pressing j results in going down one row. If I press enter key, message ":call Tex_FinishOutlineCompletion()" pops up.
More frustratingly, if I try to compile a file by entering command \ll, a new window pops up where there are two lines saying:
1.ll I can't find file `newfile.tex'. newfile.tex
2.ll Emergency stop
and below these is a message saying
[Quickfix list]: latex -interaction=nonstopmode -file-line-error-style newfile.tex
So I thought it maybe is something to do with VIM not being able to find files in my computer (so something wrong with grep?), and I tried to resolve it by downloading a software called "cygwin" on which developers said their tests were successful, but it changed nothing.
But I think the two problems are related.
As it is, I am completely newbie in this type of editing environment (or any kind of programming) but I really would like to learn some Vim seeing how efficient it is in typesetting etc. Sorry for not being a pro at typing codes here. Thanks for reading!
I believe you need a latex compiler---I've had this issue and well, one thing that's left out of the conversation a lot is the compiler (pdflatex, latexmk, etc). As of now, you should download a compiler since vim-latex (latex-suite) doesn't actually come with a compiler (that I know of) and it's just a plug in with some cool stuff in it, but not what you need to make a file.pdf out of your file.tex.
It happened to me before. I found out that this problem may happen when you have special characters (such as white space and other symbols) in your file name or folder path. Try again with file name and path only in English letters.