Here is how I create the short little demo programs you find in my C programming books, on my blog, and in my online training courses. Tiny programs (source code files). An editor window. A command prompt window. A file manager. Simple. Short. Quick - not to mention traditional!
https://lnkd.in/gZuTZ6p6
When it comes to compiling and building tiny little programs like the ones you find on my blog, in my books, in my online training, one way I like to approach things is here at the desktop, and they usually do it with a few windows open. So there's the File Manager window, which is here. And then I also have a command prompt window. This is the Windows Subsystem for Linux running the bash shell. And then I'll also have a third window open, which is the editor. So say I want to edit a program I want to edit. Days. Here in the File Manager DoubleClick days comes U in the editor O here I can add it and get things done and I can leave this window open as I switch. To the command prompt and I will embiggen this window. If I want to build the source code, I type clang, my favorite C language compiler. The wall switch to activate all warnings and the name of the program. The program is built. You can run it right here at the bash shell. The program name is about, but it's not found because you have to tell Linux to look in the current directory, which is abbreviated slash A dot out. And there's the program's output. I can switch back to the editor to make more edits to change things and of course on a larger screen monitor all of these windows would be visible at once, but. Here, as I'm showing this is the demo. You can see things full screen which makes them a little more visible, but normally all this stuff would be in little tiny windows located all over the desktop. So you can bounce from one to the other. If I wanted to edit another program say. Ohh, I don't know. Alphabet table, Here we go. It would be in one window. I could edit over here and then I could build it over here. And then the autocomplete command at the bash shell is tab. So there's alphabet table. It builds OK, it runs, it outputs all this junk there. I can go back over here and edit, which I can't because I just accidentally closed that window, but you get the idea. This is how I've done things for years. Sometimes I would actually edit here as well because you can do that. Close the days. So if you want to, you could edit in this window as well, which is the way the old timers used to do it. And it comes U in the vim editor here. Of course, one of the problems here is that you have to close that program and then run the compiler here at the command prompt. Anyway, that's the way I've been doing things. On a larger screen it all works out because you can see the windows full size here. For demo purposes, the windows are smaller and I showed them full screen. But this is the way I've done it. It's pretty easy. It's not as fancy as using an IDE, but it's ready, it's quick, and for those small short programs I use. For demos, when I teach C programming, this is the way I do things. The way you can do things, too. And now you know how it's done.
Neat, nice to get a look at your process. What’s the name of that editor you use?