Not sure what happened here.... O.O
This commit is contained in:
parent
34ab43b8f9
commit
0dbc3ead0e
272 changed files with 4767 additions and 12217 deletions
|
|
@ -1,25 +0,0 @@
|
|||
<p>Brandon and Eric are joined by Greg Myers, a Support Engineer at GitLab. In this interivew, our hosts discuss what it means to be an application for the entire DevOps pipeline and what its like to work for a company that believes EVERYTHING should be open source.</p>
|
||||
|
||||
<p><a href="https://destinationlinux.network" rel="nofollow">Destination Linux Network</a><br>
|
||||
<a href="https://bitwarden.com/dln" rel="nofollow">Sponsor: Bitwarden</a><br>
|
||||
<a href="https://sudo.show" rel="nofollow">Sudo Show Website</a></p>
|
||||
|
||||
<p><a href="https://sudo.show/shirt" rel="nofollow">Sudo Show Merch!</a></p>
|
||||
|
||||
<p>Contact Us:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://sudo.show/discuss" rel="nofollow">DLN Discourse</a></li>
|
||||
<li>Matrix: +sudoshow:matrix.org</li>
|
||||
</ul>
|
||||
|
||||
<p><a href="https://abbout.gitlab.com" rel="nofollow">GitLab Homepage</a><br>
|
||||
<a href="https://about.gitlab.com/jobs/" rel="nofollow">GitLab Careers</a></p>
|
||||
|
||||
<p>As of 2020-09-17, GitLab employs 1,305 people in 67 countries</p>
|
||||
|
||||
<p><a href="https://about.gitlab.com/company/history/" rel="nofollow">GitLab's History</a><br>
|
||||
<a href="https://about.gitlab.com/blog/2020/09/08/gnome-follow-up/" rel="nofollow">Article - Gnome: Two Years After the Move to GitLab</a></p>
|
||||
|
||||
<p><a href="https://gitlab.com/greg/" rel="nofollow">Greg Myers - GitLab</a></p><p>Special Guest: Greg Myers.</p><p>Sponsored By:</p><ul><li><a href="https://bitwarden.com/dln" rel="nofollow">Bitwarden</a></li></ul><p><a href="https://www.patreon.com/sudoshow" rel="payment">Support Sudo Show</a></p>
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
<p class="text">When you read the Bible stories, you're constantly caught in "I didn't see that coming" moments. Abraham is 75 years old when God calls him to start a new nation. Seventy-five is not the typical age to begin great adventures, much less become a parent for the first time. Moses was working for his father-in-law and any inklings of his leadership abilities had been swallowed up by the mundane work of tending herds of sheep. No one saw Moses becoming one of the greatest leaders in the history of the world. Thousands of years later, we still quote his writings to settle our most complex legal disputes.</p>
|
||||
<p class="text">We didn't see that one coming.</p>
|
||||
<p class="text">We didn't see David becoming the greatest king of Israel. When Samuel traveled to anoint David as the future king of Israel, the prophet had to ask Jesse, David's father, twice if all of Jesse's sons were standing in front of the prophet. Only then did Jesse remember David. Hardly a rousing endorsement for a future leader of the nation. His own father forgot him!</p>
|
||||
<p class="text">We didn't see Peter becoming the leader of the disciples, much less the early church. Yet, Jesus saw something in him no one else did. The Apostle Paul was a surprise to everyone. Remember, early in his ministry, the Apostle Paul was hated by everyone. He wasn't trusted by the church who still feared him as the determined persecutor of the Way. The religious leaders who supported his intolerant mission felt Paul had betrayed them. Who but God would have thought Paul would be writing letters the church would be reading and studying today?</p>
|
||||
<p class="text">If you and I were going to choose a nation to influence the world, we wouldn't have chosen Israel. There were more impressive nations all over the world. God chose ...</p><p class="more"><a href="https://www.christianitytoday.com/scot-mcknight/2021/december/sneaky-christmas.html">Continue reading</a>...</p>
|
||||
<p><br /><a href="https://rss.beaconads.com/click.php?z=1289806&k=c779018782158d93282944b4f7dd4d03&a=191476&c=12150007" target="_blank"><img src="https://rss.beaconads.com/img.php?z=1289806&k=c779018782158d93282944b4f7dd4d03&a=191476&c=12150007" border="0" alt="" /></a></p>
|
||||
|
||||
5
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
<p>Nacho Barrientos has an interesting video in which he explains <a href="https://www.youtube.com/watch?v=wbG-a8DIIuY">how to run an eshell process in the background</a>. Barrientos illustrates this with the <code>sleep</code> command. Normally, if you enter</p>
|
||||
<div class="org-src-container">
|
||||
<pre class="src src-shell">sleep 4
|
||||
</pre>
|
||||
</div>
|
||||
<p>in Eshell, Emacs will hang until <code>sleep</code> completes in 4 seconds. Barrientos’ idea is to use the Emacs <code>compile</code> mechanism to run the command in the background. The output is redirected to the <code>*compile*</code> buffer and the Eshell prompt returns immediately.</p>
|
||||
<p>That’s a nice way of starting a long running process from Eshell and being able to continue working in Emacs. He also has a way of burying the <code>*compile*</code> buffer and getting a message when the process completes.</p>
|
||||
<p>There’s not a lot of code needed to implement this. You can see the relevant function in <a href="https://github.com/nbarrientos/dotfiles/blob/c79ef0f9908844346a8506129dedbb94f3b6b678/.emacs.d/init.el#L767">Barrientos’ init.el</a>. If you use Eshell regularly and sometimes want to invoke long-running processes, it’s worth taking a look at this video. The run time is only 4 minutes, 21 seconds so it should be easy to fit it in</p>
|
||||
|
|
@ -1,49 +0,0 @@
|
|||
<p>The more I move to VC<sup id="fnref:1"><a class="footnote" href="https://www.manueluberti.eu/feed#fn:1" rel="footnote">1</a></sup>, the more I end up relying on <kbd>M-!</kbd>
|
||||
(<code class="language-plaintext highlighter-rouge">shell-command</code>). Admittedly, this is a tool I’ve hardly ever used before, but
|
||||
since VC lacks many features covered by Magit, sometimes I need to interact with
|
||||
the power of Git straight from the command line.</p>
|
||||
|
||||
<p>One of the best things about Magit is that I don’t have to remember the many Git
|
||||
options to use it every day. Through transient menus, Magit makes Git a matter
|
||||
of few key strokes. On the other hand, from time to time I find myself on remote
|
||||
machines where Magit is not available, so it does not hurt to have a better
|
||||
understanding of the basic Git operations at my disposal.</p>
|
||||
|
||||
<p>However, typing them all out every single time is not the kind of pleasant
|
||||
activity a lazy Emacs user enjoys. Juri Linkov shared this little trick on
|
||||
<code class="language-plaintext highlighter-rouge">emacs-devel</code><sup id="fnref:2"><a class="footnote" href="https://www.manueluberti.eu/feed#fn:2" rel="footnote">2</a></sup>:</p>
|
||||
|
||||
<div class="language-emacs-lisp highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">(</span><span class="nb">defun</span> <span class="nv">mu-minibuffer-complete-history</span> <span class="p">()</span>
|
||||
<span class="s">"Complete minibuffer history."</span>
|
||||
<span class="p">(</span><span class="nv">interactive</span><span class="p">)</span>
|
||||
<span class="p">(</span><span class="nv">completion-in-region</span> <span class="p">(</span><span class="nv">minibuffer--completion-prompt-end</span><span class="p">)</span> <span class="p">(</span><span class="nv">point-max</span><span class="p">)</span>
|
||||
<span class="p">(</span><span class="nb">symbol-value</span> <span class="nv">minibuffer-history-variable</span><span class="p">)</span>
|
||||
<span class="no">nil</span><span class="p">))</span>
|
||||
</code></pre></div></div>
|
||||
|
||||
<p>Juri also suggested to bind it to <kbd>C-TAB</kbd> in <code class="language-plaintext highlighter-rouge">minibuffer-local-map</code>
|
||||
which, coincidentally, is the same key binding I have to manually complete with
|
||||
Company outside of the minibuffer.</p>
|
||||
|
||||
<p>What Juri’s code does is popping up a <code class="language-plaintext highlighter-rouge">*Completions*</code> buffer with the history of
|
||||
the commands used in the minibuffer. I only use it with <code class="language-plaintext highlighter-rouge">shell-command</code>, but try
|
||||
it with <kbd>C-x C-f</kbd> for fun.</p>
|
||||
|
||||
<p>I leave it as a small exercise for the reader to understand how to switch from
|
||||
the minibuffer to the <code class="language-plaintext highlighter-rouge">*Completions*</code> buffer and vice versa. Tip: <kbd>C-h
|
||||
m</kbd> is your friend.</p>
|
||||
|
||||
<h3 id="notes">Notes</h3>
|
||||
|
||||
<div class="footnotes">
|
||||
<ol>
|
||||
<li id="fn:1">
|
||||
<p>See <a href="https://www.manueluberti.eu/emacs/2021/11/27/vc/">A job for VC</a> and
|
||||
<a href="https://www.manueluberti.eu/emacs/2021/12/05/vc-rebasing/">Rebasing with
|
||||
VC</a>. <a class="reversefootnote" href="https://www.manueluberti.eu/feed#fnref:1">↩</a></p>
|
||||
</li>
|
||||
<li id="fn:2">
|
||||
<p>See <a href="https://lists.gnu.org/archive/html/emacs-devel/2021-12/msg00802.html" target="_blank">History completion</a>. <a class="reversefootnote" href="https://www.manueluberti.eu/feed#fnref:2">↩</a></p>
|
||||
</li>
|
||||
</ol>
|
||||
</div>
|
||||
Loading…
Add table
Add a link
Reference in a new issue