shockrah/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'posting'

Browse Source
This commit is contained in:
AlejandroS 2018-07-22 01:01:10 -07:00
commit 276bd7e762
2 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
markdown/post/bash-1.md
View File

@ -20,10 +20,12 @@ Just use that alias in your bashrc and you're good to go.
## Rambled guess time ## Rambled guess time
My guess on how the alias is that bash doesn't try to figure out that you want to use `vim` since you've only typed a single `v` in this case; therefore tab-completion would go unnoticed?\ My guess on how the alias is that bash doesn't try to figure out that you want to use `vim` since you've only typed a single `v` in this case; therefore tab-completion would go unnoticed?\
Say you had a directory with files: \ Say you had a directory with files:
> first \ > first \
> second \ > second \
> third \ > third
That would mean if your shell contained `asdf`. You could go to the first character start typing any one of those file names and have bash guess the filename to autocomplete, since it only look backwards for completion. That would mean if your shell contained `asdf`. You could go to the first character start typing any one of those file names and have bash guess the filename to autocomplete, since it only look backwards for completion.
### Where be the posts ### Where be the posts

12
post/bash-1.html
View File

@ -23,11 +23,13 @@ I'm not really sure why that works, but I'm just glad it does. If you've ever ne
Just use that alias in your bashrc and you're good to go.</p> Just use that alias in your bashrc and you're good to go.</p>
<h2 id="rambled-guess-time">Rambled guess time</h2> <h2 id="rambled-guess-time">Rambled guess time</h2>
<p>My guess on how the alias is that bash doesn't try to figure out that you want to use <code>vim</code> since you've only typed a single <code>v</code> in this case; therefore tab-completion would go unnoticed?<br /> <p>My guess on how the alias is that bash doesn't try to figure out that you want to use <code>vim</code> since you've only typed a single <code>v</code> in this case; therefore tab-completion would go unnoticed?<br />
Say you had a directory with files:<br /> Say you had a directory with files:</p>
&gt; first<br /> <blockquote>
&gt; second<br /> <p>first<br />
&gt; third<br /> second<br />
That would mean if your shell contained <code>asdf</code>. You could go to the first character start typing any one of those file names and have bash guess the filename to autocomplete, since it only look backwards for completion.</p> third</p>
</blockquote>
<p>That would mean if your shell contained <code>asdf</code>. You could go to the first character start typing any one of those file names and have bash guess the filename to autocomplete, since it only look backwards for completion.</p>
<h3 id="where-be-the-posts">Where be the posts</h3> <h3 id="where-be-the-posts">Where be the posts</h3>
<p>Lately I've been working on a translator for html. Similar to how pandoc turns markdown into valid html which lead me onto another issue that I've also taken on since I've not much to do.<br /> <p>Lately I've been working on a translator for html. Similar to how pandoc turns markdown into valid html which lead me onto another issue that I've also taken on since I've not much to do.<br />
Specifically it's looking into <em>GCC</em>'s seemingly random behavior with switch cases. Essentially <em>GCC</em> will sometimes create a decision tree for a slightly faster search time through the cases, sometimes create the equivalent of linearly executable code(<em>like a bunch of if/else's</em>), and if given the opportunity &quot;<em>guess</em>&quot; the correct case on the first check... For that reason I've started diving into it to try and determine what the fug is going with this compiler and what flags, if any can be used to create some more predictable output. Hopefully the research crops up something interesting to think but who knows 🤷.</p> Specifically it's looking into <em>GCC</em>'s seemingly random behavior with switch cases. Essentially <em>GCC</em> will sometimes create a decision tree for a slightly faster search time through the cases, sometimes create the equivalent of linearly executable code(<em>like a bunch of if/else's</em>), and if given the opportunity &quot;<em>guess</em>&quot; the correct case on the first check... For that reason I've started diving into it to try and determine what the fug is going with this compiler and what flags, if any can be used to create some more predictable output. Hopefully the research crops up something interesting to think but who knows 🤷.</p>