this post was submitted on 04 Dec 2024
23 points (96.0% liked)
Programming
17668 readers
186 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So, I'm a bit rusty, but I believe in Kate you would hit F4 to get a terminal window and you would execute
gcc your_file.c -o your_output_file
Then after that's run you'd type just "your_output_file" and hit enter
I think on windows you'd need to make sure the output file name ends with .exe but I'm not sure about that, maybe someone else can chime in?
that does work, it's a little clunkier than i'd like but it's better than the code not running
Great!
But now try to set a breakpoint and do some debugging and you'll realise why most devs use real IDEs instead.
Dishonest and misleading. gdb ./main.elf, break 45. Learn your tools. Optimize for learning. Select tools that generalize. Avoid lock-in.