See, this is the part where we learn about writing code rather than how to use someone's else's point n' click interface:
Now I can call this script "F7" and on the command-line:Code:#!/bin/bash gcc -Wall -std=c99 -pedantic -superoptimize -bioniclinking -maxbugfixx -o $1 ./$1.c
F7 myprog
Some OS's also allow individual users to keep their own environment variables, eg. here's one of mine:
[root~/shell] echo $CGTK
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -L/usr/local/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0
Usually, because the cursor does not have to circumnavigate the screen in the process. And every time your hand leaves the keyboard to reach for the mouse, be sure to say "Please, I want carpal tunnel syndrome now more than ever."Unless you feel like clicking options instead of typing it out is faster and better.
So, you are a proponent of "The MacDonald's Diet", I imagine as well
Thanks for that. I'm sure I will be passing it on soon! I can even say, "If you are going to use an IDE, at least try the breakdance..."I suspect it's because they use Run With Debug (F5), which makes the console disappear when the program is finished.
Yet, using Run Without Debug (Ctrl+F5) makes the console window stay after the program is finished. A breakpoint in debug mode or run without debug is all that's needed.