nixers.net_mybb.rss.xml - sfeed_tests - sfeed tests and RSS and Atom files
 (HTM) git clone git://git.codemadness.org/sfeed_tests
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) README
 (DIR) LICENSE
       ---
       nixers.net_mybb.rss.xml (72095B)
       ---
            1 <?xml version="1.0" encoding="UTF-8"?>
            2 <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
            3         <channel>
            4                 <title><![CDATA[nixers - All Forums]]></title>
            5                 <link>https://nixers.net/</link>
            6                 <description><![CDATA[nixers - https://nixers.net]]></description>
            7                 <pubDate>Sun, 07 Nov 2021 19:10:54 +0000</pubDate>
            8                 <generator>MyBB</generator>
            9                 <item>
           10                         <title><![CDATA[Nixers Book Club - Book #6: Introduction to Operating Systems Abstractions]]></title>
           11                         <link>https://nixers.net/Thread-Nixers-Book-Club-Book-6-Introduction-to-Operating-Systems-Abstractions</link>
           12                         <pubDate>Tue, 19 Oct 2021 20:09:35 +0000</pubDate>
           13                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
           14                         <guid isPermaLink="false">https://nixers.net/Thread-Nixers-Book-Club-Book-6-Introduction-to-Operating-Systems-Abstractions</guid>
           15                         <description><![CDATA[As proposed in the last thread, the next book of the Nixer's Book Club is gonna be <a href="https://archive.org/details/plan9designintro" target="_blank" rel="noopener" class="mycode_url">Introduction to Operating Systems Abstractions using Plan 9 from Bell Labs</a><br />
           16 <br />
           17 <img src="https://9p.io/plan9/img/plan9bunnywhite.jpg" alt="[Image: plan9bunnywhite.jpg]" class="mycode_img" loading="lazy" /><br />
           18 <br />
           19 We can do 2 chapters per week.<br />
           20 Our first session will be Nov 13, when we will discuss the first two chapters.<br />
           21 See you then!]]></description>
           22                         <content:encoded><![CDATA[As proposed in the last thread, the next book of the Nixer's Book Club is gonna be <a href="https://archive.org/details/plan9designintro" target="_blank" rel="noopener" class="mycode_url">Introduction to Operating Systems Abstractions using Plan 9 from Bell Labs</a><br />
           23 <br />
           24 <img src="https://9p.io/plan9/img/plan9bunnywhite.jpg" alt="[Image: plan9bunnywhite.jpg]" class="mycode_img" loading="lazy" /><br />
           25 <br />
           26 We can do 2 chapters per week.<br />
           27 Our first session will be Nov 13, when we will discuss the first two chapters.<br />
           28 See you then!]]></content:encoded>
           29                 </item>
           30                 <item>
           31                         <title><![CDATA[Your top 10 commands]]></title>
           32                         <link>https://nixers.net/Thread-Your-top-10-commands</link>
           33                         <pubDate>Fri, 15 Oct 2021 02:10:02 +0000</pubDate>
           34                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
           35                         <guid isPermaLink="false">https://nixers.net/Thread-Your-top-10-commands</guid>
           36                         <description><![CDATA[After reading <a href="http://phroxy.z3bra.org/phlog.z3bra.org:70/0/my-top-10-commands.txt" target="_blank" rel="noopener" class="mycode_url">this post</a> on z3bra's phlog, I got curious to see what are my top 10 commands.<br />
           37 <br />
           38 <blockquote class="mycode_quote"><cite>Quote:</cite>Now what are YOUR top 10 commands ? <br />
           39 -- z3bra</blockquote>
           40 <br />
           41 On OpenBSD ksh, the history builtin only lists the last 10 commands on history, to list all commands, <a href="https://webzine.puffy.cafe/issue-1.html#tips" target="_blank" rel="noopener" class="mycode_url">you need to run this:</a><br />
           42 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>history 1</code></div></div>(history arguments are <span style="font-weight: bold;" class="mycode_b">[first [last]]</span>).<br />
           43 <br />
           44 So, this is the command I needed to run:<br />
           45 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>history 1 | awk '{print &#36;2}' | sort | uniq -c | sort -rn | head -n 10</code></div></div><br />
           46 My &#36;HISTSIZE is 1000, so my sample is not that big as z3bra's (whose &#36;HISTORY is ten times bigger).<br />
           47 <br />
           48 Here's my top 10:<br />
           49 <ul class="mycode_list"><li>1. vim: I expected that.<br />
           50 </li>
           51 <li>2. make: I use makefiles to build programs and documents, move my dotfiles to their proper places, etc.<br />
           52 </li>
           53 <li>3. cd<br />
           54 </li>
           55 <li>4. d: This is a shell function wrapper around tree(1) (actually colortree(1), a colored version of tree). Yes, I use tree(1), and not ls(1), to list the contents of a directory...<br />
           56 </li>
           57 <li>5. agenda: That's a shell script that shows a calendar for the current month, the events for the week and the tasks I need to do. Very handy. For events it calls calendar(1), for the tasks it calls todo(1). Both programs are part of my <a href="https://github.com/phillbush/orgutils" target="_blank" rel="noopener" class="mycode_url">orgutils</a>. This script reads the agenda and todo files in all directories of '~/proj/' (that is, in every project of mine), adds a prefix to each event and task corresponding to the project name, and pipes them to agenda(1) and todo(1).<br />
           58 </li>
           59 <li>6. git.<br />
           60 </li>
           61 <li>7. man.<br />
           62 </li>
           63 <li>8. xopen: That's my opener script. If I want to open a image with sxiv or a document with zathura, I just call xopen on them.<br />
           64 </li>
           65 <li>9. ssh.<br />
           66 </li>
           67 <li>10. fm: That's actually an alias for lf, the file manager, with some options.<br />
           68 </li>
           69 </ul>
           70 ]]></description>
           71                         <content:encoded><![CDATA[After reading <a href="http://phroxy.z3bra.org/phlog.z3bra.org:70/0/my-top-10-commands.txt" target="_blank" rel="noopener" class="mycode_url">this post</a> on z3bra's phlog, I got curious to see what are my top 10 commands.<br />
           72 <br />
           73 <blockquote class="mycode_quote"><cite>Quote:</cite>Now what are YOUR top 10 commands ? <br />
           74 -- z3bra</blockquote>
           75 <br />
           76 On OpenBSD ksh, the history builtin only lists the last 10 commands on history, to list all commands, <a href="https://webzine.puffy.cafe/issue-1.html#tips" target="_blank" rel="noopener" class="mycode_url">you need to run this:</a><br />
           77 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>history 1</code></div></div>(history arguments are <span style="font-weight: bold;" class="mycode_b">[first [last]]</span>).<br />
           78 <br />
           79 So, this is the command I needed to run:<br />
           80 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>history 1 | awk '{print &#36;2}' | sort | uniq -c | sort -rn | head -n 10</code></div></div><br />
           81 My &#36;HISTSIZE is 1000, so my sample is not that big as z3bra's (whose &#36;HISTORY is ten times bigger).<br />
           82 <br />
           83 Here's my top 10:<br />
           84 <ul class="mycode_list"><li>1. vim: I expected that.<br />
           85 </li>
           86 <li>2. make: I use makefiles to build programs and documents, move my dotfiles to their proper places, etc.<br />
           87 </li>
           88 <li>3. cd<br />
           89 </li>
           90 <li>4. d: This is a shell function wrapper around tree(1) (actually colortree(1), a colored version of tree). Yes, I use tree(1), and not ls(1), to list the contents of a directory...<br />
           91 </li>
           92 <li>5. agenda: That's a shell script that shows a calendar for the current month, the events for the week and the tasks I need to do. Very handy. For events it calls calendar(1), for the tasks it calls todo(1). Both programs are part of my <a href="https://github.com/phillbush/orgutils" target="_blank" rel="noopener" class="mycode_url">orgutils</a>. This script reads the agenda and todo files in all directories of '~/proj/' (that is, in every project of mine), adds a prefix to each event and task corresponding to the project name, and pipes them to agenda(1) and todo(1).<br />
           93 </li>
           94 <li>6. git.<br />
           95 </li>
           96 <li>7. man.<br />
           97 </li>
           98 <li>8. xopen: That's my opener script. If I want to open a image with sxiv or a document with zathura, I just call xopen on them.<br />
           99 </li>
          100 <li>9. ssh.<br />
          101 </li>
          102 <li>10. fm: That's actually an alias for lf, the file manager, with some options.<br />
          103 </li>
          104 </ul>
          105 ]]></content:encoded>
          106                 </item>
          107                 <item>
          108                         <title><![CDATA[webzine]]></title>
          109                         <link>https://nixers.net/Thread-webzine</link>
          110                         <pubDate>Mon, 11 Oct 2021 15:28:11 +0000</pubDate>
          111                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1240">ols</a>]]></dc:creator>
          112                         <guid isPermaLink="false">https://nixers.net/Thread-webzine</guid>
          113                         <description><![CDATA[Greetings nixers,<br />
          114 <br />
          115 I've been thinking about doing some sort of nix-related webzine for a while now, and I know that the idea has been floated on IRC a few times already.<br />
          116 <br />
          117 My thoughts are a monthly publication with a couple of short articles (350-500 words), with one longer form (800-1000 words) and then possibly some sort of recurring theme like "shell one-liner of the month".<br />
          118 <br />
          119 Interested to hear thoughts and ideas for submissions; if all goes well I would like to get issue one launched before the end of the month (optimistic I know)<br />
          120 <br />
          121 Mock up below<br />
          122 <br />
          123 <img src="https://irc.ols.wtf/uploads/14bd737fefeb7551/image.png" alt="[Image: image.png]" class="mycode_img" loading="lazy" />]]></description>
          124                         <content:encoded><![CDATA[Greetings nixers,<br />
          125 <br />
          126 I've been thinking about doing some sort of nix-related webzine for a while now, and I know that the idea has been floated on IRC a few times already.<br />
          127 <br />
          128 My thoughts are a monthly publication with a couple of short articles (350-500 words), with one longer form (800-1000 words) and then possibly some sort of recurring theme like "shell one-liner of the month".<br />
          129 <br />
          130 Interested to hear thoughts and ideas for submissions; if all goes well I would like to get issue one launched before the end of the month (optimistic I know)<br />
          131 <br />
          132 Mock up below<br />
          133 <br />
          134 <img src="https://irc.ols.wtf/uploads/14bd737fefeb7551/image.png" alt="[Image: image.png]" class="mycode_img" loading="lazy" />]]></content:encoded>
          135                 </item>
          136                 <item>
          137                         <title><![CDATA[Nixers.net Conf 2021]]></title>
          138                         <link>https://nixers.net/Thread-Nixers-net-Conf-2021</link>
          139                         <pubDate>Sun, 26 Sep 2021 11:15:30 +0000</pubDate>
          140                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=80">venam</a>]]></dc:creator>
          141                         <guid isPermaLink="false">https://nixers.net/Thread-Nixers-net-Conf-2021</guid>
          142                         <description><![CDATA[<img src="https://nixers.net/conf/2021/nixers_conf_2021_poster_white.png" alt="[Image: nixers_conf_2021_poster_white.png]" class="mycode_img" loading="lazy" /><br />
          143 Hello nixers,<br />
          144 I'd like to announce the second edition of the nixers.net conf.<br />
          145 We will host the conference on Sunday the 7th of November between 2-4pm UTC depending on the number of talks.<br />
          146 <br />
          147 The call for proposal is open for 4-5 talks.<br />
          148 The presentations has to fulfill these criteria:<br />
          149 <ul class="mycode_list"><li>Fit within a time limit of 15min<br />
          150 </li>
          151 <li>3-5min for Q&amp;A<br />
          152 </li>
          153 <li>The topic should be anything that is usually posted on nixers: a project you are working on, a unix story, some research about a topic, some lesser known unix tool, stuff you've discovered on unix, etc..<br />
          154 </li>
          155 <li>The slides should contain the logo of the conf. You can find a <a href="https://nixers.net/conf/2021/nixers_conf_2021_white.png" target="_blank" rel="noopener" class="mycode_url">version for light background</a> and a <a href="https://nixers.net/conf/2021/nixers_conf_2021_black.png" target="_blank" rel="noopener" class="mycode_url">version for dark background</a>.<br />
          156 </li>
          157 <li>The presentation should be under CC-0 if recorded and sharing the slides.<br />
          158 </li>
          159 </ul>
          160 You can either choose to have your talk recorded or not.<br />
          161 Contact me on IRC, email, or on the forums with your ideas to reserve a spot. Send me your slides, general title, and ideas. Try to finalize it as much as possible before contacting me, and let me know how you'd like to be addressed.<br />
          162 <br />
          163 Be sure to share you slides and content at least 4 days before the conf to be included in the schedule. Otherwise, you can always geek out with members after the "official" talks and present whatever you want to present. Let's make it fun and games.<br />
          164 <br />
          165 The platform that will host the conference will be the same as last year, namely bigbluebutton, BBB. We'll need to record the conference ourselves as bigbluebutton format is composed of a mix of slides and audio only. We'll also host it on <a href="https://bbb.faimaison.net" target="_blank" rel="noopener" class="mycode_url">faimaison</a> and the link will be shared here and on IRC on the day of the conference.<br />
          166 Only presenters will join with the mic, everyone else should join as listen only.<br />
          167 A tutorial of the UI will be given at the start of the conference.<br />
          168 Be aware that this software uses webrtc, and that your browser should support it.<br />
          169 <a href="https://test.webrtc.org/" target="_blank" rel="noopener" class="mycode_url">https://test.webrtc.org/</a><br />
          170 <br />
          171 <br />
          172 Please note: The event will be recorded for our use. Any comments, chats, or voice recordings by attendees may be used as part of the final recorded and published conference.<br />
          173 <br />
          174 Updates about the conference will be found in this very post.<br />
          175 Cheers!<br />
          176 <br />
          177 <hr class="mycode_hr" />
          178 <br />
          179 Schedule:<br />
          180 <ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Intro</span> 14:00-14:15<br />
          181 </li>
          182 <li><span style="font-weight: bold;" class="mycode_b">Creating your own troff macros — seninha</span> 14:15-14:35<br />
          183   <span style="font-weight: bold;" class="mycode_b">Description</span>:  What is a troff macro package, how it works and how to write your own<br />
          184 </li>
          185 <li><span style="font-weight: bold;" class="mycode_b">Keeping track of your things — venam</span> 14:35-14:55<br />
          186   <span style="font-weight: bold;" class="mycode_b">Description</span>:  The extended mind, a review of a 6 years old thread and discussion of the topic.<br />
          187 </li>
          188 <li><span style="font-weight: bold;" class="mycode_b">Pause/Buffer</span> 14:55-15:00<br />
          189 </li>
          190 <li><span style="font-weight: bold;" class="mycode_b">Truly Federated Identity for the web — push-f</span> 15:00-15:20<br />
          191   <span style="font-weight: bold;" class="mycode_b">Description</span>:  How the open source community could become more independent from megacorporations.<br />
          192 </li>
          193 <li><span style="font-weight: bold;" class="mycode_b">...</span><br />
          194 </li>
          195 <li><span style="font-weight: bold;" class="mycode_b">Outro</span> 15:20-End<br />
          196 </li>
          197 </ul>
          198 <br />
          199 Final recording in BBB format: _AVAILABLE AFTER THE CONFERENCE_<br />
          200 <br />
          201 <br />
          202 <hr class="mycode_hr" />
          203 <a href="https://nixers.net/Thread-Nixers-net-Conf-2020" target="_blank" rel="noopener" class="mycode_url">Last year's conference</a>]]></description>
          204                         <content:encoded><![CDATA[<img src="https://nixers.net/conf/2021/nixers_conf_2021_poster_white.png" alt="[Image: nixers_conf_2021_poster_white.png]" class="mycode_img" loading="lazy" /><br />
          205 Hello nixers,<br />
          206 I'd like to announce the second edition of the nixers.net conf.<br />
          207 We will host the conference on Sunday the 7th of November between 2-4pm UTC depending on the number of talks.<br />
          208 <br />
          209 The call for proposal is open for 4-5 talks.<br />
          210 The presentations has to fulfill these criteria:<br />
          211 <ul class="mycode_list"><li>Fit within a time limit of 15min<br />
          212 </li>
          213 <li>3-5min for Q&amp;A<br />
          214 </li>
          215 <li>The topic should be anything that is usually posted on nixers: a project you are working on, a unix story, some research about a topic, some lesser known unix tool, stuff you've discovered on unix, etc..<br />
          216 </li>
          217 <li>The slides should contain the logo of the conf. You can find a <a href="https://nixers.net/conf/2021/nixers_conf_2021_white.png" target="_blank" rel="noopener" class="mycode_url">version for light background</a> and a <a href="https://nixers.net/conf/2021/nixers_conf_2021_black.png" target="_blank" rel="noopener" class="mycode_url">version for dark background</a>.<br />
          218 </li>
          219 <li>The presentation should be under CC-0 if recorded and sharing the slides.<br />
          220 </li>
          221 </ul>
          222 You can either choose to have your talk recorded or not.<br />
          223 Contact me on IRC, email, or on the forums with your ideas to reserve a spot. Send me your slides, general title, and ideas. Try to finalize it as much as possible before contacting me, and let me know how you'd like to be addressed.<br />
          224 <br />
          225 Be sure to share you slides and content at least 4 days before the conf to be included in the schedule. Otherwise, you can always geek out with members after the "official" talks and present whatever you want to present. Let's make it fun and games.<br />
          226 <br />
          227 The platform that will host the conference will be the same as last year, namely bigbluebutton, BBB. We'll need to record the conference ourselves as bigbluebutton format is composed of a mix of slides and audio only. We'll also host it on <a href="https://bbb.faimaison.net" target="_blank" rel="noopener" class="mycode_url">faimaison</a> and the link will be shared here and on IRC on the day of the conference.<br />
          228 Only presenters will join with the mic, everyone else should join as listen only.<br />
          229 A tutorial of the UI will be given at the start of the conference.<br />
          230 Be aware that this software uses webrtc, and that your browser should support it.<br />
          231 <a href="https://test.webrtc.org/" target="_blank" rel="noopener" class="mycode_url">https://test.webrtc.org/</a><br />
          232 <br />
          233 <br />
          234 Please note: The event will be recorded for our use. Any comments, chats, or voice recordings by attendees may be used as part of the final recorded and published conference.<br />
          235 <br />
          236 Updates about the conference will be found in this very post.<br />
          237 Cheers!<br />
          238 <br />
          239 <hr class="mycode_hr" />
          240 <br />
          241 Schedule:<br />
          242 <ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Intro</span> 14:00-14:15<br />
          243 </li>
          244 <li><span style="font-weight: bold;" class="mycode_b">Creating your own troff macros — seninha</span> 14:15-14:35<br />
          245   <span style="font-weight: bold;" class="mycode_b">Description</span>:  What is a troff macro package, how it works and how to write your own<br />
          246 </li>
          247 <li><span style="font-weight: bold;" class="mycode_b">Keeping track of your things — venam</span> 14:35-14:55<br />
          248   <span style="font-weight: bold;" class="mycode_b">Description</span>:  The extended mind, a review of a 6 years old thread and discussion of the topic.<br />
          249 </li>
          250 <li><span style="font-weight: bold;" class="mycode_b">Pause/Buffer</span> 14:55-15:00<br />
          251 </li>
          252 <li><span style="font-weight: bold;" class="mycode_b">Truly Federated Identity for the web — push-f</span> 15:00-15:20<br />
          253   <span style="font-weight: bold;" class="mycode_b">Description</span>:  How the open source community could become more independent from megacorporations.<br />
          254 </li>
          255 <li><span style="font-weight: bold;" class="mycode_b">...</span><br />
          256 </li>
          257 <li><span style="font-weight: bold;" class="mycode_b">Outro</span> 15:20-End<br />
          258 </li>
          259 </ul>
          260 <br />
          261 Final recording in BBB format: _AVAILABLE AFTER THE CONFERENCE_<br />
          262 <br />
          263 <br />
          264 <hr class="mycode_hr" />
          265 <a href="https://nixers.net/Thread-Nixers-net-Conf-2020" target="_blank" rel="noopener" class="mycode_url">Last year's conference</a>]]></content:encoded>
          266                 </item>
          267                 <item>
          268                         <title><![CDATA[how do you know which tools you (really) use?]]></title>
          269                         <link>https://nixers.net/Thread-how-do-you-know-which-tools-you-really-use</link>
          270                         <pubDate>Fri, 27 Aug 2021 01:03:07 +0000</pubDate>
          271                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=2054">freem</a>]]></dc:creator>
          272                         <guid isPermaLink="false">https://nixers.net/Thread-how-do-you-know-which-tools-you-really-use</guid>
          273                         <description><![CDATA[Hello.<br />
          274 <br />
          275 I was debootstrapping a debian 11 on some partitions yesterday (because my upgrade path won't be easy considering my tweaks, between the init system and the rebuilt packages...) and started to create a mindmap of stuff to do next time (turns out it almost looks like a roadmap of stuff to do to create a distro, but that's another topic).<br />
          276 <br />
          277 In the end, I noticed... or rather, am noticing, that I do not use that many programs, and that this tool (the mindmap) allows me to get a better understanding of what I use, in which context, and why, if I would like a replacement or not, etc.<br />
          278 <br />
          279 I might end in sharing the file, when it will be a bit more refined, but it spawned the (one in title) questions of: do you really know which tools you are using? Do you know why you're using them? Do you know any alternatives to them? Why not use them? How would you collect those informations for future use (when a program stops working (depends on deprecated tech), when your needs evolve, etc)?<br />
          280 <br />
          281 Note that I only have in mind the tools <span style="font-weight: bold;" class="mycode_b">you</span> use, not the ones the tools you use depends on, that's a very different thing.<br />
          282 <br />
          283 I think it would be interesting to have thoughts from fellow nixers on those questions, and maybe on other ones you might ask in the discussion?]]></description>
          284                         <content:encoded><![CDATA[Hello.<br />
          285 <br />
          286 I was debootstrapping a debian 11 on some partitions yesterday (because my upgrade path won't be easy considering my tweaks, between the init system and the rebuilt packages...) and started to create a mindmap of stuff to do next time (turns out it almost looks like a roadmap of stuff to do to create a distro, but that's another topic).<br />
          287 <br />
          288 In the end, I noticed... or rather, am noticing, that I do not use that many programs, and that this tool (the mindmap) allows me to get a better understanding of what I use, in which context, and why, if I would like a replacement or not, etc.<br />
          289 <br />
          290 I might end in sharing the file, when it will be a bit more refined, but it spawned the (one in title) questions of: do you really know which tools you are using? Do you know why you're using them? Do you know any alternatives to them? Why not use them? How would you collect those informations for future use (when a program stops working (depends on deprecated tech), when your needs evolve, etc)?<br />
          291 <br />
          292 Note that I only have in mind the tools <span style="font-weight: bold;" class="mycode_b">you</span> use, not the ones the tools you use depends on, that's a very different thing.<br />
          293 <br />
          294 I think it would be interesting to have thoughts from fellow nixers on those questions, and maybe on other ones you might ask in the discussion?]]></content:encoded>
          295                 </item>
          296                 <item>
          297                         <title><![CDATA[Nixers Book Club - Book #5: Computer Science from the Bottom Up]]></title>
          298                         <link>https://nixers.net/Thread-Nixers-Book-Club-Book-5-Computer-Science-from-the-Bottom-Up</link>
          299                         <pubDate>Mon, 16 Aug 2021 03:10:42 +0000</pubDate>
          300                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
          301                         <guid isPermaLink="false">https://nixers.net/Thread-Nixers-Book-Club-Book-5-Computer-Science-from-the-Bottom-Up</guid>
          302                         <description><![CDATA[As proposed by Venam, the next book of the Nixer's Book Club is gonna be «<a href="https://www.bottomupcs.com/index.xhtml" target="_blank" rel="noopener" class="mycode_url">Computer Science from the Bottom Up</a>».<br />
          303 <br />
          304 Quoting from its introduction:<br />
          305 <blockquote class="mycode_quote"><cite>Quote:</cite>In a nutshell, what you are reading is intended to be a shop class for computer science. Young computer science students are taught to "drive" the computer; but where do you go to learn what is under the hood? Trying to understand the operating system is unfortunately not as easy as just opening the bonnet. The current Linux kernel runs into the millions of lines of code, add to that the other critical parts of a modern operating system (the compiler, assembler and system libraries) and your code base becomes unimaginable. Further still, add a University level operating systems course (or four), some good reference manuals, two or three years of C experience and, just maybe, you might be able to figure out where to start looking to make sense of it all.<br />
          306 <br />
          307 To keep with the car analogy, the prospective student is starting out trying to work on a Formula One engine without ever knowing how a two stroke motor operates. During their shop class the student should pull apart, twist, turn and put back together that two stroke motor, and consequentially have a pretty good framework for understanding just how the Formula One engine works. Nobody will expect them to be a Formula One engineer, but they are well on their way!</blockquote>
          308 <br />
          309 Chapters are short, so we can do 2 chapters per week.<br />
          310 Our first session will be Aug, 21 (next Saturday), when we will discuss the first two chapters.<br />
          311 See you then!]]></description>
          312                         <content:encoded><![CDATA[As proposed by Venam, the next book of the Nixer's Book Club is gonna be «<a href="https://www.bottomupcs.com/index.xhtml" target="_blank" rel="noopener" class="mycode_url">Computer Science from the Bottom Up</a>».<br />
          313 <br />
          314 Quoting from its introduction:<br />
          315 <blockquote class="mycode_quote"><cite>Quote:</cite>In a nutshell, what you are reading is intended to be a shop class for computer science. Young computer science students are taught to "drive" the computer; but where do you go to learn what is under the hood? Trying to understand the operating system is unfortunately not as easy as just opening the bonnet. The current Linux kernel runs into the millions of lines of code, add to that the other critical parts of a modern operating system (the compiler, assembler and system libraries) and your code base becomes unimaginable. Further still, add a University level operating systems course (or four), some good reference manuals, two or three years of C experience and, just maybe, you might be able to figure out where to start looking to make sense of it all.<br />
          316 <br />
          317 To keep with the car analogy, the prospective student is starting out trying to work on a Formula One engine without ever knowing how a two stroke motor operates. During their shop class the student should pull apart, twist, turn and put back together that two stroke motor, and consequentially have a pretty good framework for understanding just how the Formula One engine works. Nobody will expect them to be a Formula One engineer, but they are well on their way!</blockquote>
          318 <br />
          319 Chapters are short, so we can do 2 chapters per week.<br />
          320 Our first session will be Aug, 21 (next Saturday), when we will discuss the first two chapters.<br />
          321 See you then!]]></content:encoded>
          322                 </item>
          323                 <item>
          324                         <title><![CDATA[How do I Ubuntu ?]]></title>
          325                         <link>https://nixers.net/Thread-How-do-I-Ubuntu</link>
          326                         <pubDate>Fri, 06 Aug 2021 15:36:23 +0000</pubDate>
          327                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=579">z3bra</a>]]></dc:creator>
          328                         <guid isPermaLink="false">https://nixers.net/Thread-How-do-I-Ubuntu</guid>
          329                         <description><![CDATA[Hello folks,<br />
          330 <br />
          331 This thread will be a little awkward (for me at least!).<br />
          332 Next monday, I'll have my work laptop reinstalled under stock Ubuntu 21.04, as per my company's policies.<br />
          333 <br />
          334 The thing is, I have not used a pre-configured distro in years !<br />
          335 I don't want to use the default Gnome shell, or the default software provided with the distro. I don't mind keeping everything installed though, in case a coworker needs to login on my computer (it'll be connected to the active directory).<br />
          336 <br />
          337 So my question will be simple (though the answer might be complex…) :<br />
          338 <br />
          339 <span style="font-weight: bold;" class="mycode_b">How do I <span style="font-style: italic;" class="mycode_i">cleanly</span> change my login session under Ubuntu ?</span><br />
          340 <br />
          341 I basically have my ~/.xsession setup for use with the "xdm" login manager (it is equivalent to an .xinitrc). How do I translate/change it so I can use it under Ubuntu ? I've found that it uses GDM3 and that I'd possibly have to create a .desktop entry to /usr/share/xsessions to launch my own "session script" or whatever. Is that correct ?<br />
          342 <br />
          343 Also, Ubuntu 21.04 ships with Wayland by default. Apparently X is still installed, but I'd like to confirm that if anyone has the info.<br />
          344 <br />
          345 Help me as the Ubuntu login stack is totally unknown to me, and I don't want to loose too much time setting up my machine next week. <br />
          346 <br />
          347 Thanks everyone !]]></description>
          348                         <content:encoded><![CDATA[Hello folks,<br />
          349 <br />
          350 This thread will be a little awkward (for me at least!).<br />
          351 Next monday, I'll have my work laptop reinstalled under stock Ubuntu 21.04, as per my company's policies.<br />
          352 <br />
          353 The thing is, I have not used a pre-configured distro in years !<br />
          354 I don't want to use the default Gnome shell, or the default software provided with the distro. I don't mind keeping everything installed though, in case a coworker needs to login on my computer (it'll be connected to the active directory).<br />
          355 <br />
          356 So my question will be simple (though the answer might be complex…) :<br />
          357 <br />
          358 <span style="font-weight: bold;" class="mycode_b">How do I <span style="font-style: italic;" class="mycode_i">cleanly</span> change my login session under Ubuntu ?</span><br />
          359 <br />
          360 I basically have my ~/.xsession setup for use with the "xdm" login manager (it is equivalent to an .xinitrc). How do I translate/change it so I can use it under Ubuntu ? I've found that it uses GDM3 and that I'd possibly have to create a .desktop entry to /usr/share/xsessions to launch my own "session script" or whatever. Is that correct ?<br />
          361 <br />
          362 Also, Ubuntu 21.04 ships with Wayland by default. Apparently X is still installed, but I'd like to confirm that if anyone has the info.<br />
          363 <br />
          364 Help me as the Ubuntu login stack is totally unknown to me, and I don't want to loose too much time setting up my machine next week. <br />
          365 <br />
          366 Thanks everyone !]]></content:encoded>
          367                 </item>
          368                 <item>
          369                         <title><![CDATA[Nixers Book Club - Review and next book #4]]></title>
          370                         <link>https://nixers.net/Thread-Nixers-Book-Club-Review-and-next-book-4</link>
          371                         <pubDate>Mon, 12 Jul 2021 10:42:59 +0000</pubDate>
          372                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
          373                         <guid isPermaLink="false">https://nixers.net/Thread-Nixers-Book-Club-Review-and-next-book-4</guid>
          374                         <description><![CDATA[<img src="https://i.postimg.cc/WVnqq32c/unixbooks.jpg" alt="[Image: unixbooks.jpg]" class="mycode_img" loading="lazy" /><br />
          375 <br />
          376 We concluded The Art of UNIX Programming on our book club.<br />
          377 What do you though of TAOUP?<br />
          378 Did it change the way you program on UNIX?<br />
          379 <br />
          380 Let's also vote for the next book.<br />
          381 These are the candidates:<br />
          382 <ul class="mycode_list"><li>Introduction to Operating Systems Abstractions Using Plan 9.<br />
          383 </li>
          384 <li>The Design of the UNIX Operating System.<br />
          385 </li>
          386 </ul>
          387 <br />
          388 venam gave the idea on irc to include specs, RFCs and other generic OS books.<br />
          389 If you have another recommendation, please comment.]]></description>
          390                         <content:encoded><![CDATA[<img src="https://i.postimg.cc/WVnqq32c/unixbooks.jpg" alt="[Image: unixbooks.jpg]" class="mycode_img" loading="lazy" /><br />
          391 <br />
          392 We concluded The Art of UNIX Programming on our book club.<br />
          393 What do you though of TAOUP?<br />
          394 Did it change the way you program on UNIX?<br />
          395 <br />
          396 Let's also vote for the next book.<br />
          397 These are the candidates:<br />
          398 <ul class="mycode_list"><li>Introduction to Operating Systems Abstractions Using Plan 9.<br />
          399 </li>
          400 <li>The Design of the UNIX Operating System.<br />
          401 </li>
          402 </ul>
          403 <br />
          404 venam gave the idea on irc to include specs, RFCs and other generic OS books.<br />
          405 If you have another recommendation, please comment.]]></content:encoded>
          406                 </item>
          407                 <item>
          408                         <title><![CDATA[CB UNIX: DevOps before it was cool]]></title>
          409                         <link>https://nixers.net/Thread-CB-UNIX-DevOps-before-it-was-cool</link>
          410                         <pubDate>Wed, 30 Jun 2021 01:50:57 +0000</pubDate>
          411                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1548">jkl</a>]]></dc:creator>
          412                         <guid isPermaLink="false">https://nixers.net/Thread-CB-UNIX-DevOps-before-it-was-cool</guid>
          413                         <description><![CDATA[At least Columbus UNIX - an internally used UNIX at Bell Labs - seems to <a href="https://twitter.com/nabijaczleweli/status/1408801062832807941" target="_blank" rel="noopener" class="mycode_url">have come with</a> the <span style="font-style: italic;" class="mycode_i">allofc</span> command which I could not find in any other system.<br />
          414 <br />
          415 <blockquote class="mycode_quote"><cite>Quote:</cite>The allofc utility program was created to simplify the update/upgrade procedures. Allofc permits a sequence of UNIX commands to be performed in some or all office and type directories.</blockquote>
          416 <br />
          417 Arguably, its usage seems to be less intuitive than you'd think; still looks much less like a big pile of webshit poo than what "modern" "developers" call "DevOps".<br />
          418 <br />
          419 The man page claims that <span style="font-style: italic;" class="mycode_i">allofc</span> came as a part of (a version of) SCCS which makes sense, in a way. I wonder if it has spread into other Unices at some point in time.]]></description>
          420                         <content:encoded><![CDATA[At least Columbus UNIX - an internally used UNIX at Bell Labs - seems to <a href="https://twitter.com/nabijaczleweli/status/1408801062832807941" target="_blank" rel="noopener" class="mycode_url">have come with</a> the <span style="font-style: italic;" class="mycode_i">allofc</span> command which I could not find in any other system.<br />
          421 <br />
          422 <blockquote class="mycode_quote"><cite>Quote:</cite>The allofc utility program was created to simplify the update/upgrade procedures. Allofc permits a sequence of UNIX commands to be performed in some or all office and type directories.</blockquote>
          423 <br />
          424 Arguably, its usage seems to be less intuitive than you'd think; still looks much less like a big pile of webshit poo than what "modern" "developers" call "DevOps".<br />
          425 <br />
          426 The man page claims that <span style="font-style: italic;" class="mycode_i">allofc</span> came as a part of (a version of) SCCS which makes sense, in a way. I wonder if it has spread into other Unices at some point in time.]]></content:encoded>
          427                 </item>
          428                 <item>
          429                         <title><![CDATA[Command-line interface on GUI programs.]]></title>
          430                         <link>https://nixers.net/Thread-Command-line-interface-on-GUI-programs</link>
          431                         <pubDate>Thu, 24 Jun 2021 23:12:01 +0000</pubDate>
          432                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
          433                         <guid isPermaLink="false">https://nixers.net/Thread-Command-line-interface-on-GUI-programs</guid>
          434                         <description><![CDATA[The standard input and output have no use on most GUI applications.<br />
          435 I have found, however, an application that makes use of the standard input for the user to type commands: gnubg, GNU's backgammon game.<br />
          436 <br />
          437 Here's a sample video.  On the video, I first type "new game" to start a new game, then "roll" to roll the dice, "help" to get a dialog window listing known commands, and "move" to move the tokens.  Then, I type ^D (Control+D) to send EOF and close the game.<br />
          438 <br />
          439 <a href="https://0x0.st/-pop.mp4" target="_blank" rel="noopener" class="mycode_url">Here's the video.</a><br />
          440 <br />
          441 This command-based interface is not available when the user opens gnubg(1) from the application menu/start menu, only when the stdin is connected to a terminal.<br />
          442 <br />
          443 However, the commands are fundamental to the game operations: menu entries and the icons on the toolbar are bound to commands (clicking in one of them has the same effect as entering a command on stdin).  You can also run a game from a script either by pipeing it to the stdin; or by running gnubg(1) with the -c option; or from the menu bar on File/Open Commands.<br />
          444 <br />
          445 I found that interface really interesting, because it can be extended and composed with other applications.  The user can run gnubg(1) from a script and call dmenu to run commands from it and/or get a list of commands within dmenu (mimicking HUD on the Unity DE from Ubuntu).<br />
          446 <br />
          447 MacOS' global menu bar can also be mimicked.  We can have a global menu bar in which clicking on a option on the menu bar sends commands to the stdin of the process of the active window.<br />
          448 <br />
          449 This kind of interface: a regular user interface that also interprets command is nothing new on TUI (aka roguelike interfaces): Vim and emacs have a command-line interpreter at the bottom of their windows.  Ranger, lf and other file managers can also interpret commands while also being controlled by usual keybindings.<br />
          450 <br />
          451 With this kind of interface we can bind commands to menu entries, icons, and hotkeys with separate programs like dmenu and sxhkd.<br />
          452 <br />
          453 Something like a command-line interface is being implemented in <a href="https://www.debugpoint.com/2021/05/kcommandbar-kde-feature/" target="_blank" rel="noopener" class="mycode_url">QT5 applications for KDE</a>.  The user can enter commands in a dmenu-like prompt, those commands are interpreted by the toolkit, which will run the corresponding action for the application.<br />
          454 <br />
          455 That kind of GUI interface, so unexplored, influenced me in projecting two different, but related applications: control and xfiles.  Xfiles will be a GUI file manager that reads commands from the stdin.  Control will have server and client processes.  The server is a macOS-like bar with global menu that changes its menus based on the current active window.  The client is a wrapper; calling "control xfiles" will open xfiles with its stdin bound to control, allowing the user to control xfiles (ie., send commands to its stdin) from the global menu bar.  Control will know which process stdin corresponds to which window by means of <a href="https://specifications.freedesktop.org/startup-notification-spec/startup-notification-latest.txt" target="_blank" rel="noopener" class="mycode_url">startup notification</a>.<br />
          456 <br />
          457 Control and xfiles are still in my mind, and will be there for a long time, as I do not have time to work on them (my uni is returning next semester).<br />
          458 <br />
          459 What do you think of a command-line interface (CLI) for GUI applications?<br />
          460 And what do you think in implementing CLI in GUI by means of the standard interface (as gnubg does)?<br />
          461 Are CLI and GUI unrelated or can they be used together?<br />
          462 What do you think of KDE way of implementing CLI in GUI by means of the QT toolkit?<br />
          463 What solution is better: including CLI in GUI via stdin or via toolkit?<br />
          464 <br />
          465 I think that implementing CLI in GUI, while not caring about implementing menu bars, toolbars and keybindings in the application, is the UNIXy way of GUI interfaces: let the actual interface to be done by other programs (dmenu, sxhkd, macos-like global menu, etc), concentrate only on interpreting a little language and separate the interface from the engine.]]></description>
          466                         <content:encoded><![CDATA[The standard input and output have no use on most GUI applications.<br />
          467 I have found, however, an application that makes use of the standard input for the user to type commands: gnubg, GNU's backgammon game.<br />
          468 <br />
          469 Here's a sample video.  On the video, I first type "new game" to start a new game, then "roll" to roll the dice, "help" to get a dialog window listing known commands, and "move" to move the tokens.  Then, I type ^D (Control+D) to send EOF and close the game.<br />
          470 <br />
          471 <a href="https://0x0.st/-pop.mp4" target="_blank" rel="noopener" class="mycode_url">Here's the video.</a><br />
          472 <br />
          473 This command-based interface is not available when the user opens gnubg(1) from the application menu/start menu, only when the stdin is connected to a terminal.<br />
          474 <br />
          475 However, the commands are fundamental to the game operations: menu entries and the icons on the toolbar are bound to commands (clicking in one of them has the same effect as entering a command on stdin).  You can also run a game from a script either by pipeing it to the stdin; or by running gnubg(1) with the -c option; or from the menu bar on File/Open Commands.<br />
          476 <br />
          477 I found that interface really interesting, because it can be extended and composed with other applications.  The user can run gnubg(1) from a script and call dmenu to run commands from it and/or get a list of commands within dmenu (mimicking HUD on the Unity DE from Ubuntu).<br />
          478 <br />
          479 MacOS' global menu bar can also be mimicked.  We can have a global menu bar in which clicking on a option on the menu bar sends commands to the stdin of the process of the active window.<br />
          480 <br />
          481 This kind of interface: a regular user interface that also interprets command is nothing new on TUI (aka roguelike interfaces): Vim and emacs have a command-line interpreter at the bottom of their windows.  Ranger, lf and other file managers can also interpret commands while also being controlled by usual keybindings.<br />
          482 <br />
          483 With this kind of interface we can bind commands to menu entries, icons, and hotkeys with separate programs like dmenu and sxhkd.<br />
          484 <br />
          485 Something like a command-line interface is being implemented in <a href="https://www.debugpoint.com/2021/05/kcommandbar-kde-feature/" target="_blank" rel="noopener" class="mycode_url">QT5 applications for KDE</a>.  The user can enter commands in a dmenu-like prompt, those commands are interpreted by the toolkit, which will run the corresponding action for the application.<br />
          486 <br />
          487 That kind of GUI interface, so unexplored, influenced me in projecting two different, but related applications: control and xfiles.  Xfiles will be a GUI file manager that reads commands from the stdin.  Control will have server and client processes.  The server is a macOS-like bar with global menu that changes its menus based on the current active window.  The client is a wrapper; calling "control xfiles" will open xfiles with its stdin bound to control, allowing the user to control xfiles (ie., send commands to its stdin) from the global menu bar.  Control will know which process stdin corresponds to which window by means of <a href="https://specifications.freedesktop.org/startup-notification-spec/startup-notification-latest.txt" target="_blank" rel="noopener" class="mycode_url">startup notification</a>.<br />
          488 <br />
          489 Control and xfiles are still in my mind, and will be there for a long time, as I do not have time to work on them (my uni is returning next semester).<br />
          490 <br />
          491 What do you think of a command-line interface (CLI) for GUI applications?<br />
          492 And what do you think in implementing CLI in GUI by means of the standard interface (as gnubg does)?<br />
          493 Are CLI and GUI unrelated or can they be used together?<br />
          494 What do you think of KDE way of implementing CLI in GUI by means of the QT toolkit?<br />
          495 What solution is better: including CLI in GUI via stdin or via toolkit?<br />
          496 <br />
          497 I think that implementing CLI in GUI, while not caring about implementing menu bars, toolbars and keybindings in the application, is the UNIXy way of GUI interfaces: let the actual interface to be done by other programs (dmenu, sxhkd, macos-like global menu, etc), concentrate only on interpreting a little language and separate the interface from the engine.]]></content:encoded>
          498                 </item>
          499                 <item>
          500                         <title><![CDATA[Dmenu Scripts]]></title>
          501                         <link>https://nixers.net/Thread-Dmenu-Scripts</link>
          502                         <pubDate>Wed, 09 Jun 2021 06:38:22 +0000</pubDate>
          503                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=2034">pfr</a>]]></dc:creator>
          504                         <guid isPermaLink="false">https://nixers.net/Thread-Dmenu-Scripts</guid>
          505                         <description><![CDATA[While I acknowledge the following threads exist:<ul class="mycode_list"><li><a href="https://nixers.net/Thread-Scripts-to-be-quick-and-efficient?highlight=dmenu%2Bscripts" target="_blank" rel="noopener" class="mycode_url">Scripts-to-be-quick-and-efficient</a><br />
          506 </li>
          507 <li><a href="https://nixers.net/Thread-What-software-have-you-made-to-improve-your-workflow-or-rice?highlight=dmenu%2Bscripts" target="_blank" rel="noopener" class="mycode_url">What-software-have-you-made-to-improve-your-workflow-or-rice?</a><br />
          508 </li>
          509 </ul>
          510 I still think there is a need for a dedicated thread for dmenu scripts. dmenu is so widely used and is so versatile, resulting in an endless list of scripting possibilities, it would be nice to have them all in one place here on nixers.net.<br />
          511 <br />
          512 Cyr4x3 had a few cool looking scripts in their recent <a href="https://nixers.net/Thread-Workflow-Compilation-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">workflow</a> video which sparked my interest. <br />
          513 <br />
          514 Feel free to drop in some helpful scripts to extend dmenu's capabilities in this thread. <br />
          515 The one I'm interested in at the moment is a <a href="https://forum.archlabslinux.com/t/the-great-dmenu-thread/4062/2" target="_blank" rel="noopener" class="mycode_url">screenshot script</a> that also allows for editing and uploading of screenshots. <span style="font-weight: bold;" class="mycode_b">I am however looking for some help</span> to replace <a href="https://paste.xinu.at/" target="_blank" rel="noopener" class="mycode_url">fb</a> with xero's <a href="https://github.com/xero/dotfiles/blob/master/bin/bin/pb" target="_blank" rel="noopener" class="mycode_url">pb</a> or just simply use curl to upload to 0x0. The thing I like most about this script is that, in addition to using xclip to copy the url to the clipboard, the upload option also sends the url through notify-send which (in gnome at least) is a clickable link. <br />
          516 <br />
          517 I hope some of you have more scripts to share.<br />
          518 <br />
          519 One of my most used is <a href="https://git.zx2c4.com/password-store/tree/contrib/dmenu/passmenu" target="_blank" rel="noopener" class="mycode_url">passmenu</a> which is now baked into pass itself. <br />
          520 <br />
          521 You've also got old mate dt <a href="https://gitlab.com/dwt1/dmscripts" target="_blank" rel="noopener" class="mycode_url">over here</a> with his bunch of scripts. <br />
          522 <a href="https://github.com/debxp/dmenu-scripts" target="_blank" rel="noopener" class="mycode_url">debxp</a> and <a href="https://github.com/I-LeCorbeau/dmenu-scripts" target="_blank" rel="noopener" class="mycode_url">I-LeCorbeau</a> also have a few. <br />
          523 <br />
          524 I don't have anything of my own to offer up, this is purely a selfish script trawling mission. <br />
          525 <br />
          526 Also feel free to mention/promote any dmenu alternatives or replacements (Philbush I'm looking at you - xmenu looks awesome), just keep any scripts in this thread dmenu specific to avoid confusion.]]></description>
          527                         <content:encoded><![CDATA[While I acknowledge the following threads exist:<ul class="mycode_list"><li><a href="https://nixers.net/Thread-Scripts-to-be-quick-and-efficient?highlight=dmenu%2Bscripts" target="_blank" rel="noopener" class="mycode_url">Scripts-to-be-quick-and-efficient</a><br />
          528 </li>
          529 <li><a href="https://nixers.net/Thread-What-software-have-you-made-to-improve-your-workflow-or-rice?highlight=dmenu%2Bscripts" target="_blank" rel="noopener" class="mycode_url">What-software-have-you-made-to-improve-your-workflow-or-rice?</a><br />
          530 </li>
          531 </ul>
          532 I still think there is a need for a dedicated thread for dmenu scripts. dmenu is so widely used and is so versatile, resulting in an endless list of scripting possibilities, it would be nice to have them all in one place here on nixers.net.<br />
          533 <br />
          534 Cyr4x3 had a few cool looking scripts in their recent <a href="https://nixers.net/Thread-Workflow-Compilation-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">workflow</a> video which sparked my interest. <br />
          535 <br />
          536 Feel free to drop in some helpful scripts to extend dmenu's capabilities in this thread. <br />
          537 The one I'm interested in at the moment is a <a href="https://forum.archlabslinux.com/t/the-great-dmenu-thread/4062/2" target="_blank" rel="noopener" class="mycode_url">screenshot script</a> that also allows for editing and uploading of screenshots. <span style="font-weight: bold;" class="mycode_b">I am however looking for some help</span> to replace <a href="https://paste.xinu.at/" target="_blank" rel="noopener" class="mycode_url">fb</a> with xero's <a href="https://github.com/xero/dotfiles/blob/master/bin/bin/pb" target="_blank" rel="noopener" class="mycode_url">pb</a> or just simply use curl to upload to 0x0. The thing I like most about this script is that, in addition to using xclip to copy the url to the clipboard, the upload option also sends the url through notify-send which (in gnome at least) is a clickable link. <br />
          538 <br />
          539 I hope some of you have more scripts to share.<br />
          540 <br />
          541 One of my most used is <a href="https://git.zx2c4.com/password-store/tree/contrib/dmenu/passmenu" target="_blank" rel="noopener" class="mycode_url">passmenu</a> which is now baked into pass itself. <br />
          542 <br />
          543 You've also got old mate dt <a href="https://gitlab.com/dwt1/dmscripts" target="_blank" rel="noopener" class="mycode_url">over here</a> with his bunch of scripts. <br />
          544 <a href="https://github.com/debxp/dmenu-scripts" target="_blank" rel="noopener" class="mycode_url">debxp</a> and <a href="https://github.com/I-LeCorbeau/dmenu-scripts" target="_blank" rel="noopener" class="mycode_url">I-LeCorbeau</a> also have a few. <br />
          545 <br />
          546 I don't have anything of my own to offer up, this is purely a selfish script trawling mission. <br />
          547 <br />
          548 Also feel free to mention/promote any dmenu alternatives or replacements (Philbush I'm looking at you - xmenu looks awesome), just keep any scripts in this thread dmenu specific to avoid confusion.]]></content:encoded>
          549                 </item>
          550                 <item>
          551                         <title><![CDATA[A Week of Trial [June Events 2021]]]></title>
          552                         <link>https://nixers.net/Thread-A-Week-of-Trial-June-Events-2021</link>
          553                         <pubDate>Tue, 01 Jun 2021 15:07:29 +0000</pubDate>
          554                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=80">venam</a>]]></dc:creator>
          555                         <guid isPermaLink="false">https://nixers.net/Thread-A-Week-of-Trial-June-Events-2021</guid>
          556                         <description><![CDATA[This is part of the <a href="https://nixers.net/Thread-The-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">June events</a>.<br />
          557 <br />
          558 In previous years we've had the <a href="https://nixers.net/Thread-A-Week-In-The-TTY" target="_blank" rel="noopener" class="mycode_url">"Week in the TTY"</a> where we forced ourselves to only use the TTY for an entire week.<br />
          559 This time, let's just make it either a full week in the TTY or a vintage OS/software stack/very limited hardware.<br />
          560 <br />
          561 The week should be between Friday 25th and Wednesday the 30th of June.<br />
          562 <br />
          563 Bump this thread with what you intend to try out during that week, be it the original week in the TTY or something else. Then when the week ends you can post what you've discovered.<br />
          564 <br />
          565 Here are some ideas for the TTY:<br />
          566 <br />
          567 Get comfortable with terminal multiplexers, the command line in general, command line and curses games, emailing from the cli, browsing the internet from the TTY through protocols you might not have tried such as gemini or gopher, chat from the cli, manage offline documentation, and more...]]></description>
          568                         <content:encoded><![CDATA[This is part of the <a href="https://nixers.net/Thread-The-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">June events</a>.<br />
          569 <br />
          570 In previous years we've had the <a href="https://nixers.net/Thread-A-Week-In-The-TTY" target="_blank" rel="noopener" class="mycode_url">"Week in the TTY"</a> where we forced ourselves to only use the TTY for an entire week.<br />
          571 This time, let's just make it either a full week in the TTY or a vintage OS/software stack/very limited hardware.<br />
          572 <br />
          573 The week should be between Friday 25th and Wednesday the 30th of June.<br />
          574 <br />
          575 Bump this thread with what you intend to try out during that week, be it the original week in the TTY or something else. Then when the week ends you can post what you've discovered.<br />
          576 <br />
          577 Here are some ideas for the TTY:<br />
          578 <br />
          579 Get comfortable with terminal multiplexers, the command line in general, command line and curses games, emailing from the cli, browsing the internet from the TTY through protocols you might not have tried such as gemini or gopher, chat from the cli, manage offline documentation, and more...]]></content:encoded>
          580                 </item>
          581                 <item>
          582                         <title><![CDATA[Workflow Compilation [June Events 2021]]]></title>
          583                         <link>https://nixers.net/Thread-Workflow-Compilation-June-Events-2021</link>
          584                         <pubDate>Tue, 01 Jun 2021 15:05:47 +0000</pubDate>
          585                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=80">venam</a>]]></dc:creator>
          586                         <guid isPermaLink="false">https://nixers.net/Thread-Workflow-Compilation-June-Events-2021</guid>
          587                         <description><![CDATA[This is part of the <a href="https://nixers.net/Thread-The-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">June events</a>.<br />
          588 <br />
          589 Time to show off your workflow to everyone! You know the concept.<br />
          590 <br />
          591 <span style="font-weight: bold;" class="mycode_b">What is it ?</span><br />
          592 This is a video compiling a bunch of screencast from the nixers members, all performing the same task, but using their personal setup.<br />
          593 this would result in a compilation showing the personal workflow of each participant, and setting a comparison point between them.<br />
          594 <br />
          595 <span style="font-weight: bold;" class="mycode_b">Can I participate ?</span><br />
          596 Sure ! The more videos we get, the better. Just post your submission and we'll add it !<br />
          597 <br />
          598 <br />
          599 <span style="font-weight: bold;" class="mycode_b">What are the rules ?</span><br />
          600 1. Nixers will have to perform the tasks in the exact order they are listed (see below).<br />
          601 2. Nixers must use a single monitor for the screencast<br />
          602 3. Nixers' screen resolution should be above 1280x720<br />
          603 4. Nixers submissions should be in webm format<br />
          604 5. Nixers should submit their compilation before <span style="font-weight: bold;" class="mycode_b">2021-06-30 at midnight (UTC)</span><br />
          605 <br />
          606 <span style="font-weight: bold;" class="mycode_b">How can I record the video ?</span><br />
          607 The command to use is the following (adjust the resolution to fit your actual setup, it might also vary as you may find the recording too fast):<br />
          608 <br />
          609 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=&#36;(xwininfo -root | sed -nE 's/-geometry[[:space:]]([[:digit:]]+x[[:digit:]]+)+.*&#36;/&#92;1/p')</code></div></div><br />
          610 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          611 ffmpeg -f x11grab -s &#36;RESOLUTION -an -r 16 -loglevel quiet -i :0.0 -b:v 5M -y workflow-compil-&#36;{USER}.webm</code></div></div><br />
          612 Another example<br />
          613 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          614 ffmpeg -thread_queue_size 128 -f x11grab -r 30 -s &#36;RESOLUTION -i :0.0 -vcodec libx264 -preset ultrafast -threads 0 -y output.mkv<br />
          615 ffmpeg -i output.mkv workflow-compil-&#36;{USER}.webm</code></div></div><br />
          616 For those running OSX:<br />
          617 <br />
          618 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          619 ffmpeg -f avfoundation -s &#36;RESOLUTION -an -r 16 -loglevel quiet -i 0:none -b:v 5M -y workflow-compil-&#36;{USER}.webm</code></div></div><br />
          620 To end the video, press `q`.<br />
          621 <br />
          622 <span style="font-weight: bold;" class="mycode_b">What is the task list ?</span><br />
          623 <ul class="mycode_list"><li>Put on some music<br />
          624 </li>
          625 <li>Write some random text to a file in /tmp<br />
          626 </li>
          627 <li>Show "toilet", "figlet", ASCII art, and try it in a funny way !<br />
          628 </li>
          629 <li>Install a simple software (show pkg management)<br />
          630 </li>
          631 <li>Set a wallpaper<br />
          632 </li>
          633 <li>Take a scrot ( beautify it if you must ) and upload it to a pastebin of your choice<br />
          634 </li>
          635 <li>Join the IRC and paste the link to the scrot in <span style="font-weight: bold;" class="mycode_b">#nixers</span><br />
          636 </li>
          637 <li>Check your RSS feed (optional)<br />
          638 </li>
          639 <li>Browse the forum (post something on this thread, you'll edit it later with the actual link of the video)<br />
          640 </li>
          641 </ul>
          642 <br />
          643 <br />
          644 <span style="font-weight: bold;" class="mycode_b">Submissions</span><ul class="mycode_list"><li><a href="http://fixedpoints.zapto.org/workflow-compil-opfez.webm" target="_blank" rel="noopener" class="mycode_url">opfez</a><br />
          645 </li>
          646 <li><a href="https://transfer.sh/get/1PEN5mH/workflow-compil-prx.webm" target="_blank" rel="noopener" class="mycode_url">prx*</a><br />
          647 </li>
          648 <li><a href="https://movq.de/v/644d98f311/2021-nixers-workflow-compil-movq.webm" target="_blank" rel="noopener" class="mycode_url">movq</a><br />
          649 </li>
          650 <li><a href="https://perso.pw/f/RofdGjw5AJ6tbLSuQMiXPQ.webm" target="_blank" rel="noopener" class="mycode_url">solene</a><br />
          651 </li>
          652 <li><a href="https://upload.disroot.org/r/5hKve4UH#ha5IdKEwIhQneSRsouw6COkcHj0jH+lgx6K4XTi77Rs=" target="_blank" rel="noopener" class="mycode_url">phillbush</a><br />
          653 </li>
          654 <li><a href="https://venam.nixers.net/2021-nixers-workflow-compil-vnm.webm" target="_blank" rel="noopener" class="mycode_url">venam</a><br />
          655 </li>
          656 <li><a href="https://tmp.c0de.in/workflow-compil-jolia.webm" target="_blank" rel="noopener" class="mycode_url">jolia</a><br />
          657 </li>
          658 <li><a href="https://transfer.sh/1ubJjNZ/workflow-remiferous.webm" target="_blank" rel="noopener" class="mycode_url">ramiferous</a><br />
          659 </li>
          660 <li><a href="https://p.mort.coffee/2jR.webm" target="_blank" rel="noopener" class="mycode_url">mort</a><br />
          661 </li>
          662 <li><a href="https://transfer.sh/u/workflow-compil-cyr4x3.webm" target="_blank" rel="noopener" class="mycode_url">cyr4x3</a><br />
          663 </li>
          664 <li><a href="https://upload.disroot.org/r/8NaJ7XLX#4VqQHIKbJao5qd7DoOaDnEW9atZo+V+hrkovsUkTUqE=" target="_blank" rel="noopener" class="mycode_url">tuxifreund</a><br />
          665 </li>
          666 <li><a href="https://transfer.sh/1yV36Bc/workflow-compil-dany74q.webm" target="_blank" rel="noopener" class="mycode_url">dany74q</a><br />
          667 </li>
          668 <li><a href="https://pyratebeard.net/20210701-nixers_workflow.webm" target="_blank" rel="noopener" class="mycode_url">pyratebeard</a><br />
          669 </li>
          670 </ul>
          671 <br />
          672 <br />
          673 <hr class="mycode_hr" />
          674 <br />
          675 Previous threads: <a href="https://nixers.net/showthread.php?tid=1606" target="_blank" rel="noopener" class="mycode_url">#1</a>, <a href="https://nixers.net/showthread.php?tid=2130" target="_blank" rel="noopener" class="mycode_url">#2</a>, &amp; <a href="https://nixers.net/Thread-Workflow-Compilation-2020-finished" target="_blank" rel="noopener" class="mycode_url">#3</a>.<br />
          676 <br />
          677 <hr class="mycode_hr" />
          678 <br />
          679 Feel free to add more information about your setup as others might be interested in knowing what is actually running in the video. Otherwise, hope on <a href="https://nixers.net/Thread-IRC--1876" target="_blank" rel="noopener" class="mycode_url">IRC</a> and ask.<br />
          680 <br />
          681 <hr class="mycode_hr" />
          682 <br />
          683 Have fun!<br />
          684 <br />
          685 <hr class="mycode_hr" />
          686 <br />
          687 The result has been uploaded as <a href="https://nixers.net/images/2021-nixers-workflow-compilation.webm" target="_blank" rel="noopener" class="mycode_url">webm</a>, on a <a href="https://www.youtube.com/watch?v=PvsanPakB_g" target="_blank" rel="noopener" class="mycode_url">YouTube mirror</a>, on <a href="https://movq.de/h/d6b8c3fb8/2021-nixers-workflow-compilation.webm" target="_blank" rel="noopener" class="mycode_url">movq mirror</a>]]></description>
          688                         <content:encoded><![CDATA[This is part of the <a href="https://nixers.net/Thread-The-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">June events</a>.<br />
          689 <br />
          690 Time to show off your workflow to everyone! You know the concept.<br />
          691 <br />
          692 <span style="font-weight: bold;" class="mycode_b">What is it ?</span><br />
          693 This is a video compiling a bunch of screencast from the nixers members, all performing the same task, but using their personal setup.<br />
          694 this would result in a compilation showing the personal workflow of each participant, and setting a comparison point between them.<br />
          695 <br />
          696 <span style="font-weight: bold;" class="mycode_b">Can I participate ?</span><br />
          697 Sure ! The more videos we get, the better. Just post your submission and we'll add it !<br />
          698 <br />
          699 <br />
          700 <span style="font-weight: bold;" class="mycode_b">What are the rules ?</span><br />
          701 1. Nixers will have to perform the tasks in the exact order they are listed (see below).<br />
          702 2. Nixers must use a single monitor for the screencast<br />
          703 3. Nixers' screen resolution should be above 1280x720<br />
          704 4. Nixers submissions should be in webm format<br />
          705 5. Nixers should submit their compilation before <span style="font-weight: bold;" class="mycode_b">2021-06-30 at midnight (UTC)</span><br />
          706 <br />
          707 <span style="font-weight: bold;" class="mycode_b">How can I record the video ?</span><br />
          708 The command to use is the following (adjust the resolution to fit your actual setup, it might also vary as you may find the recording too fast):<br />
          709 <br />
          710 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=&#36;(xwininfo -root | sed -nE 's/-geometry[[:space:]]([[:digit:]]+x[[:digit:]]+)+.*&#36;/&#92;1/p')</code></div></div><br />
          711 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          712 ffmpeg -f x11grab -s &#36;RESOLUTION -an -r 16 -loglevel quiet -i :0.0 -b:v 5M -y workflow-compil-&#36;{USER}.webm</code></div></div><br />
          713 Another example<br />
          714 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          715 ffmpeg -thread_queue_size 128 -f x11grab -r 30 -s &#36;RESOLUTION -i :0.0 -vcodec libx264 -preset ultrafast -threads 0 -y output.mkv<br />
          716 ffmpeg -i output.mkv workflow-compil-&#36;{USER}.webm</code></div></div><br />
          717 For those running OSX:<br />
          718 <br />
          719 <div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>RESOLUTION=1440x900<br />
          720 ffmpeg -f avfoundation -s &#36;RESOLUTION -an -r 16 -loglevel quiet -i 0:none -b:v 5M -y workflow-compil-&#36;{USER}.webm</code></div></div><br />
          721 To end the video, press `q`.<br />
          722 <br />
          723 <span style="font-weight: bold;" class="mycode_b">What is the task list ?</span><br />
          724 <ul class="mycode_list"><li>Put on some music<br />
          725 </li>
          726 <li>Write some random text to a file in /tmp<br />
          727 </li>
          728 <li>Show "toilet", "figlet", ASCII art, and try it in a funny way !<br />
          729 </li>
          730 <li>Install a simple software (show pkg management)<br />
          731 </li>
          732 <li>Set a wallpaper<br />
          733 </li>
          734 <li>Take a scrot ( beautify it if you must ) and upload it to a pastebin of your choice<br />
          735 </li>
          736 <li>Join the IRC and paste the link to the scrot in <span style="font-weight: bold;" class="mycode_b">#nixers</span><br />
          737 </li>
          738 <li>Check your RSS feed (optional)<br />
          739 </li>
          740 <li>Browse the forum (post something on this thread, you'll edit it later with the actual link of the video)<br />
          741 </li>
          742 </ul>
          743 <br />
          744 <br />
          745 <span style="font-weight: bold;" class="mycode_b">Submissions</span><ul class="mycode_list"><li><a href="http://fixedpoints.zapto.org/workflow-compil-opfez.webm" target="_blank" rel="noopener" class="mycode_url">opfez</a><br />
          746 </li>
          747 <li><a href="https://transfer.sh/get/1PEN5mH/workflow-compil-prx.webm" target="_blank" rel="noopener" class="mycode_url">prx*</a><br />
          748 </li>
          749 <li><a href="https://movq.de/v/644d98f311/2021-nixers-workflow-compil-movq.webm" target="_blank" rel="noopener" class="mycode_url">movq</a><br />
          750 </li>
          751 <li><a href="https://perso.pw/f/RofdGjw5AJ6tbLSuQMiXPQ.webm" target="_blank" rel="noopener" class="mycode_url">solene</a><br />
          752 </li>
          753 <li><a href="https://upload.disroot.org/r/5hKve4UH#ha5IdKEwIhQneSRsouw6COkcHj0jH+lgx6K4XTi77Rs=" target="_blank" rel="noopener" class="mycode_url">phillbush</a><br />
          754 </li>
          755 <li><a href="https://venam.nixers.net/2021-nixers-workflow-compil-vnm.webm" target="_blank" rel="noopener" class="mycode_url">venam</a><br />
          756 </li>
          757 <li><a href="https://tmp.c0de.in/workflow-compil-jolia.webm" target="_blank" rel="noopener" class="mycode_url">jolia</a><br />
          758 </li>
          759 <li><a href="https://transfer.sh/1ubJjNZ/workflow-remiferous.webm" target="_blank" rel="noopener" class="mycode_url">ramiferous</a><br />
          760 </li>
          761 <li><a href="https://p.mort.coffee/2jR.webm" target="_blank" rel="noopener" class="mycode_url">mort</a><br />
          762 </li>
          763 <li><a href="https://transfer.sh/u/workflow-compil-cyr4x3.webm" target="_blank" rel="noopener" class="mycode_url">cyr4x3</a><br />
          764 </li>
          765 <li><a href="https://upload.disroot.org/r/8NaJ7XLX#4VqQHIKbJao5qd7DoOaDnEW9atZo+V+hrkovsUkTUqE=" target="_blank" rel="noopener" class="mycode_url">tuxifreund</a><br />
          766 </li>
          767 <li><a href="https://transfer.sh/1yV36Bc/workflow-compil-dany74q.webm" target="_blank" rel="noopener" class="mycode_url">dany74q</a><br />
          768 </li>
          769 <li><a href="https://pyratebeard.net/20210701-nixers_workflow.webm" target="_blank" rel="noopener" class="mycode_url">pyratebeard</a><br />
          770 </li>
          771 </ul>
          772 <br />
          773 <br />
          774 <hr class="mycode_hr" />
          775 <br />
          776 Previous threads: <a href="https://nixers.net/showthread.php?tid=1606" target="_blank" rel="noopener" class="mycode_url">#1</a>, <a href="https://nixers.net/showthread.php?tid=2130" target="_blank" rel="noopener" class="mycode_url">#2</a>, &amp; <a href="https://nixers.net/Thread-Workflow-Compilation-2020-finished" target="_blank" rel="noopener" class="mycode_url">#3</a>.<br />
          777 <br />
          778 <hr class="mycode_hr" />
          779 <br />
          780 Feel free to add more information about your setup as others might be interested in knowing what is actually running in the video. Otherwise, hope on <a href="https://nixers.net/Thread-IRC--1876" target="_blank" rel="noopener" class="mycode_url">IRC</a> and ask.<br />
          781 <br />
          782 <hr class="mycode_hr" />
          783 <br />
          784 Have fun!<br />
          785 <br />
          786 <hr class="mycode_hr" />
          787 <br />
          788 The result has been uploaded as <a href="https://nixers.net/images/2021-nixers-workflow-compilation.webm" target="_blank" rel="noopener" class="mycode_url">webm</a>, on a <a href="https://www.youtube.com/watch?v=PvsanPakB_g" target="_blank" rel="noopener" class="mycode_url">YouTube mirror</a>, on <a href="https://movq.de/h/d6b8c3fb8/2021-nixers-workflow-compilation.webm" target="_blank" rel="noopener" class="mycode_url">movq mirror</a>]]></content:encoded>
          789                 </item>
          790                 <item>
          791                         <title><![CDATA[The June Events [2021]]]></title>
          792                         <link>https://nixers.net/Thread-The-June-Events-2021</link>
          793                         <pubDate>Tue, 01 Jun 2021 15:04:09 +0000</pubDate>
          794                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=80">venam</a>]]></dc:creator>
          795                         <guid isPermaLink="false">https://nixers.net/Thread-The-June-Events-2021</guid>
          796                         <description><![CDATA[The past years (<a href="https://nixers.net/Thread-The-June-Events" target="_blank" rel="noopener" class="mycode_url">1</a>, <a href="https://nixers.net/Thread-June-2017-Events" target="_blank" rel="noopener" class="mycode_url">2</a>, <a href="https://nixers.net/Thread-Unix-Weekly-Challenges" target="_blank" rel="noopener" class="mycode_url">3</a>, etc..) during the month of June we try to organize some events.<br />
          797 <br />
          798 So let's get some activities going on for this year.<br />
          799 I'll create separate threads for them.<br />
          800 <ul class="mycode_list"><li><a href="https://nixers.net/Thread-Workflow-Compilation-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">A workflow compilation thread</a><br />
          801 </li>
          802 <li><a href="https://nixers.net/Thread-A-Week-of-Trial-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">A week of trial</a> (Week in the TTY mixed with vintage OS)<br />
          803 </li>
          804 </ul>
          805 <br />
          806 Feel free to propose other ideas and share feedback here.]]></description>
          807                         <content:encoded><![CDATA[The past years (<a href="https://nixers.net/Thread-The-June-Events" target="_blank" rel="noopener" class="mycode_url">1</a>, <a href="https://nixers.net/Thread-June-2017-Events" target="_blank" rel="noopener" class="mycode_url">2</a>, <a href="https://nixers.net/Thread-Unix-Weekly-Challenges" target="_blank" rel="noopener" class="mycode_url">3</a>, etc..) during the month of June we try to organize some events.<br />
          808 <br />
          809 So let's get some activities going on for this year.<br />
          810 I'll create separate threads for them.<br />
          811 <ul class="mycode_list"><li><a href="https://nixers.net/Thread-Workflow-Compilation-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">A workflow compilation thread</a><br />
          812 </li>
          813 <li><a href="https://nixers.net/Thread-A-Week-of-Trial-June-Events-2021" target="_blank" rel="noopener" class="mycode_url">A week of trial</a> (Week in the TTY mixed with vintage OS)<br />
          814 </li>
          815 </ul>
          816 <br />
          817 Feel free to propose other ideas and share feedback here.]]></content:encoded>
          818                 </item>
          819                 <item>
          820                         <title><![CDATA[What is your coding style?]]></title>
          821                         <link>https://nixers.net/Thread-What-is-your-coding-style</link>
          822                         <pubDate>Tue, 25 May 2021 14:43:41 +0000</pubDate>
          823                         <dc:creator><![CDATA[<a href="https://nixers.net/member.php?action=profile&uid=1965">seninha</a>]]></dc:creator>
          824                         <guid isPermaLink="false">https://nixers.net/Thread-What-is-your-coding-style</guid>
          825                         <description><![CDATA[Recently I have been reading other people's coding style.<br />
          826 I have read <a href="http://doc.cat-v.org/bell_labs/pikestyle" target="_blank" rel="noopener" class="mycode_url">Rob Pike's</a>, <a href="https://suckless.org/coding_style/" target="_blank" rel="noopener" class="mycode_url">suckless'</a>, some <a href="http://aiju.de/misc/c-style" target="_blank" rel="noopener" class="mycode_url">9front</a> <a href="https://ftrv.se/3" target="_blank" rel="noopener" class="mycode_url">developers'</a>, and <a href="https://nxr.netbsd.org/xref/src/share/misc/style" target="_blank" rel="noopener" class="mycode_url">NetBSD</a> and <a href="https://man.openbsd.org/style.9" target="_blank" rel="noopener" class="mycode_url">OpenBSD</a> coding styles.<br />
          827 Those documents inspired me to write down all the subjective practices I have in my mind into objective conventions. And thus I wrote <a href="https://github.com/phillbush/home/blob/master/style.txt" target="_blank" rel="noopener" class="mycode_url">my coding style</a>.<br />
          828 <br />
          829 What do you think of those coding styles?<br />
          830 Do they enforce good practice or are they too normative to be feasible?<br />
          831 Do you have a coding style you follow in your projects? If yes, why not writing it down?]]></description>
          832                         <content:encoded><![CDATA[Recently I have been reading other people's coding style.<br />
          833 I have read <a href="http://doc.cat-v.org/bell_labs/pikestyle" target="_blank" rel="noopener" class="mycode_url">Rob Pike's</a>, <a href="https://suckless.org/coding_style/" target="_blank" rel="noopener" class="mycode_url">suckless'</a>, some <a href="http://aiju.de/misc/c-style" target="_blank" rel="noopener" class="mycode_url">9front</a> <a href="https://ftrv.se/3" target="_blank" rel="noopener" class="mycode_url">developers'</a>, and <a href="https://nxr.netbsd.org/xref/src/share/misc/style" target="_blank" rel="noopener" class="mycode_url">NetBSD</a> and <a href="https://man.openbsd.org/style.9" target="_blank" rel="noopener" class="mycode_url">OpenBSD</a> coding styles.<br />
          834 Those documents inspired me to write down all the subjective practices I have in my mind into objective conventions. And thus I wrote <a href="https://github.com/phillbush/home/blob/master/style.txt" target="_blank" rel="noopener" class="mycode_url">my coding style</a>.<br />
          835 <br />
          836 What do you think of those coding styles?<br />
          837 Do they enforce good practice or are they too normative to be feasible?<br />
          838 Do you have a coding style you follow in your projects? If yes, why not writing it down?]]></content:encoded>
          839                 </item>
          840         </channel>
          841