<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Base (Posts about productivity)</title><link>https://bgstack15.ddns.net/blog/</link><description></description><atom:link href="https://bgstack15.ddns.net/blog/categories/productivity.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2022 &lt;a href="mailto:bgstack15@gmail.com"&gt;bgstack15&lt;/a&gt; 
&lt;a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"&gt;
&lt;img alt="Creative Commons License BY-SA"
style="border-width:0; margin-bottom:12px;"
src="https://bgstack15.ddns.net/.images/l_by-sa_4.0_88x31.png"&gt;&lt;/a&gt;</copyright><lastBuildDate>Mon, 14 Mar 2022 18:59:15 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Save common commands on this server to .useful file</title><link>https://bgstack15.ddns.net/blog/posts/2020/05/29/save-common-commands-on-this-server-to-useful-file/</link><dc:creator>bgstack15</dc:creator><description>&lt;p&gt;Command line productivity takes many forms. Some people live by bash
autocompletion. I disdained it when I first started using bash (coming from
ksh93) but over time realized that it's a fantastic method for discovery (it's
much more complete on Debian-based distros than Fedora-based ones) and ease of
use when typing long pathnames. When you manage a disparate set of systems,
and there are some tasks you repeat often, you usually try to list history and
find the useful commands. One of mine:&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="n"&gt;sudo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="k"&gt;var&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;storage1&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;shares&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;www&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;example&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;repo&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;devuan&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;deb&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;update&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;devuan&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;deb&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;sh&lt;/span&gt;&lt;span class="w"&gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;But over time, I have many commands I log in for, just to run the one command,
and log out. So I have started using a text file: &lt;strong&gt;~/.useful&lt;/strong&gt;. Inside this
file, place your oneliners. So whenever you log onto a box, and you need to
see what commands you run here commonly, check what you've saved:&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;cat ~/.useful
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Of course, it's only useful if you bother to populate it.&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="n"&gt;echo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s1"&gt;'vi $( newest /var/log/debmirror/ log )'&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;~/.&lt;/span&gt;&lt;span class="n"&gt;useful&lt;/span&gt;&lt;span class="w"&gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;</description><category>autocomplete</category><category>bash</category><category>cli</category><category>oneliner</category><category>productivity</category><guid>https://bgstack15.ddns.net/blog/posts/2020/05/29/save-common-commands-on-this-server-to-useful-file/</guid><pubDate>Fri, 29 May 2020 12:34:11 GMT</pubDate></item><item><title>KDE always show keyboard underscores</title><link>https://bgstack15.ddns.net/blog/posts/2017/05/01/kde-always-show-keyboard-underscores/</link><dc:creator>bgstack15</dc:creator><description>&lt;h2&gt;Overview&lt;/h2&gt;
&lt;p&gt;I like to use the keyboard to interact with my computer, even in the gui. On
my KDE system, I wanted my accelerator keys to always be visible. I had to
poke around the World Wide Web for a while to find out exactly how to do that.
These instructions are valid for kdelibs 6:4.14.30-1.fc25.&lt;/p&gt;
&lt;h2&gt;KDE always show accelerator keys&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Open up "System Settings" application.&lt;/li&gt;
&lt;li&gt;Select "Application Style."&lt;/li&gt;
&lt;li&gt;Select "Widget Style" tab.&lt;/li&gt;
&lt;li&gt;Select "Configure..." button beside Widget style.&lt;a href="https://bgstack15.ddns.net/blog/2017/04/configure-breeze.png"&gt;&lt;img alt="" src="https://bgstack15.ddns.net/blog/2017/04/configure-breeze.png"&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Adjust "Keyboard accelerators visibility" to "Always show keyboard"&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;References&lt;/h2&gt;
&lt;h3&gt;Weblinks&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Instructions for an older version of kde &lt;a href="https://ubuntuforums.org/showthread.php?t=1384425"&gt;https://ubuntuforums.org/showthread.php?t=1384425&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;</description><category>accelerators</category><category>kde</category><category>keyboard</category><category>productivity</category><guid>https://bgstack15.ddns.net/blog/posts/2017/05/01/kde-always-show-keyboard-underscores/</guid><pubDate>Mon, 01 May 2017 12:54:05 GMT</pubDate></item></channel></rss>