mirror of
https://github.com/balkian/balkian.github.com.git
synced 2025-02-22 17:55:07 +00:00
1602 lines
142 KiB
XML
1602 lines
142 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>J. Fernando Sánchez</title><link>https://balkian.com/</link><description>Recent content on J. Fernando Sánchez</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 17 Feb 2025 23:02:47 +0100</lastBuildDate><atom:link href="https://balkian.com/index.xml" rel="self" type="application/rss+xml"/><item><title>uv - One rust tool to rule all pythons</title><link>https://balkian.com/p/uv-one-rust-tool-to-rule-all-pythons/</link><pubDate>Mon, 17 Feb 2025 23:02:47 +0100</pubDate><guid>https://balkian.com/p/uv-one-rust-tool-to-rule-all-pythons/</guid><description><img src="https://balkian.com/img/uv.png" alt="Featured image of post uv - One rust tool to rule all pythons" /><p>Long story short: I&rsquo;m now using <a class="link" href="https://github.com/astral-sh/uv" target="_blank" rel="noopener"
|
||
>uv</a>, and so should you.
|
||
It is a great replacement for pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.</p>
|
||
<h2 id="context">Context
|
||
</h2><p>For years, my strategy to manage python projects has been a mix of a custom <code>setup.py</code>, several hand-crafted <code>requirements.txt</code> files (through <code>pip freeze</code>), a custom virtualenv per project, and multiple tools to upload to PyPI.
|
||
Although this works, this setup has many drawbacks:</p>
|
||
<ul>
|
||
<li>It requires user intervention (creating a venv, sourcing it, handling new deps). This isn&rsquo;t ideal if you want new (probably inexperienced) users to use your projects.</li>
|
||
<li>On a similar note, the whole process needs to be well documented if you want other users to contribute or maintain the code.</li>
|
||
<li>Pinning dependency versions is finicky, and I&rsquo;ve run into problems beause of that.</li>
|
||
<li>Creating a new project involves a template, or copying files from an older project.</li>
|
||
</ul>
|
||
<p>Of course, this is nothing new.
|
||
There is a whole site dedicated to <a class="link" href="https://packaging.python.org/en/latest/" target="_blank" rel="noopener"
|
||
>packaging your Python project</a>.
|
||
A plethora of different projects have come and go, with varying degrees of success.</p>
|
||
<h2 id="alternatives-poetry">Alternatives (poetry)
|
||
</h2><p>About a year before trying <code>uv</code>, I tried to catch up with the ecosystem and get to know the <code>blessed new way</code>.
|
||
However, the task proved to be a little more difficult, as the landscape is filled with a myriad of alternatives, each with their own set of drawbacks and detractors.
|
||
Packaging has historically been a weak spot, in ironical contradiction to the Zen of Python&rsquo;s &ldquo;There should be one&ndash; and preferably only one &ndash;obvious way to do it&rdquo;,</p>
|
||
<p>I eventually settled on <a class="link" href="https://python-poetry.org/" target="_blank" rel="noopener"
|
||
>poetry</a>.
|
||
Mostly because it seemed like the most popular alternative.</p>
|
||
<p>There are many things I liked about it.
|
||
First of all, having a convention for dependencies (<code>pyproject.toml</code>) and a tool that properly handles them was nice.
|
||
It also removed the need to remember specific incantations to build and publish my Python projects.
|
||
Lastly, I mixed it <code>poetry2nix</code> to create reproducible python environments using nix.
|
||
This makes for a very powerful experience.</p>
|
||
<p>However, there were multiple hiccups.
|
||
First of all, it took me some time to figure out which specific fields to use (each tool can define ad-hoc properties in a the <code>pyproject.toml</code> file), and some of them seemed redundant with the more generic ones.
|
||
Full disclosure, this specific point might be a mistake on my side, and I do not remember the details.
|
||
The second one is speed.
|
||
(Re-)creating an environment took a non-negligible amount of time.</p>
|
||
<h2 id="enter-light-uv">Enter <del>light</del> <code>uv</code>
|
||
</h2><p>According to its repository, <code>uv </code>can replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.
|
||
Not only that, but it also claims to do that 10-100 times faster than pip.
|
||
I must admit that it being written in rust was a another selling point for me, as I&rsquo;m looking for excuses to collaborate in a decently-sized rust projejct.</p>
|
||
<p>Installing it is dead simple: simply download the binary (e.g., with curl) or run <code>pip install uv</code>.
|
||
You won&rsquo;t need much more: <code>uv</code> seems to just do the right thing out of the box.
|
||
And it does it really, really fast.
|
||
The rest of the time it gets out of the way.</p>
|
||
<p>My only gripe so far is that I don&rsquo;t seem to find a built-in command to drop into a shell, but that is nothing that <code>uv run $SHELL</code> cannot fix.</p>
|
||
<h2 id="common-operations">Common operations
|
||
</h2><h3 id="initialize-a-repository">Initialize a repository
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">uv init
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h3 id="adding-dependencies">Adding dependencies
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">uv add senpy
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h3 id="running-commands-inside-the-environment">Running commands inside the environment
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">uv run &lt;COMMAND&gt;
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"># e.g., run a shell using your python version and dependencies
|
||
</span></span><span class="line"><span class="cl">uv run $SHELL
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h3 id="dependency-tree">Dependency tree
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span><span class="lnt">14
|
||
</span><span class="lnt">15
|
||
</span><span class="lnt">16
|
||
</span><span class="lnt">17
|
||
</span><span class="lnt">18
|
||
</span><span class="lnt">19
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">uv shell
|
||
</span></span><span class="line"><span class="cl">Resolved 44 packages in 1ms
|
||
</span></span><span class="line"><span class="cl">my-project v0.1.0
|
||
</span></span><span class="line"><span class="cl">├── fastapi[standard] v0.115.8
|
||
</span></span><span class="line"><span class="cl">│ ├── pydantic v2.10.6
|
||
</span></span><span class="line"><span class="cl">│ │ ├── annotated-types v0.7.0
|
||
</span></span><span class="line"><span class="cl">│ │ ├── pydantic-core v2.27.2
|
||
</span></span><span class="line"><span class="cl">│ │ │ └── typing-extensions v4.12.2
|
||
</span></span><span class="line"><span class="cl">│ │ └── typing-extensions v4.12.2
|
||
</span></span><span class="line"><span class="cl">│ ├── starlette v0.45.3
|
||
</span></span><span class="line"><span class="cl">│ │ └── anyio v4.8.0
|
||
</span></span><span class="line"><span class="cl">│ │ ├── exceptiongroup v1.2.2
|
||
</span></span><span class="line"><span class="cl">│ │ ├── idna v3.10
|
||
</span></span><span class="line"><span class="cl">│ │ ├── sniffio v1.3.1
|
||
</span></span><span class="line"><span class="cl">│ │ └── typing-extensions v4.12.2
|
||
</span></span><span class="line"><span class="cl">│ ├── typing-extensions v4.12.2
|
||
</span></span><span class="line"><span class="cl">│ ├── email-validator v2.2.0 (extra: standard)
|
||
</span></span><span class="line"><span class="cl">│ │ ├── dnspython v2.7.0
|
||
</span></span><span class="line"><span class="cl">...
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Nix Recipe for Python Projects</title><link>https://balkian.com/p/nix-recipe-for-python-projects/</link><pubDate>Mon, 13 Nov 2023 18:21:46 +0100</pubDate><guid>https://balkian.com/p/nix-recipe-for-python-projects/</guid><description><p>This is a quick and easy recipe to add a <code>default.nix</code> to any Python project with a <code>requirements.txt</code> file:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span><span class="lnt">14
|
||
</span><span class="lnt">15
|
||
</span><span class="lnt">16
|
||
</span><span class="lnt">17
|
||
</span><span class="lnt">18
|
||
</span><span class="lnt">19
|
||
</span><span class="lnt">20
|
||
</span><span class="lnt">21
|
||
</span><span class="lnt">22
|
||
</span><span class="lnt">23
|
||
</span><span class="lnt">24
|
||
</span><span class="lnt">25
|
||
</span><span class="lnt">26
|
||
</span><span class="lnt">27
|
||
</span><span class="lnt">28
|
||
</span><span class="lnt">29
|
||
</span><span class="lnt">30
|
||
</span><span class="lnt">31
|
||
</span><span class="lnt">32
|
||
</span><span class="lnt">33
|
||
</span><span class="lnt">34
|
||
</span><span class="lnt">35
|
||
</span><span class="lnt">36
|
||
</span><span class="lnt">37
|
||
</span><span class="lnt">38
|
||
</span><span class="lnt">39
|
||
</span><span class="lnt">40
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="k">with</span> <span class="kn">import</span> <span class="sr">&lt;nixpkgs&gt;</span> <span class="p">{</span> <span class="p">};</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">let</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">pythonPackages</span> <span class="o">=</span> <span class="n">python311Packages</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"><span class="k">in</span> <span class="n">pkgs</span><span class="o">.</span><span class="n">mkShell</span> <span class="k">rec</span> <span class="p">{</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">name</span> <span class="o">=</span> <span class="s2">&#34;impurePythonEnv&#34;</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">venvDir</span> <span class="o">=</span> <span class="s2">&#34;./.venv&#34;</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">buildInputs</span> <span class="o">=</span> <span class="p">[</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># A python interpreter including the &#39;venv&#39; module is required to bootstrap</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># the environment.</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">pythonPackages</span><span class="o">.</span><span class="n">python</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># This execute some shell code to initialize a venv in $venvDir before</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># dropping into the shell</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">pythonPackages</span><span class="o">.</span><span class="n">venvShellHook</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># Those are dependencies that we would like to use from nixpkgs, which will</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># add them to PYTHONPATH and thus make them accessible from within the venv.</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">pythonPackages</span><span class="o">.</span><span class="n">numpy</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">pythonPackages</span><span class="o">.</span><span class="n">requests</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># In this particular example, in order to compile any binary extensions they may</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># require, the python modules listed in the hypothetical requirements.txt need</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># the following packages to be installed locally:</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">taglib</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">openssl</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">git</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">libxml2</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">libxslt</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">libzip</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">zlib</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">];</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># Now we can execute any commands within the virtual environment.</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1"># This is optional and can be left out to run pip manually.</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">postShellHook</span> <span class="o">=</span> <span class="s1">&#39;&#39;
|
||
</span></span></span><span class="line"><span class="cl"><span class="s1"> pip install -r requirements.txt
|
||
</span></span></span><span class="line"><span class="cl"><span class="s1"> &#39;&#39;</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">}</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Now, you will get a clean environment by running:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">nix-shell
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Kanata: advanced keyboard configuration</title><link>https://balkian.com/p/kanata-advanced-keyboard-configuration/</link><pubDate>Fri, 20 Jan 2023 18:11:00 +0000</pubDate><guid>https://balkian.com/p/kanata-advanced-keyboard-configuration/</guid><description><p><a class="link" href="https://github.com/jtroo/kanata/" target="_blank" rel="noopener"
|
||
>Kanata</a> is a software keyboard remapper that aims to improve keyboard comfort and usability with advanced customization.
|
||
Keyboard remappers are a good alternative to running a custom keyboard with QMK/ZMK, and have two main advantages: they work on any keyboard, and you can configure them to launch any command or program you want, not just key presses.
|
||
On the other hand, you need to configure them on every PC/OS you&rsquo;re using your keyboard with, and all the processing is done on software on top of the OS, so there may be glitches and performance issues.</p>
|
||
<p>The project was inspired by the more popular <a class="link" href="https://github.com/kmonad/kmonad" target="_blank" rel="noopener"
|
||
>KMonad</a>, and the author cites some of the <a class="link" href="https://github.com/jtroo/kanata/blob/main/docs/kmonad_comparison.md" target="_blank" rel="noopener"
|
||
>differences</a>.
|
||
Both projects use a very similar configuration format based on lisp.
|
||
The configuration consists of a set of general options, a base key configuration, a series of layers, and macros that can be used within those layers.
|
||
<a class="link" href="https://github.com/jtroo/kanata/blob/main/cfg_samples/kanata.kbd" target="_blank" rel="noopener"
|
||
>Here&rsquo;s a very complete config that serves as documentation</a>.</p>
|
||
<p>One big disadvantage of the lispy configuration is that you need to specify your hardware layout/all your keys, and repeat that every time you define a new layer.
|
||
The result visually maps to your keyboard, but can be very verbose/big if you need really few changes.</p>
|
||
<p><a class="link" href="https://github.com/rvaiya/keyd/" target="_blank" rel="noopener"
|
||
>Keyd</a> is another alternative with a more declarative configuration format, which might lend itself to smaller.</p>
|
||
<p>For now I&rsquo;m just trying it out, and getting a feel for using fewer keys before I build my own ZMK keyboard.
|
||
I particularly like the option of using mod-keys on the home row (e.g., having A work as a CTRL when held).
|
||
Mod-tap, tap-dancing and the like are very common techniques in sub-40% layouts, where there simply aren&rsquo;t enough keys for all the letters and symbols.
|
||
In a regular-sized keyboard, these techniques can also help you stay on the home row and type more comfortably.
|
||
At least, that&rsquo;s the idea.
|
||
We&rsquo;ll see if I like it enough to stick with it.</p>
|
||
<p>For now, here&rsquo;s my very simple config:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span><span class="lnt">14
|
||
</span><span class="lnt">15
|
||
</span><span class="lnt">16
|
||
</span><span class="lnt">17
|
||
</span><span class="lnt">18
|
||
</span><span class="lnt">19
|
||
</span><span class="lnt">20
|
||
</span><span class="lnt">21
|
||
</span><span class="lnt">22
|
||
</span><span class="lnt">23
|
||
</span><span class="lnt">24
|
||
</span><span class="lnt">25
|
||
</span><span class="lnt">26
|
||
</span><span class="lnt">27
|
||
</span><span class="lnt">28
|
||
</span><span class="lnt">29
|
||
</span><span class="lnt">30
|
||
</span><span class="lnt">31
|
||
</span><span class="lnt">32
|
||
</span><span class="lnt">33
|
||
</span><span class="lnt">34
|
||
</span><span class="lnt">35
|
||
</span><span class="lnt">36
|
||
</span><span class="lnt">37
|
||
</span><span class="lnt">38
|
||
</span><span class="lnt">39
|
||
</span><span class="lnt">40
|
||
</span><span class="lnt">41
|
||
</span><span class="lnt">42
|
||
</span><span class="lnt">43
|
||
</span><span class="lnt">44
|
||
</span><span class="lnt">45
|
||
</span><span class="lnt">46
|
||
</span><span class="lnt">47
|
||
</span><span class="lnt">48
|
||
</span><span class="lnt">49
|
||
</span><span class="lnt">50
|
||
</span><span class="lnt">51
|
||
</span><span class="lnt">52
|
||
</span><span class="lnt">53
|
||
</span><span class="lnt">54
|
||
</span><span class="lnt">55
|
||
</span><span class="lnt">56
|
||
</span><span class="lnt">57
|
||
</span><span class="lnt">58
|
||
</span><span class="lnt">59
|
||
</span><span class="lnt">60
|
||
</span><span class="lnt">61
|
||
</span><span class="lnt">62
|
||
</span><span class="lnt">63
|
||
</span><span class="lnt">64
|
||
</span><span class="lnt">65
|
||
</span><span class="lnt">66
|
||
</span><span class="lnt">67
|
||
</span><span class="lnt">68
|
||
</span><span class="lnt">69
|
||
</span><span class="lnt">70
|
||
</span><span class="lnt">71
|
||
</span><span class="lnt">72
|
||
</span><span class="lnt">73
|
||
</span><span class="lnt">74
|
||
</span><span class="lnt">75
|
||
</span><span class="lnt">76
|
||
</span><span class="lnt">77
|
||
</span><span class="lnt">78
|
||
</span><span class="lnt">79
|
||
</span><span class="lnt">80
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-lisp" data-lang="lisp"><span class="line"><span class="cl"><span class="p">(</span><span class="nv">defcfg</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1">;; Your keyboard device will likely differ from this.</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">linux-dev</span> <span class="nv">/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="c1">;; Windows doesn&#39;t need any input/output configuration entries; however, there</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1">;; must still be a defcfg entry. You can keep the linux-dev entry or delete</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1">;; it and leave it empty.</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">defsrc</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">grv</span> <span class="mi">1</span> <span class="mi">2</span> <span class="mi">3</span> <span class="mi">4</span> <span class="mi">5</span> <span class="mi">6</span> <span class="mi">7</span> <span class="mi">8</span> <span class="mi">9</span> <span class="mi">0</span> <span class="nf">-</span> <span class="nf">=</span> <span class="nv">bspc</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">tab</span> <span class="nv">q</span> <span class="nv">w</span> <span class="nv">e</span> <span class="nv">r</span> <span class="no">t</span> <span class="nv">y</span> <span class="nv">u</span> <span class="nv">i</span> <span class="nv">o</span> <span class="nv">p</span> <span class="nv">[</span> <span class="nv">]</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">caps</span> <span class="nv">a</span> <span class="nv">s</span> <span class="nv">d</span> <span class="nv">f</span> <span class="nv">g</span> <span class="nv">h</span> <span class="nv">j</span> <span class="nv">k</span> <span class="nv">l</span> <span class="c1">; &#39; ret</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lsft</span> <span class="nv">\ z</span> <span class="nv">x</span> <span class="nv">c</span> <span class="nv">v</span> <span class="nv">b</span> <span class="nv">n</span> <span class="nv">m</span> <span class="o">,</span> <span class="o">.</span> <span class="nf">/</span> <span class="nv">rsft</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lctl</span> <span class="nv">lmet</span> <span class="nv">lalt</span> <span class="nv">spc</span> <span class="nv">ralt</span> <span class="nv">rmet</span> <span class="nv">rctl</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">deflayer</span> <span class="nv">qwerty</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">grv</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">@warrows</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lctrl</span> <span class="nv">@alctrl</span> <span class="nv">@slsft</span> <span class="nv">@dlalt</span> <span class="nv">@flmet</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">@jrmet</span> <span class="nv">@kralt</span> <span class="nv">@lrsft</span> <span class="nv">@</span><span class="c1">;rctrl _ _</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">@smartspace</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">deflayer</span> <span class="nv">arrows</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">@flmet</span> <span class="nv">_</span> <span class="nv">left</span> <span class="nv">down</span> <span class="nv">up</span> <span class="nv">rght</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">@smartspace</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">deflayer</span> <span class="nv">colemak</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">grv</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">tab</span> <span class="nv">q</span> <span class="nv">w</span> <span class="nv">f</span> <span class="nv">p</span> <span class="nv">b</span> <span class="nv">j</span> <span class="nv">l</span> <span class="nv">u</span> <span class="nv">y</span> <span class="c1">; [ ] </span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lctrl</span> <span class="nv">@alctrl</span> <span class="nv">@rlsft</span> <span class="nv">@slalt</span> <span class="nv">@tlmet</span> <span class="nv">g</span> <span class="nv">m</span> <span class="nv">@nrmet</span> <span class="nv">@eralt</span> <span class="nv">@irsft</span> <span class="nv">@orctrl</span> <span class="o">&#39;</span> <span class="nv">ret</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lsft</span> <span class="nv">XX</span> <span class="nv">z</span> <span class="nv">x</span> <span class="nv">c</span> <span class="nv">d</span> <span class="nv">v</span> <span class="nv">k</span> <span class="nv">h</span> <span class="o">,</span> <span class="o">.</span> <span class="nf">/</span> <span class="nv">rsft</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">@smartspace</span> <span class="nv">XX</span> <span class="nv">XX</span> <span class="nv">XX</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">deflayer</span> <span class="nv">magic</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">@clmk</span> <span class="nv">@qwerty</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">tab</span> <span class="nv">A-tab</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">bspc</span> <span class="nv">esc</span> <span class="nv">_</span> <span class="nv">ret</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span> <span class="nv">_</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="p">(</span><span class="nv">defalias</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">warrows</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">w</span> <span class="p">(</span><span class="nv">layer-toggle</span> <span class="nv">arrows</span><span class="p">))</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">alctrl</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">a</span> <span class="nv">lctrl</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">slsft</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">s</span> <span class="nv">lsft</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">dlalt</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">d</span> <span class="nv">lalt</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">flmet</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">f</span> <span class="nv">lmet</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">jrmet</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">j</span> <span class="nv">rmet</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">kralt</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">k</span> <span class="nv">ralt</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">lrsft</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">l</span> <span class="nv">rsft</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="c1">;rctrl (tap-hold 200 200 ; rctrl)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">rlsft</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">r</span> <span class="nv">lsft</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">slalt</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">s</span> <span class="nv">lalt</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">tlmet</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="no">t</span> <span class="nv">lmet</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">nrmet</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">n</span> <span class="nv">rmet</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">eralt</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">e</span> <span class="nv">ralt</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">irsft</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">i</span> <span class="nv">rsft</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">orctrl</span> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">200</span> <span class="mi">200</span> <span class="nv">o</span> <span class="nv">rctrl</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">clmk</span> <span class="p">(</span><span class="nv">layer-switch</span> <span class="nv">colemak</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">qwerty</span> <span class="p">(</span><span class="nv">layer-switch</span> <span class="nv">qwerty</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">smartspace</span> <span class="p">(</span><span class="nv">tap-dance</span> <span class="mi">200</span> <span class="p">(</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">300</span> <span class="mi">300</span> <span class="nv">spc</span> <span class="p">(</span><span class="nv">layer-toggle</span> <span class="nv">magic</span><span class="p">))</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">(</span><span class="nv">tap-hold</span> <span class="mi">300</span> <span class="mi">300</span> <span class="p">(</span><span class="nv">one-shot</span> <span class="mi">300</span> <span class="nv">lalt</span><span class="p">)</span> <span class="nv">spc</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nv">a</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">))</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="p">)</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Archives</title><link>https://balkian.com/archives/</link><pubDate>Sun, 06 Mar 2022 00:00:00 +0000</pubDate><guid>https://balkian.com/archives/</guid><description/></item><item><title>Logitech MB850 combi in linux</title><link>https://balkian.com/p/logitech-mb850-combi-in-linux/</link><pubDate>Sat, 30 Oct 2021 00:00:01 +0000</pubDate><guid>https://balkian.com/p/logitech-mb850-combi-in-linux/</guid><description><p>As a follow-up to my last post, I&rsquo;ve decided to also configure my mk850 combo (k850 + m720 triathlon).</p>
|
||
<p>Some notes:</p>
|
||
<ul>
|
||
<li>The keyboard is usually connected to this PC through bluetooth. Since this is a change I usually do in the system for every keyboard, I added a rule for any bus (usb, bluetooth, etc)</li>
|
||
<li>The mouse has an additional button that registers as a keyboard. Every press maps to three key events. I&rsquo;ve disabled two of them and mapped the action to F19, in case I want to use it in my DE/WM.</li>
|
||
</ul>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span><span class="lnt">6
|
||
</span><span class="lnt">7
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="na">evdev:input:* </span>
|
||
</span></span><span class="line"><span class="cl"> <span class="na">KEYBOARD_KEY_70039</span><span class="o">=</span><span class="s">leftctrl # bind capslock to w </span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="na">evdev:input:b0005v046DpB015*</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="na">KEYBOARD_KEY_700e0</span><span class="o">=</span><span class="s">f19
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_700e2=unknown
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_7002b=unknown</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>After that, simply run:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl"> sudo udevadm hwdb --update &amp;&amp; sudo udevadm trigger
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Make sure the settings have been applied by running <code>evemu-describe</code>:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"> sudo /sbin/evemu-describe /dev/input/event&lt;id of your device&gt; <span class="p">|</span> grep KEY_
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Logitech MX Keys for Mac on Linux</title><link>https://balkian.com/p/logitech-mx-keys-for-mac-on-linux/</link><pubDate>Fri, 29 Oct 2021 00:00:01 +0000</pubDate><guid>https://balkian.com/p/logitech-mx-keys-for-mac-on-linux/</guid><description><p>I recently got Logitech MX Keys for Mac keyboard at work.
|
||
The German version, to be more precise.
|
||
This version was three times cheaper than the Windows equivalent with either US or ES layout.
|
||
Since I touch type anyway, I thought it was a bargain.</p>
|
||
<p>As soon as I plugged it in, I realized there were some glaring issues with the keyboard.
|
||
First of all, the Meta/Super and Alt keys are reversed in this keyboard.
|
||
In the normal/full version of this keyboard, Logitech gives an option to choose between Mac, Windows and iOS host, and that changes the behavior of the keys.
|
||
In this version, tho, only iOS and Mac are available.</p>
|
||
<p>Besides that, there&rsquo;s the issue of the grave (tilde) and angle keys switched as well.</p>
|
||
<p>Switching these keys around would be very easy with Xorg, but Wayland once again complicates things&hellip;</p>
|
||
<p>These issues almost made me return the keyboard.
|
||
Luckily, tho, there is another option: configuring the keys one level lower than wayland (and X11), through hwdb.</p>
|
||
<p>Long story short, this will configure any Logitech keyboard with the same product id (0x4092) to use a saner configuration:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="c1">#File: /etc/udev/hwdb.d/90-logitech-keyboard.hwdb</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="na">evdev:input:b0003v046Dp4092*</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="na">KEYBOARD_KEY_700e2</span><span class="o">=</span><span class="s">leftmeta
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_700e3=leftalt
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_70039=leftctrl
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_70064=102nd
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_70035=grave
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_700e7=rightalt
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_700e6=rightmeta
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> KEYBOARD_KEY_7006d=compose</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>After that, simply run:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl"> sudo udevadm hwdb --update &amp;&amp; sudo udevadm trigger
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Linux on the Microsoft Surface Go</title><link>https://balkian.com/p/linux-on-the-microsoft-surface-go/</link><pubDate>Sat, 01 Jun 2019 00:00:01 +0000</pubDate><guid>https://balkian.com/p/linux-on-the-microsoft-surface-go/</guid><description><p>Believe it or not, Surface tablets have pretty good linux support, except for the webcams in newer models.
|
||
These are some useful notes to get Ubuntu installed in your surface go, as of Summer 2019.</p>
|
||
<h2 id="installing-the-kernel">Installing the kernel
|
||
</h2><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">git clone --depth <span class="m">1</span> https://github.com/jakeday/linux-surface.git ~/linux-surface
|
||
</span></span><span class="line"><span class="cl">cp -a ~/linux-surface /media/&lt;your usb&gt;
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">cp -a /media/&lt;your usb&gt;/linux-surface ~/
|
||
</span></span><span class="line"><span class="cl"><span class="nb">cd</span> ~/linux-surface/
|
||
</span></span><span class="line"><span class="cl">sudo sh setup.sh
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h2 id="booting-ubuntu-first">Booting ubuntu first
|
||
</h2><p>Switch out of Windows S mode.</p>
|
||
<p>Boot into the &ldquo;Command Prompt&rdquo;.</p>
|
||
<p>From Windows go to &ldquo;change advanced startup options&rdquo; and select &ldquo;restart now&rdquo;.</p>
|
||
<p>When it reboots, choose the &ldquo;Troubleshoot&rdquo; option, then choose the &ldquo;Advanced options&rdquo; option, and finally choose the &ldquo;Command Prompt&rdquo; option.</p>
|
||
<p>After the device reboots, login to the command prompt and then you should see a terminal with X:\windows\system32&gt;</p>
|
||
<p>At the prompt, check your UEFI entries:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">bcdedit /enum firmware
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Copy UEFI entry of &ldquo;Windows Boot Manager&rdquo; to create a new entry for Ubuntu: bcdedit /copy {bootmgr} /d &ldquo;Ubuntu&rdquo;</p>
|
||
<p>Copy the printed GUID number including the braces {} using Ctrl+C</p>
|
||
<p>Set file path for the new Ubuntu entry. Replace {guid} with the returned GUID of the previous command (Ctrl+V). bcdedit /set {guid} path \EFI\ubuntu\grubx64.efi</p>
|
||
<p>Set Ubuntu as the first/ entry in the boot sequence. Again replace {guid} with the returned GUID of the copy command.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">bcdedit /set <span class="o">{</span>fwbootmgr<span class="o">}</span> displayorder <span class="o">{</span>guid<span class="o">}</span> /addfirst
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Check your UEFI entries again: bcdedit /enum firmware You should see something like this:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl">Firmware Boot Manager
|
||
</span></span><span class="line"><span class="cl">---------------------
|
||
</span></span><span class="line"><span class="cl">identifier <span class="o">{</span>fwbootmgr<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl">displayorder <span class="o">{</span>3510232e-f8eb-e811-95ce-9ecab3f9d1c4<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="o">{</span>bootmgr<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="o">{</span>2148799b-f8eb-e811-95ce-9ecab3f9d1c4<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="o">{</span>312e8a67-c2f6-e811-95ce-3c1ab3f9d1de<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="o">{</span>312e8a68-c2f6-e811-95ce-3c1ab3f9d1de<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl">timeout <span class="m">0</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Make sure the GUID you copied is the first one listed in displayorder. Then type exit, turn off the PC and turn it back on. After this my surface go is automatically booting to the grub bootloader which lets me choose between Windows and Ubuntu but defaults to Ubuntu after ten seconds.</p></description></item><item><title>Controlling Zigbee devices with MQTT</title><link>https://balkian.com/p/controlling-zigbee-devices-with-mqtt/</link><pubDate>Sun, 06 Jan 2019 10:00:00 +0000</pubDate><guid>https://balkian.com/p/controlling-zigbee-devices-with-mqtt/</guid><description><p>This is a short tutorial on connecting a zigbee device (an Aqara cube)
|
||
to an MQTT server, so you can control your zigbee devices from the
|
||
network.</p>
|
||
<p>If you&rsquo;re anything like me, you&rsquo;re probably a sucker for IoT devices.
|
||
For a long time, I&rsquo;ve been using WiFi-enabled lights, and Amazon dash
|
||
buttons to control them. To keep these (cheap Chinese) internet enabled
|
||
devices away from your network and their respective cloud services,
|
||
you&rsquo;ll probably want to set up a dedicated network in your router (more
|
||
on this on a future post, maybe). Another disadvantage of WiFi devices
|
||
is that they&rsquo;re relatively power hungry.</p>
|
||
<p>A popular alternative is using ZigBee for communication. It is a
|
||
dedicated protocol similar to bluetooth (BLE), with lower power
|
||
requirements and bitrate.</p>
|
||
<p>Take the (super cute) aqara cube as an example. It is a small cube that
|
||
detects rotation on all of its axes, and tapping events. Here&rsquo;s a
|
||
video:</p>
|
||
<div class="video-wrapper">
|
||
<iframe loading="lazy"
|
||
src="https://www.youtube.com/embed/5YtqG1wEnng"
|
||
allowfullscreen
|
||
title="YouTube Video"
|
||
>
|
||
</iframe>
|
||
</div>
|
||
<p>To connect to zigbee devices you will need a zigbee enabled gateway
|
||
(a.k.a. hub), which connects to your WiFi network and your zigbee
|
||
devices. Once again, this means adding an internet-enabled device to
|
||
your home, and probably a couple of cloud services.</p>
|
||
<p>As an alternative, you can set up your own zigbee gateway, and control
|
||
it to your home automation platform of choice (e.g. home assistant). We
|
||
will cover how to set up a zigbee2mqtt gateway that is also connected to
|
||
an MQTT server, so you can use MQTT to control your devices and get
|
||
notifications.</p>
|
||
<p>What you need:</p>
|
||
<ul>
|
||
<li><a class="link" href="https://www.aliexpress.com/item/Original-Xiaomi-Mi-Aqara-Cube-Smart-Home-Controller-6-Action-Operation-Fr-Home-Device-Zigbee-Version/32892947622.html?spm=a2g0s.9042311.0.0.3da24c4dXV8sBI" target="_blank" rel="noopener"
|
||
>Aqara
|
||
cube</a>.</li>
|
||
<li><a class="link" href="https://www.aliexpress.com/item/Wireless-Zigbee-CC2531-CC2540-Zigbee-Sniffer-Bluetooth-BLE-4-0-Dongle-Capture-Module-USB-Programmer-Downloader/32907587711.html?spm=a2g0s.9042311.0.0.3da24c4dXV8sBI" target="_blank" rel="noopener"
|
||
>CC2531 zigbee
|
||
sniffer</a>.</li>
|
||
<li><a class="link" href="https://www.aliexpress.com/item/CFSUNBIRD-CC-DEBUGGER-Debugger-and-Programmer-for-RF-System-on-Chips-TI-ORIGINAL-Fast-hipping/32813122315.html?spm=a2g0s.9042311.0.0.3da24c4dXV8sBI" target="_blank" rel="noopener"
|
||
>CC-debugger</a>.</li>
|
||
</ul>
|
||
<p>You will need to flash your sniffer. For that, you only need to follow
|
||
the instructions from the <a class="link" href="https://koenkk.github.io/zigbee2mqtt/" target="_blank" rel="noopener"
|
||
>zigbee2mqtt
|
||
documentation</a>.</p>
|
||
<p>Once you&rsquo;re done flashing, you&rsquo;re ready to set up the zigbee2mqtt
|
||
server. For convenience, I wrote a simple docker-compose to deploy a
|
||
zigbee2mqtt server and a test mosquitto server:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span><span class="lnt">14
|
||
</span><span class="lnt">15
|
||
</span><span class="lnt">16
|
||
</span><span class="lnt">17
|
||
</span><span class="lnt">18
|
||
</span><span class="lnt">19
|
||
</span><span class="lnt">20
|
||
</span><span class="lnt">21
|
||
</span><span class="lnt">22
|
||
</span><span class="lnt">23
|
||
</span><span class="lnt">24
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="s1">&#39;2.1&#39;</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">services</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">zigbee2mqtt</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">koenkk/zigbee2mqtt</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">zigbee2mqtt </span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">always</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="l">./z2m-data/:/app/data/</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">devices</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="s2">&#34;/dev/ttyACM0&#34;</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">networks</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="l">hass</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">mqtt</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">eclipse-mosquitto</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">ports</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="m">1883</span><span class="p">:</span><span class="m">1883</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="m">9001</span><span class="p">:</span><span class="m">9001</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">networks</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="l">hass</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="l">./mosquitto.conf:/mosquitto/config/mosquitto.conf</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">networks</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">hass</span><span class="p">:</span><span class="w">
|
||
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">driver</span><span class="p">:</span><span class="w"> </span><span class="l">overlay</span><span class="w">
|
||
</span></span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>You can test your installation with:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span><span class="lnt">6
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">❯ mosquitto_sub -h localhost -p <span class="m">1883</span> -t <span class="s1">&#39;zigbee2mqtt/#&#39;</span>
|
||
</span></span><span class="line"><span class="cl">online
|
||
</span></span><span class="line"><span class="cl"><span class="o">{</span><span class="s2">&#34;battery&#34;</span>:17,<span class="s2">&#34;voltage&#34;</span>:2925,<span class="s2">&#34;linkquality&#34;</span>:149,<span class="s2">&#34;action&#34;</span>:<span class="s2">&#34;rotate_right&#34;</span>,<span class="s2">&#34;angle&#34;</span>:12.8<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"><span class="o">{</span><span class="s2">&#34;battery&#34;</span>:17,<span class="s2">&#34;voltage&#34;</span>:2925,<span class="s2">&#34;linkquality&#34;</span>:141,<span class="s2">&#34;action&#34;</span>:<span class="s2">&#34;slide&#34;</span>,<span class="s2">&#34;side&#34;</span>:2<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"><span class="o">{</span><span class="s2">&#34;battery&#34;</span>:17,<span class="s2">&#34;voltage&#34;</span>:2925,<span class="s2">&#34;linkquality&#34;</span>:120<span class="o">}</span>
|
||
</span></span><span class="line"><span class="cl"><span class="o">{</span><span class="s2">&#34;battery&#34;</span>:17,<span class="s2">&#34;voltage&#34;</span>:2925,<span class="s2">&#34;linkquality&#34;</span>:141,<span class="s2">&#34;action&#34;</span>:<span class="s2">&#34;wakeup&#34;</span><span class="o">}</span></span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div>
|
||
<p>zigbee2mqtt supports the following events for the aqara cube: shake,
|
||
wakeup, fall, tap, slide, flip180, flip90, rotate_left and
|
||
rotate_right. Every event has additional information, such as the sides
|
||
involved, or the degrees turned.</p>
|
||
<p>Now you are ready to set up home assistant support in zigbee2mqtt
|
||
following <a class="link" href="https://koenkk.github.io/zigbee2mqtt/integration/home_assistant.html" target="_blank" rel="noopener"
|
||
>this
|
||
guide</a>.</p></description></item><item><title>Progress bars in python</title><link>https://balkian.com/p/progress-bars-in-python/</link><pubDate>Wed, 28 Sep 2016 18:47:00 +0000</pubDate><guid>https://balkian.com/p/progress-bars-in-python/</guid><description><p><a class="link" href="https://github.com/noamraph/tqdm" target="_blank" rel="noopener"
|
||
>tqdm</a> is a nice way to add progress
|
||
bars in the command line or in a jupyter notebook.</p>
|
||
<p><img src="https://camo.githubusercontent.com/48838faaa8d00ea297f18e5bf55d3c6bb4e0ba6b/68747470733a2f2f692e696d6775722e636f6d2f686539417735432e676966"
|
||
loading="lazy"
|
||
alt="image"
|
||
></p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"><span class="line"><span class="cl"><span class="kn">from</span> <span class="nn">tqdm</span> <span class="kn">import</span> <span class="n">tqdm</span>
|
||
</span></span><span class="line"><span class="cl"><span class="kn">import</span> <span class="nn">time</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">for</span> <span class="n">i</span> <span class="ow">in</span> <span class="n">tqdm</span><span class="p">(</span><span class="nb">range</span><span class="p">(</span><span class="mi">100</span><span class="p">)):</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">time</span><span class="o">.</span><span class="n">sleep</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Sharing dotfiles</title><link>https://balkian.com/p/sharing-dotfiles/</link><pubDate>Fri, 10 Apr 2015 17:47:00 +0000</pubDate><guid>https://balkian.com/p/sharing-dotfiles/</guid><description><p>Today&rsquo;s post is half a quick note, half public shaming. In other words,
|
||
it is a reminder to be very careful with OAuth tokens and passwords.</p>
|
||
<p>As part of moving to emacs, I starting using the incredibly useful
|
||
<a class="link" href="https://github.com/defunkt/gist.el" target="_blank" rel="noopener"
|
||
>gh.el</a>. When you first use it, the
|
||
extension saves either your password or an OAuth token in your
|
||
.gitconfig file. This is cool and convenient, unless you <a class="link" href="https://github.com/balkian/dotfiles" target="_blank" rel="noopener"
|
||
>happen to be
|
||
publishing your .gitconfig file in a public
|
||
repo</a>.</p>
|
||
<p>So, how can you still share your gitconfig without sharing your
|
||
password/token with the rest of the world? Since Git 1.7.0, you can
|
||
<a class="link" href="http://stackoverflow.com/questions/1557183/is-it-possible-to-include-a-file-in-your-gitconfig" target="_blank" rel="noopener"
|
||
>include other files in your
|
||
gitconfig</a>.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">[include]
|
||
</span></span><span class="line"><span class="cl"> path = ~/.gitconfig_secret
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>And now, in your .gitconfig_secret file, you just have to add this:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">[github]
|
||
</span></span><span class="line"><span class="cl"> user = balkian
|
||
</span></span><span class="line"><span class="cl"> token = &#34;&lt; Your secret token &gt;&#34;
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Zotero</title><link>https://balkian.com/p/zotero/</link><pubDate>Tue, 09 Dec 2014 12:12:12 +0000</pubDate><guid>https://balkian.com/p/zotero/</guid><description><p><a class="link" href="https://www.zotero.org/" target="_blank" rel="noopener"
|
||
>Zotero</a> is an Open Source tool that lets you
|
||
organise your bibliography, syncing it with the cloud. Unlike other
|
||
alternatives such as <a class="link" href="http://www.mendeley.com" target="_blank" rel="noopener"
|
||
>Mendeley</a>, Zotero can
|
||
upload the attachments and data to a private cloud via WebDav.</p>
|
||
<p>If you use nginx as your web server, know that even though it provides
|
||
partial support for webdav, Zotero needs more than that. Hence, you will
|
||
need another webdav server, and optionally let nginx proxy to it. This
|
||
short post provides the basics to get that set-up working under
|
||
Debian/Ubuntu.</p>
|
||
<h2 id="setting-up-apache">Setting up Apache
|
||
</h2><p>First we need to install Apache:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install apache2
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Change the head of &ldquo;/etc/apache2/sites-enabled/000-default&rdquo; to:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-apache" data-lang="apache"><span class="line"><span class="cl"><span class="nt">&lt;VirtualHost</span> <span class="s">*:880</span><span class="nt">&gt;</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Then, create a file /etc/apache2/sites-available/webdav:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-apache" data-lang="apache"><span class="line"><span class="cl"><span class="nb">Alias</span> <span class="sx">/dav</span> <span class="sx">/home/webdav/dav</span>
|
||
</span></span><span class="line"><span class="cl"><span class="nt">&lt;Location</span> <span class="s">/dav</span><span class="nt">&gt;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Dav</span> <span class="k">on</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Order</span> Allow,Deny
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Allow</span> from <span class="k">all</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Dav</span> <span class="k">On</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Options</span> +Indexes
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">AuthType</span> Basic
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">AuthName</span> DAV
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">AuthBasicProvider</span> file
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">AuthUserFile</span> <span class="sx">/home/webdav/.htpasswd</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">Require</span> valid-user
|
||
</span></span><span class="line"><span class="cl"><span class="nt">&lt;/Location&gt;</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Ideally, you want your webdav folders to be private, adding
|
||
authentication to them. So you need to create the webdav and zotero
|
||
users and add the passwords to an htpasswd file. Even though you could
|
||
use a single user, since you will be configuring several clients with
|
||
your credentials I encourage you to create the zotero user as well. This
|
||
way you can always change the password for zotero without affecting any
|
||
other application using webdav.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo adduser webdav
|
||
</span></span><span class="line"><span class="cl">sudo htpasswd -c /home/webdav/.htpasswd webdav
|
||
</span></span><span class="line"><span class="cl">sudo htpasswd /home/webdav/.htpasswd zotero
|
||
</span></span><span class="line"><span class="cl">sudo mkdir -p /home/webdav/dav/zotero
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Enable the site and restart apache:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo a2enmod webdav
|
||
</span></span><span class="line"><span class="cl">sudo a2enmod dav_fs
|
||
</span></span><span class="line"><span class="cl">sudo a2ensite webdav
|
||
</span></span><span class="line"><span class="cl">sudo service apache2 restart
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>At this point everything should be working at
|
||
<a class="link" href="http://" target="_blank" rel="noopener"
|
||
>http://</a>&lt;your_host&gt;:880/dav/zotero</p>
|
||
<h2 id="setting-up-nginx">Setting up NGINX
|
||
</h2><p>After the Apache side is working, we can use nginx as a proxy to get
|
||
cleaner URIs. In your desired site/location, add this:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span><span class="lnt">6
|
||
</span><span class="lnt">7
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-nginx" data-lang="nginx"><span class="line"><span class="cl"><span class="k">location</span> <span class="s">/dav</span> <span class="p">{</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kn">client_max_body_size</span> <span class="s">20M</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kn">proxy_set_header</span> <span class="s">X-Real-IP</span> <span class="nv">$remote_addr</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kn">proxy_set_header</span> <span class="s">X-Forwarded-For</span> <span class="nv">$remote_addr</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kn">proxy_set_header</span> <span class="s">Host</span> <span class="nv">$host</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kn">proxy_pass</span> <span class="s">http://127.0.0.1:880</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">}</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Now just reload nginx:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo service nginx force-reload
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h2 id="extras">Extras
|
||
</h2><ul>
|
||
<li><a class="link" href="http://zoteroreader.com/" target="_blank" rel="noopener"
|
||
>Zotero Reader</a> - HTML5 client</li>
|
||
<li><a class="link" href="https://github.com/ajlyon/zandy" target="_blank" rel="noopener"
|
||
>Zandy</a> - Android Open Source
|
||
client</li>
|
||
</ul></description></item><item><title>Proxies with Apache and python</title><link>https://balkian.com/p/proxies-with-apache-and-python/</link><pubDate>Thu, 09 Oct 2014 10:00:00 +0000</pubDate><guid>https://balkian.com/p/proxies-with-apache-and-python/</guid><description><p>This is a quick note on proxying a local python application (e.g. flask)
|
||
to a subdirectory in Apache. This assumes that the file wsgi.py contains
|
||
a WSGI application with the name <em>application</em>. Hence, wsgi:application.</p>
|
||
<h2 id="gunicorn">Gunicorn
|
||
</h2><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-apache" data-lang="apache"><span class="line"><span class="cl"><span class="nt">&lt;Location</span> <span class="s">/myapp/</span><span class="nt">&gt;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">ProxyPass</span> http://127.0.0.1:8888/myapp/
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">ProxyPassReverse</span> http://127.0.0.1:8888/myapp/
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">RequestHeader</span> set SCRIPT_NAME <span class="s2">&#34;/myapp/&#34;</span>
|
||
</span></span><span class="line"><span class="cl"><span class="nt">&lt;/Location&gt;</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p><strong>Important</strong>: <em>SCRIPT_NAME</em> and the end of <em>ProxyPass</em> URL <strong>MUST BE
|
||
THE SAME</strong>. Otherwise, Gunicorn will fail miserably.</p>
|
||
<p>Try it with:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">venv/bin/gunicorn -w <span class="m">4</span> -b 127.0.0.1:8888 --log-file - --access-logfile - wsgi:application
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h2 id="uwsgi">UWSGI
|
||
</h2><p>This is a very simple configuration. I will try to upload one with more
|
||
options for uwsgi (in a .ini file).</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-apache" data-lang="apache"><span class="line"><span class="cl"><span class="nt">&lt;Location</span> <span class="s">/myapp/</span><span class="nt">&gt;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">SetHandler</span> uwsgi_handler
|
||
</span></span><span class="line"><span class="cl"> <span class="nb">uWSGISocker</span> <span class="m">127.0.0.1</span>:8888
|
||
</span></span><span class="line"><span class="cl"><span class="nt">&lt;/Location&gt;</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Try it with:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">uwsgi --socket 127.0.0.1:8888 -w wsgi:application
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h2 id="extra-supervisor">Extra: Supervisor
|
||
</h2><p>If everything went as expected, you can wrap your command in a
|
||
supervisor config file and let it handle the server for you.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span><span class="lnt">14
|
||
</span><span class="lnt">15
|
||
</span><span class="lnt">16
|
||
</span><span class="lnt">17
|
||
</span><span class="lnt">18
|
||
</span><span class="lnt">19
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-ini" data-lang="ini"><span class="line"><span class="cl"><span class="k">[unix_http_server]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">file</span><span class="o">=</span><span class="s">/tmp/myapp.sock ; path to your socket file</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">[supervisord]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">logfile</span> <span class="o">=</span> <span class="s">%(here)s/logs/supervisor.log</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">childlogdir</span> <span class="o">=</span> <span class="s">%(here)s/logs/</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">[rpcinterface:supervisor]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">supervisor.rpcinterface_factory</span> <span class="o">=</span> <span class="s">supervisor.rpcinterface:make_main_rpcinterface</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">[supervisorctl]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">logfile</span> <span class="o">=</span> <span class="s">%(here)s/logs/supervisorctl.log</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">serverurl</span><span class="o">=</span><span class="s">unix:///tmp/supervisor.sock ; use a unix:// URL for a unix socket</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="k">[program:myapp]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">command</span> <span class="o">=</span> <span class="s">venv/bin/gunicorn -w 4 -b 0.0.0.0:5000 --log-file %(here)s/logs/gunicorn.log --access-logfile - wsgi:application</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">directory</span> <span class="o">=</span> <span class="s">%(here)s</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">environment</span> <span class="o">=</span> <span class="s">PATH=%(here)s/venv/bin/</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">logfile</span> <span class="o">=</span> <span class="s">%(here)s/logs/myapp.log</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Publishing on PyPi</title><link>https://balkian.com/p/publishing-on-pypi/</link><pubDate>Sat, 27 Sep 2014 10:00:00 +0000</pubDate><guid>https://balkian.com/p/publishing-on-pypi/</guid><description><p>Developing a python module and publishing it on Github is cool, but most
|
||
of the times you want others to download and use it easily. That is the
|
||
role of PyPi, the python package repository. In this post I show you how
|
||
to publish your package in less than 10 minutes.</p>
|
||
<h2 id="choose-a-fancy-name">Choose a fancy name
|
||
</h2><p>If you haven&rsquo;t done so yet, take a minute or two to think about this.
|
||
To publish on PyPi you need a name for your package that isn&rsquo;t taken.
|
||
What&rsquo;s more, a catchy and unique name will help people remember your
|
||
module and feel more inclined to at least try it.</p>
|
||
<p>The package name should hint what your module does, but that&rsquo;s not
|
||
always the case. That&rsquo;s your call. I personally put uniqueness and
|
||
memorability over describing the functionality.</p>
|
||
<h2 id="create-a-pypirc-configuration-file">Create a .pypirc configuration file
|
||
</h2><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span><span class="lnt">13
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="na">[distutils] # this tells distutils what package indexes you can push to</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">index-servers</span> <span class="o">=</span><span class="s">
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> pypi # the live PyPI
|
||
</span></span></span><span class="line"><span class="cl"><span class="s"> pypitest # test PyPI</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="na">[pypi] # authentication details for live PyPI</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">repository</span> <span class="o">=</span> <span class="s">https://pypi.python.org/pypi</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">username</span> <span class="o">=</span> <span class="s">{ your_username }</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">password</span> <span class="o">=</span> <span class="s">{ your_password } # not necessary</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="na">[pypitest] # authentication details for test PyPI</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">repository</span> <span class="o">=</span> <span class="s">https://testpypi.python.org/pypi</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">username</span> <span class="o">=</span> <span class="s">{ your_username }</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>As you can see, you need to register both in the <a class="link" href="https://pypi.python.org/pypi?%3Aaction=register_form" target="_blank" rel="noopener"
|
||
>main pypi
|
||
repository</a> and
|
||
the <a class="link" href="https://testpypi.python.org/pypi?%3Aaction=register_form" target="_blank" rel="noopener"
|
||
>testing
|
||
server</a>. The
|
||
usernames and passwords might be different, that is up to you!</p>
|
||
<h2 id="prepare-your-package">Prepare your package
|
||
</h2><p>This should be the structure:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">root-dir/ # Any name you want
|
||
</span></span><span class="line"><span class="cl"> setup.py
|
||
</span></span><span class="line"><span class="cl"> setup.cfg
|
||
</span></span><span class="line"><span class="cl"> LICENSE.txt
|
||
</span></span><span class="line"><span class="cl"> README.md
|
||
</span></span><span class="line"><span class="cl"> mypackage/
|
||
</span></span><span class="line"><span class="cl"> __init__.py
|
||
</span></span><span class="line"><span class="cl"> foo.py
|
||
</span></span><span class="line"><span class="cl"> bar.py
|
||
</span></span><span class="line"><span class="cl"> baz.py
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h3 id="setupcfg">setup.cfg
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="k">[metadata]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">description-file</span> <span class="o">=</span> <span class="s">README.md</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>The markdown README is the <em>de facto</em> standard in Github, but you can
|
||
also use rST (reStructuredText), the standard in the python community.</p>
|
||
<h3 id="setuppy">setup.py
|
||
</h3><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"><span class="line"><span class="cl"><span class="kn">from</span> <span class="nn">distutils.core</span> <span class="kn">import</span> <span class="n">setup</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="n">setup</span><span class="p">(</span><span class="n">name</span> <span class="o">=</span> <span class="s1">&#39;mypackage&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">packages</span> <span class="o">=</span> <span class="p">[</span><span class="s1">&#39;mypackage&#39;</span><span class="p">],</span> <span class="c1"># this must be the same as the name above</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">version</span> <span class="o">=</span> <span class="s1">&#39;{ version }&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">description</span> <span class="o">=</span> <span class="s1">&#39;{ description }&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">author</span> <span class="o">=</span> <span class="s1">&#39;{ name }&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">email</span> <span class="o">=</span> <span class="s1">&#39;{ email }&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">url</span> <span class="o">=</span> <span class="s1">&#39;https://github.com/</span><span class="si">{user}</span><span class="s1">/</span><span class="si">{package}</span><span class="s1">&#39;</span><span class="p">,</span> <span class="c1"># URL to the github repo</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">download_url</span> <span class="o">=</span> <span class="s1">&#39;https://github.com/</span><span class="si">{user}</span><span class="s1">/</span><span class="si">{repo}</span><span class="s1">/tarball/</span><span class="si">{version}</span><span class="s1">&#39;</span><span class="p">,</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">keywords</span> <span class="o">=</span> <span class="p">[</span><span class="s1">&#39;websockets&#39;</span><span class="p">,</span> <span class="s1">&#39;display&#39;</span><span class="p">,</span> <span class="s1">&#39;d3&#39;</span><span class="p">],</span> <span class="c1"># list of keywords that represent your package</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">classifiers</span> <span class="o">=</span> <span class="p">[],</span> <span class="p">)</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>You might notice that the download_url points to a Github URL. We could
|
||
host our package anywhere, but Github is a convenient option. To create
|
||
the tarball and the zip packages, you only need to tag a tag in your
|
||
repository and push it to github:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">git tag <span class="o">{</span>version<span class="o">}</span> -m <span class="s2">&#34;{ Description of this tag/version}&#34;</span>
|
||
</span></span><span class="line"><span class="cl">git push --tags origin master
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h2 id="push-to-the-testingmain-pypi-server">Push to the testing/main pypi server
|
||
</h2><p>It is advisable that you try your package on the test repository and fix
|
||
any problems first. The process is simple:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">python setup.py register -r <span class="o">{</span>pypitest/pypi<span class="o">}</span> python setup.py sdist upload -r <span class="o">{</span>pypitest/pypi<span class="o">}</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>If everything went as expected, you can now install your package through
|
||
pip and browse your package&rsquo;s page. For instance, check my senpy
|
||
package: <a class="link" href="https://pypi.python.org/pypi/senpy" target="_blank" rel="noopener"
|
||
>https://pypi.python.org/pypi/senpy</a></p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">pip install senpy
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Updating EuroLoveMap</title><link>https://balkian.com/p/updating-eurolovemap/</link><pubDate>Thu, 27 Mar 2014 14:00:00 +0000</pubDate><guid>https://balkian.com/p/updating-eurolovemap/</guid><description><p>As part of the <a class="link" href="http://www.opener-project.org/2013/07/18/opener-hackathon-in-amsterdam/" target="_blank" rel="noopener"
|
||
>OpeNER
|
||
hackathon</a>
|
||
we decided to build a prototype that would allow us to compare how
|
||
different countries feel about several topics. We used the OpeNER
|
||
pipeline to get the sentiment from a set of newspaper articles we
|
||
gathered from media in several languages. Then we aggregated those
|
||
articles by category and country (using the source of the article or the
|
||
language it was written in), obtaining the &ldquo;overall feeling&rdquo; of each
|
||
country about each topic. Then, we used some fancy JavaScript to make
|
||
sense out of the raw information.</p>
|
||
<p>It didn&rsquo;t go too bad, it turns out <a class="link" href="http://eurosentiment.eu/wp-content/uploads/2013/07/BOLv9qnCIAAJEek.jpg" target="_blank" rel="noopener"
|
||
>we
|
||
won</a>.</p>
|
||
<p>Now, it was time for a face-lift. I used this opportunity to play with
|
||
new technologies and improve it:</p>
|
||
<ul>
|
||
<li>Using Flask, this time using python 3.3 and Bootstrap 3.0</li>
|
||
<li>Cool HTML5+JS cards (thanks to
|
||
<a class="link" href="http://pastetophone.com" target="_blank" rel="noopener"
|
||
>pastetophone</a>)</li>
|
||
<li>Automatic generation of fake personal data to test the interface</li>
|
||
<li>Obfuscation of personal emails</li>
|
||
</ul>
|
||
<p>The result can be <a class="link" href="http://eurolovemap.herokuapp.com/" target="_blank" rel="noopener"
|
||
>seen here</a>.</p>
|
||
<h2 id="publishing-a-python-3-app-on-heroku">Publishing a Python 3 app on Heroku
|
||
</h2><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkvirtualenv -p /usr/bin/python3.3 eurolovemap
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Since Heroku uses python 2.7 by default, we have to tell it which
|
||
version we want, although it supports python 3.4 as well. I couldn&rsquo;t
|
||
get python 3.4 working using the
|
||
<a class="link" href="https://launchpad.net/~fkrull/&#43;archive/deadsnakes" target="_blank" rel="noopener"
|
||
>deadsnakes</a> ppa, so
|
||
I used python 3.3 instead, which works fine but is not officially
|
||
supported. Just create a file named <em>runtime.txt</em> in your project root,
|
||
with the python version you want to use:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python-3.3.1
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Don&rsquo;t forget to freeze your dependencies so Heroku can install them:
|
||
<code>bash pip freze &gt; requirements.txt</code></p>
|
||
<h2 id="publishing-personal-emails">Publishing personal emails
|
||
</h2><p>There are really sophisticated and effective ways to obfuscate personal
|
||
emails so that spammers cannot easily grab yours. However, this time I
|
||
needed something really simple to hide our emails from the simplest form
|
||
of crawlers. Most of the team are in academia somehow, so in the end all
|
||
our emails are available in sites like Google Scholar. Anyway, nobody
|
||
likes getting spammed so I settled for a custom <a class="link" href="http://en.wikipedia.org/wiki/Caesar_cipher" target="_blank" rel="noopener"
|
||
>Caesar
|
||
cipher</a>. Please, don&rsquo;t use
|
||
it for any serious application if you are concerned about being spammed.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"><span class="line"><span class="cl"><span class="k">def</span> <span class="nf">blur_email</span><span class="p">(</span><span class="n">email</span><span class="p">):</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="s2">&#34;&#34;</span><span class="o">.</span><span class="n">join</span><span class="p">([</span><span class="nb">chr</span><span class="p">(</span><span class="nb">ord</span><span class="p">(</span><span class="n">i</span><span class="p">)</span><span class="o">+</span><span class="mi">5</span><span class="p">)</span> <span class="k">for</span> <span class="n">i</span> <span class="ow">in</span> <span class="n">email</span><span class="p">])</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>And this is the client side:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt"> 1
|
||
</span><span class="lnt"> 2
|
||
</span><span class="lnt"> 3
|
||
</span><span class="lnt"> 4
|
||
</span><span class="lnt"> 5
|
||
</span><span class="lnt"> 6
|
||
</span><span class="lnt"> 7
|
||
</span><span class="lnt"> 8
|
||
</span><span class="lnt"> 9
|
||
</span><span class="lnt">10
|
||
</span><span class="lnt">11
|
||
</span><span class="lnt">12
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="nb">window</span><span class="p">.</span><span class="nx">onload</span> <span class="o">=</span> <span class="kd">function</span><span class="p">(){</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nx">elems</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">getElementsByClassName</span><span class="p">(</span><span class="s1">&#39;profile-email&#39;</span><span class="p">);</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="k">for</span><span class="p">(</span><span class="kd">var</span> <span class="nx">e</span> <span class="k">in</span> <span class="nx">elems</span><span class="p">){</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kd">var</span> <span class="nx">blur</span> <span class="o">=</span> <span class="nx">elems</span><span class="p">[</span><span class="nx">e</span><span class="p">].</span><span class="nx">innerHTML</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kd">var</span> <span class="nx">email</span> <span class="o">=</span> <span class="s2">&#34;&#34;</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="k">for</span><span class="p">(</span><span class="kd">var</span> <span class="nx">s</span> <span class="k">in</span> <span class="nx">blur</span><span class="p">){</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="kd">var</span> <span class="nx">a</span> <span class="o">=</span> <span class="nx">blur</span><span class="p">.</span><span class="nx">charCodeAt</span><span class="p">(</span><span class="nx">s</span><span class="p">)</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nx">email</span> <span class="o">=</span> <span class="nx">email</span><span class="o">+</span><span class="nb">String</span><span class="p">.</span><span class="nx">fromCharCode</span><span class="p">(</span><span class="nx">a</span><span class="o">-</span><span class="mi">5</span><span class="p">);</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">}</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="nx">elems</span><span class="p">[</span><span class="nx">e</span><span class="p">].</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="nx">email</span><span class="p">;</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="p">}</span>
|
||
</span></span><span class="line"><span class="cl"><span class="p">}</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Unfortunately, this approach does not hide your email from anyone using
|
||
<a class="link" href="http://phantomjs.org/" target="_blank" rel="noopener"
|
||
>PhantomJS</a>,
|
||
<a class="link" href="http://zombie.labnotes.org/" target="_blank" rel="noopener"
|
||
>ZombieJS</a> or similar. For that, other
|
||
approaches like generating a picture with the address would be
|
||
necessary. Nevertheless, it is overkill for a really simple ad-hoc
|
||
application with custom formatting and just a bunch of emails that would
|
||
easily be grabbed manually.</p>
|
||
<h2 id="generation-of-fake-data">Generation of fake data
|
||
</h2><p>To test the contact section of the site, I wanted to populate it with
|
||
fake data. <a class="link" href="https://github.com/joke2k/faker" target="_blank" rel="noopener"
|
||
>Fake-Factory</a> is an amazing
|
||
library that can generate fake data of almost any kind: emails,
|
||
association names, acronyms&hellip; It even lets you localise the results
|
||
(get Spanish names, for instance) and generate factories for certain
|
||
classes (à la Django).</p>
|
||
<p>But I also wanted pictures, enter <a class="link" href="http://lorempixel.com/" target="_blank" rel="noopener"
|
||
>Lorem Pixel</a>.
|
||
With its API you can generate pictures of almost any size, for different
|
||
topics (e.g. nightlife, people) and with a custom text. You can even use
|
||
an index, so it will always show the same picture.</p>
|
||
<p>For instance, the picture below is served through Lorem Pixel.</p>
|
||
<p><img src="http://lorempixel.com/400/200/nightlife/"
|
||
loading="lazy"
|
||
></p>
|
||
<p>By the way, if you only want cat pictures, take a look at
|
||
<a class="link" href="http://placekitten.com/" target="_blank" rel="noopener"
|
||
>Placekitten</a>. And for NSFW text, there&rsquo;s the
|
||
<a class="link" href="http://slipsum.com/" target="_blank" rel="noopener"
|
||
>Samuel L. Jackson Ipsum</a></p></description></item><item><title>Remove git files with globbing</title><link>https://balkian.com/p/remove-git-files-with-globbing/</link><pubDate>Thu, 22 Aug 2013 23:14:00 +0000</pubDate><guid>https://balkian.com/p/remove-git-files-with-globbing/</guid><description><p>A simple trick. If you want to remove all the &lsquo;.swp&rsquo; files from a git
|
||
repository, just use:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">git rm --cached <span class="s1">&#39;**.swp&#39;</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Creating my web</title><link>https://balkian.com/p/creating-my-web/</link><pubDate>Thu, 22 Aug 2013 14:14:22 +0000</pubDate><guid>https://balkian.com/p/creating-my-web/</guid><description><p>I&rsquo;ve finally decided to set up a decent personal page. I have settled
|
||
for github-pages because I like the idea of keeping my site in a
|
||
repository and having someone else host and deploy it for me. The site
|
||
will be really simple, mostly static files. Thanks to Github,
|
||
<a class="link" href="http://jekyllrb.com" target="_blank" rel="noopener"
|
||
>Jekyll</a> will automatically generate static pages
|
||
for my posts every time I commit anything new to this repository.</p>
|
||
<p>But Jekyll can be used independently, so if I ever choose to host the
|
||
site myself, I can do it quite easily. Another thing that I liked about
|
||
this approach is that the generated html files can be used in the
|
||
future, and I will not need Jekyll to serve it. Jekyll is really simple
|
||
and most of the things are written in plain html. That means that
|
||
everything could be easily reused if I ever choose to change to another
|
||
blogging framework (e.g. pelical). But, for the time being, I like the
|
||
fact that Github takes care of the compilation as well, so I can simply
|
||
modify or add files through the web interface should I need to.</p>
|
||
<p>I hadn&rsquo;t played with HTML and CSS for a while now, so I also wanted to
|
||
use this site as a playground. At some point, I realised I was doing
|
||
mostly everything in plain HTML and CSS, and decided to keep it like
|
||
that for as long as possible. As of this writing, I haven&rsquo;t included
|
||
any Javascript code in the page. Probably I will use some to add my
|
||
<a class="link" href="http://gist.github.com/balkian" target="_blank" rel="noopener"
|
||
>gists</a> and
|
||
<a class="link" href="http://github.com/balkian" target="_blank" rel="noopener"
|
||
>repositories</a>, but we will see about that.</p>
|
||
<p>I think the code speaks for itself, so you can check out <a class="link" href="http://github.com/balkian/balkian.github.com" target="_blank" rel="noopener"
|
||
>my repository
|
||
on Github</a>. You can clone
|
||
and deploy it easily like this:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">git clone
|
||
</span></span><span class="line"><span class="cl">https://github.com/balkian/balkian.github.com <span class="nb">cd</span> balkian.github.com
|
||
</span></span><span class="line"><span class="cl">jekyll serve -w
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>I will keep updating this post with information about:</p>
|
||
<ul>
|
||
<li>Some Jekyll plugins that might be useful</li>
|
||
<li>What CSS tricks I learnt</li>
|
||
<li>The webfonts I used</li>
|
||
<li>The badge on the left side of the page</li>
|
||
</ul></description></item><item><title>Emacs</title><link>https://balkian.com/emacs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/emacs/</guid><description><img src="https://balkian.com/img/emacs.png" alt="Featured image of post Emacs" /><h2 id="show-plain-text-version">Show plain text version
|
||
</h2><div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-lisp" data-lang="lisp"><span class="line"><span class="cl"><span class="p">(</span><span class="nv">font-lock-mode</span><span class="p">)</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Links</title><link>https://balkian.com/links/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/links/</guid><description/></item><item><title>Linux</title><link>https://balkian.com/linux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/linux/</guid><description><img src="https://balkian.com/img/linux.png" alt="Featured image of post Linux" /><h2 id="black-screen-and-lightdm-doesnt-unlock">Black screen and LightDM doesn&rsquo;t unlock
|
||
</h2><p>Add this to your /etc/lightdm/lightdm.conf file:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="k">[LightDM]</span>
|
||
</span></span><span class="line"><span class="cl"><span class="na">logind-check-graphical</span><span class="o">=</span><span class="s">true</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>##Edit previous commands</p>
|
||
<p><code>fc</code> is a shell builtin to list and edit previous commands in an editor.
|
||
In addition to editing a single line (which you can also do with <code>C-x C-e</code>), it also allows you to edit and run several lines at the same time.
|
||
You use it like this:</p>
|
||
<p>List previous commands</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">$ <span class="nb">fc</span> -l
|
||
</span></span><span class="line"><span class="cl"><span class="m">10259</span> nvim deploy.sh
|
||
</span></span><span class="line"><span class="cl">10260* <span class="nb">cd</span> ..
|
||
</span></span><span class="line"><span class="cl">10261* nvim content/cheatsheet/linux.md
|
||
</span></span><span class="line"><span class="cl"><span class="m">10262</span> <span class="nb">cd</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>List commands with date (in zsh)</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">$ <span class="nb">fc</span> -ld
|
||
</span></span><span class="line"><span class="cl">10260* 19:38 <span class="nb">cd</span> ..
|
||
</span></span><span class="line"><span class="cl">10261* 19:38 nvim content/cheatsheet/linux.md
|
||
</span></span><span class="line"><span class="cl"><span class="m">10262</span> 19:40 <span class="nb">cd</span>
|
||
</span></span><span class="line"><span class="cl"><span class="m">10263</span> 19:40 <span class="nb">fc</span> -l
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>You can add the date too:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">$ <span class="nb">fc</span> -fld
|
||
</span></span><span class="line"><span class="cl"><span class="m">10262</span> 1/10/2019 19:40 <span class="nb">cd</span>
|
||
</span></span><span class="line"><span class="cl"><span class="m">10263</span> 1/10/2019 19:40 <span class="nb">fc</span> -l
|
||
</span></span><span class="line"><span class="cl"><span class="m">10264</span> 1/10/2019 19:40 <span class="nb">fc</span> -ld
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>You can edit a range of commands</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">$ <span class="nb">fc</span> <span class="m">10262</span> <span class="m">10264</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>The range can be relative to the current position, so the previous command is equivalent to:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">$ <span class="nb">fc</span> -3 -1
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>If you save and exit, all commands are executed as a script, and it will be added to your history.</p>
|
||
<p>Source: <a class="link" href="https://shapeshed.com/unix-fc/" target="_blank" rel="noopener"
|
||
>https://shapeshed.com/unix-fc/</a></p>
|
||
<h2 id="prevent-logoff-from-killing-tmux-sessions">Prevent logoff from killing tmux sessions
|
||
</h2><p>Lately I&rsquo;ve noticed that logging out of i3, intentionally or when i3 fails, would also kill any tmux or emacs sessions.
|
||
This is extremely annoying.</p>
|
||
<p>This is caused by a new default in logind (systemd&rsquo;s login) to kill user process on logoff.
|
||
You can revert this setting in your logind.conf (<code>/etc/systemd/logind.conf</code>):</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-cfg" data-lang="cfg"><span class="line"><span class="cl"><span class="na">KillUserProcesses</span><span class="o">=</span><span class="s">no</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Or only for a specific process (e.g., tmux):</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">systemd-run --scope --user tmux
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Source: <a class="link" href="https://unix.stackexchange.com/questions/490267/prevent-logoff-from-killing-tmux-session" target="_blank" rel="noopener"
|
||
>https://unix.stackexchange.com/questions/490267/prevent-logoff-from-killing-tmux-session</a></p>
|
||
<h2 id="upload-a-temporary-file">Upload a temporary file
|
||
</h2><p>Sometimes you just need to copy/paste a file from a server, and copying from the terminal can be a hassle.
|
||
These two services are command-line &ldquo;pastebins&rdquo; just one curl away:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span><span class="lnt">6
|
||
</span><span class="lnt">7
|
||
</span><span class="lnt">8
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">&lt;command&gt; <span class="p">|</span> curl -F <span class="s1">&#39;sprunge=&lt;-&#39;</span> http://sprunge.us
|
||
</span></span><span class="line"><span class="cl"><span class="c1"># OR</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl">&lt;command&gt; 2&gt;<span class="p">&amp;</span><span class="m">1</span> <span class="p">|</span> curl -F <span class="s1">&#39;f:1=&lt;-&#39;</span> ix.io
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"><span class="c1"># OR</span>
|
||
</span></span><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl">&lt;command&gt; <span class="p">|</span> curl -F<span class="s2">&#34;file=@-&#34;</span> https://ttm.sh
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><h1 id="install-fortinet-sslvpn-support-for-networkmanager">Install Fortinet SSLVPN support for NetworkManager
|
||
</h1><p>UPM (Universidad Politécnica de Madrid) uses a propriatary VPN solution.
|
||
The instructions for GNU/Linux on their website involve downloading a specific client (<code>.tar.gz</code>) and manually running it.
|
||
That works, but it is kind of a hassle.
|
||
A much more convenient alternative is installing this NetworkManager plugin:</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">pacman -Sy networkmanager-fortisslvpn
|
||
</span></span><span class="line"><span class="cl"><span class="c1"># Or apt get install networkmanager-fortisslvpn </span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div><p>Now you can simply add a new VPN connection in NetworkManager and manage it as you would any other connection.</p></description></item><item><title>Projects</title><link>https://balkian.com/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/projects/</guid><description><h1 id="ongoing-projects">Ongoing Projects
|
||
</h1><ul>
|
||
<li><a class="link" href="https://soilsim.readthedocs.io" target="_blank" rel="noopener"
|
||
>Soil</a>: an agent-based simulator for social networks based on nx-sim and networkx.</li>
|
||
<li><a class="link" href="https://github.com/balkian/soilent" target="_blank" rel="noopener"
|
||
>Soilent</a>: an efficient scheduler for soil using rust and pyo3.</li>
|
||
<li><a class="link" href="https://senpy.readthedocs.io" target="_blank" rel="noopener"
|
||
>Senpy</a>: a framework for semantic sentiment and emotion analysis services.</li>
|
||
</ul>
|
||
<h1 id="past-projects">Past Projects
|
||
</h1><ul>
|
||
<li><a class="link" href="http://gsi.dit.upm.es/ontologies/onyx" target="_blank" rel="noopener"
|
||
>Onyx</a>: an ontology for emotion analysis that includes concepts from W3C&rsquo;s provenance.</li>
|
||
<li><a class="link" href="https://github.com/balkian/ESP8266_Clock_NTP" target="_blank" rel="noopener"
|
||
>ESP8266 Clock NTP</a>: a simple clock display using arduino, the ESP8266 and NTP (network time protocol).</li>
|
||
<li><a class="link" href="https://github.com/balkian/shinesp" target="_blank" rel="noopener"
|
||
>Shine ESP</a>: control an ws2812b LED strip over the network with an ESP8266.</li>
|
||
<li><a class="link" href="https://github.com/balkian/bitter" target="_blank" rel="noopener"
|
||
>Bitter</a>: a wrapper and CLI over the (now defunct) Twitter API to researchers to download Twitter data much faster using multiple accounts.</li>
|
||
<li><a class="link" href="http://gsi.dit.upm.es/ontologies/marl" target="_blank" rel="noopener"
|
||
>Marl</a>: I updated this ontology, originally created by Adam Westerski, to make it compatible with the W3C&rsquo;s provenance ontology.</li>
|
||
<li><a class="link" href="http://github.com/balkian/hermes" target="_blank" rel="noopener"
|
||
>Hermes</a>: one of my first projects, developed together with David Pérez as the special custom assignment in one of our courses. Hermes is an affective bot designed to mimic the behavour of humans. It included a plug-in system for its sensors and actuators. The information from its sensors changed its emotional state, which was shown via its actuators. Among others, it could fetch inforation from Twitter or its host system and change the expressions of an external Face made with servo motors or speak via its Text-To-Speech software. For instance, it could detect it was running out of battery, showing a sad face and sending an alerting tweet. You can see it in action in these two youtube videos: <a class="link" href="http://www.youtube.com/watch?v=KnEYahPD9z4" target="_blank" rel="noopener"
|
||
>Part 1</a> and <a class="link" href="http://www.youtube.com/watch?v=lQZldCTPEJc" target="_blank" rel="noopener"
|
||
>Part 2</a>.</li>
|
||
<li><a class="link" href="http://github.com/gsi-upm/maia" target="_blank" rel="noopener"
|
||
>Maia</a>: the Modular Architecture for Intelligent Agents is an evented agent architecture that aims to update the classical frameworks for intelligent agents with the concepts emerged from the Live Web.</li>
|
||
<li><a class="link" href="http://github.com/eestec/eestec.portal" target="_blank" rel="noopener"
|
||
>EESTEC.net</a>: the Plone based official portal of EESTEC. It has been my first and only experience with Plone. I fixed some bugs and implemented basic features.</li>
|
||
</ul>
|
||
<p>For more information, check my list of public repositories in <a href="http://github.com/balkian"><i class="fab fa-github"> Github</i></a>.</p></description></item><item><title>Python</title><link>https://balkian.com/python/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/python/</guid><description><img src="https://balkian.com/img/python.png" alt="Featured image of post Python" /><h2 id="interesting-libraries">Interesting libraries
|
||
</h2><h3 id="tqdm"><a class="link" href="https://github.com/tqdm/tqdm" target="_blank" rel="noopener"
|
||
>TQDM</a>
|
||
</h3><p>From tqdm&rsquo;s github repository:</p>
|
||
<blockquote>
|
||
<p>tqdm means &ldquo;progress&rdquo; in Arabic (taqadum, تقدّم) and an abbreviation for &ldquo;I love you so much&rdquo; in Spanish (te quiero demasiado).</p></blockquote>
|
||
<p><img src="https://raw.githubusercontent.com/tqdm/tqdm/master/images/tqdm.gif"
|
||
loading="lazy"
|
||
alt="TQDM in action"
|
||
></p>
|
||
<h2 id="tools">Tools
|
||
</h2><h3 id="uv"><a class="link" href="https://github.com/astral-sh/uv" target="_blank" rel="noopener"
|
||
>uv</a>
|
||
</h3><p>🚀 A single tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.
|
||
⚡️ 10-100x faster than pip.</p>
|
||
<ul>
|
||
<li>Provides comprehensive project management, with a universal lockfile.</li>
|
||
<li>Runs scripts, with support for inline dependency metadata.</li>
|
||
<li>Installs and manages Python versions.</li>
|
||
<li>Runs and installs tools published as Python packages.</li>
|
||
<li>Includes a pip-compatible interface for a performance boost with a familiar CLI.</li>
|
||
<li>Supports Cargo-style workspaces for scalable projects.</li>
|
||
<li>Disk-space efficient, with a global cache for dependency deduplication.</li>
|
||
<li>Installable without Rust or Python via curl or pip.</li>
|
||
<li>Supports macOS, Linux, and Windows.</li>
|
||
</ul></description></item><item><title>Raspberry Pi</title><link>https://balkian.com/raspberry-pi/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/raspberry-pi/</guid><description><img src="https://balkian.com/img/rpi.png" alt="Featured image of post Raspberry Pi" /><h2 id="hdmi-flickering">HDMI flickering
|
||
</h2><p>Avoid HDMI flickering/intermittent blanking on RPI with a 1400x1050 VGA monitor.</p>
|
||
<div class="highlight"><div class="chroma">
|
||
<table class="lntable"><tr><td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code><span class="lnt">1
|
||
</span><span class="lnt">2
|
||
</span><span class="lnt">3
|
||
</span><span class="lnt">4
|
||
</span><span class="lnt">5
|
||
</span><span class="lnt">6
|
||
</span></code></pre></td>
|
||
<td class="lntd">
|
||
<pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"><span class="line"><span class="cl">
|
||
</span></span><span class="line"><span class="cl"> <span class="n">hdmi_drive</span><span class="o">=</span><span class="mi">2</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">hdmi_group</span><span class="o">=</span><span class="mi">2</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">hdmi_mode</span><span class="o">=</span><span class="mi">42</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">disable_overscan</span><span class="o">=</span><span class="mi">1</span>
|
||
</span></span><span class="line"><span class="cl"> <span class="n">config_hdmi_boost</span><span class="o">=</span><span class="mi">7</span>
|
||
</span></span></code></pre></td></tr></table>
|
||
</div>
|
||
</div></description></item><item><title>Search</title><link>https://balkian.com/search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://balkian.com/search/</guid><description/></item></channel></rss> |