<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with gcc]]></title><description><![CDATA[A list of topics that have been tagged with gcc]]></description><link>https://board.circlewithadot.net/tags/gcc</link><generator>RSS for Node</generator><lastBuildDate>Mon, 25 May 2026 06:23:16 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/gcc.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[IDEs, UNIX, AND THE OLD WORKFLOW THAT NEVER WENT AWAY]]></title><description><![CDATA[IDEs, UNIX, AND THE OLD WORKFLOW THAT NEVER WENT AWAYWords of Wisdom are dispensed in the articleI have a workflow consisting ofscreenbash or one ofcshkshzshvim orvim.motiffunction third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }function mkcd(){ [ ! -z "$1" ] &amp;&amp; mkdir -p "$1" &amp;&amp; cd "$_"; }gccg++asmlngo from golanglsdncduThese choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle &amp; KISSquotestl;dr*Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.bashcoreutilslesstmuxnvialready form a complete and focused development environment for many Unix workflows.The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictablesources:man sh(1)man ls(1)man coreutils(1)man less(1)man screen(1)man tmux(1)man vim(1)https://www.gnu.org/software/screen/https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txthttps://go.dev/doc/installhttps://go.dev/doc/tutorial/getting-started#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX]]></description><link>https://board.circlewithadot.net/topic/508afbee-5479-4af6-8ba9-65d6aa66a8e2/ides-unix-and-the-old-workflow-that-never-went-away</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/508afbee-5479-4af6-8ba9-65d6aa66a8e2/ides-unix-and-the-old-workflow-that-never-went-away</guid><dc:creator><![CDATA[radio_azureus@ioc.exchange]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>