Table of Contents

1 Blog posts

I'm Jakob and this is my blog. Please drop me an e-mail if you have questions on any of the topics.

This is just a quick HTML export of my Org mode file which I'm currently managing in Vim.

1.1 Using the Neo keyboard layout on a physical US keyboard [2017-10-17 Tue]

Neo is a keyboard layout which is optimized for German but also great for English, programming, and other languages. As I bought my Laptop in the US, I have a physical US keyboard which is not perfect for using the Neo layout: The enter key on an US keyboard is wide and low. The mod3 key (labeled with |\) is above the enter key and it is hard to reach.

This article shows how the US keyboard layout is actually not good for programming. Using Neo is already a huge optimization, but the mod3 key on a physical US keyboard sucks.

Working on Linux, I decided to swap enter and mod3. The advantages are:

  • The two mod3 keys (left and right) are symmetrical now.
  • The mod3 key is easier to reach. (And I'm pretty sure I use mod3 more often than enter.)

The rest of this article describes how I managed to swapped these two keys.

1.1.1 How it worked for me

I use the ~/.Xmodmap file to redefine some keys. I don't know which Linux desktops source this file automatically. Using xmonad, I had to source the file during startup with this command: sleep 3 && xmodmap ~/.Xmodmap &

! This is a comment line
! This mapping swaps Neo's right Mod3 and the Return key on my physical US keyboard.
! I recommend this settings for Neo users who have to work on physical US keyboards.

! :r !xmodmap -pke | grep Level3_Shift
keycode  51 = Return Return Return

! :r !xmodmap -pke | grep Return
keycode  36 = ISO_Level3_Shift ISO_Level3_Shift ISO_Level3_Shift

! You can activate the mapping from VIM using one of these command
! :!xmodmap %
! :w !xmodmap -
! Or from the command line with

In this configuration file there are comments suggesting Vim commands to generate the configuration because the key codes and identifiers might differ from system to system.


1.2 Writing a thesis with LaTeX, knitr, TikZ, R, GNU Make, …

1.2.1 Make-options for the thesis [2017-10-17 Tue]

The make program can take options in this format:


Make will automatically define and export these options as environment variables, available for all recepies. For my thesis I use these two options to enable TikZ on demand (because the compilation with TikZ is much slower) and to create a book print with roman and arabic page numbering (as opposed to a PDF with only arabic page numbering which I prefer).

To make this working, I have to manipulate my main thesis.Rtex file. BTW, the file is called .Rtex, not .tex, because the knitr preprocessor first evaluates the embedded R code and generates the .tex file.

At the beginning of my thesis.Rtex I have the following chunks of R code:

... % latex preamble


... % latex code

<<echo=FALSE, results='asis'>>=
if (ifdef('BOOK_PRINT')) {

... % latex code

if (ifdef('USE_TIKZ')) {
    # tikz takes a very long time!
    # Use it for the final version:
    opts_chunk$set(dev = 'tikz')

... % latex code

The first chunk loads an R file which defines a function ifdef (similar to the ifdef macro in C/C++).

The second chunk changes the page numbering to roman (for table of contents and list of figures, tables, listings, …). Later there is a chunk to reset the page numbering to arabic, starting at chapter 1.

The third chunk enables TikZ as output device for R plots.

This is my helpers.R file:

isSet = function(val) {
    if (is.character(val))
	return(val != '')
ifdef = function(name) {
    var = Sys.getenv(name)

1.2.2 Printing the thesis [2016-10-28 Fri]

So yesterday I finished my thesis! It will be printed in a few hours. A few pages will be printed in color – so I noted their real page numbers (i.e. BOOK_PRINT=0, see my last post). Doing this, I stumbled upon this problem:

Cross references and links are highlighted in a blue color. For black/white print this is not a problem; links will be printed black (or grey). But links on colored pages will be printed in blue! This inconsistency looks horrible for me, so I added another knitr snippet in my thesis.Rtex file:

<<echo=FALSE, results='asis'>>=
if (ifdef('BOOK_PRINT')) {
} else {

It's important to note, that the \hypersetup command can only set this option if it has not been passed to the hyperref package yet.

    % colorlinks=true, % must not be set here!
    % ...

Finally I created the thesis.pdf with the command make BOOK_PRINT=1 and got a PDF file with non-highlighted links, roman page numbering for the first pages and arabic page numbering starting at the first chapter.

1.2.3 Finally, the result [2016-11-07 Mon]

In this post, I describe some steps of the fully automated compilation process of my master thesis. I'm referring to the Makefile.

The thesis can be downloaded here (PDF) and this is the GitHub repository:

  • latexmk -bibtex -lualatex thesis.tex
    • latexmk automatically processes the TeX file the correct number of times to enable the cross-references to the bibliography and other links to labels.
    • -bibtex, to use the literature database of my research group and my own one (.bib text files). These text file are not encoded in UTF-8; I think I should have better used bibtex8. With bibtex, I always have to write e.g. German umlauts like this: M\"uller. I wrote a bash script to translate fields like author names, abstract, etc. to the LaTeX ANSI encoding (
    • -luatex, to really enable use of UTF-8 in LaTeX source. For example, in math mode I can write $α \cdot β$ instead of $\alpha \cdot \beta$ which is much nicer to read and write (using the Neo keyboard layout).
  • ~R -q -e 'library(knitr); knit("thesis.Rtex", out = "thesis.tex")'~ – I use R in -q=uiet mode and pass an =-e=xpression to convert =thesis.Rtex to thesis.tex using knitr. The .Rtex format allows the use of R code in LaTeX, to generate numbers, tables, plots, and program output.
  • I use command line utilities (GNU core utils) like join, awk, cp, grep, sed, etc. to prepare some sources for inclusion in the LaTeX document.
  • ctags to generate a tags file to facilitate navigation in LaTeX sources in Vim.
  • There are scripts in tools/
    • to extract methods or functions from Java and R files,
    • to remove the indentation from source code,
    • to skip lines of source and replace them with "…",
    • and a tool to convert UMLet XML files to vector graphics (using umlet itself).
  • inkscape, to convert SVG files to PDF for inclusion in the document.
  • emacs' command line API and Org mode, to convert another .org source to PDF to include it in the document.
  • javap, to extract the class definition of a Java class from its binary file.

1.3 Vim usage of the dot operator [2016-10-28 Fri]   vim

Recently, I thought, I discovered a great new way to use the dot operator in Vim.

Suppose you want to make a number of lines to be LaTeX sections. I would place the cursor at the first line, and then type:

  • cc, to cut the line and switch to insert mode, and
  • \section{<C-r>"<BS>}<Esc>, to surround the line with the section command.

For other lines, I only have to position the cursor on them and press the dot (.).

But it does not work :(

:help . does not tell much about the dot operator. Apparently, the dot operator does not actually repeat the last atomic edit but rather reconstruct the effect in a naive way.

Consolation: Reading some docs, I just stumbled on the related :help redo-register. This feature of the dot operator enables you to paste words from the "delete history". I guess I will use this feature in future. Here is a use case:

Sometimes you delete some words or phrases and then you want to paste one of the phrases in a different place. p pastes the last deleted text – oh, that was the wrong one, undo it with u. ​"2p pastes the text deleted before. Oh, it's still the wrong one! Now you can press u., (repeatedly) and Vim pastes text from the history of deleted text.

P.S. Regarding the original problem (converting lines to LaTeX headers) there are other solutions, e.g. :s/\(.*\)/\\section{\1}/ and then & to repeat this command on other lines.

1.4 Using xmonad in a restrictive touch user interface [2016-11-25 Fri]   xmonad linux

At work we develop intensive care units for animal hospitals. Inside, there is an embedded computer which proivides a graphical user interface (amongst other things). The user can interact using the attached touch display.

Requirements for the GUI are that it is stable, secure, and hopefully not hackable. It must always display an web app running on localhost. It also must provide additional options such as configuring wifi and activating remote control.

Some specs:

  • OS: Debian GNU/Linux
  • Display server: X11
  • Window manager: xmonad
  • Desktop environment: xmonad, xmobar, stalonetray, nm-applet, controlpanel, xvkbd
  • User programs: chromium in app mode with touch mode enabled

The operating system and the display server are given. I chose xmonad as the window manager because it is highly configurable and an empty configuration is the perfect starting point for a very restrictive and secure desktop environment. These are the steps at system boot:

  1. Auto-login the restrictive user for the GUI
  2. Auto-start X: startx -- -nocursor in ~/.bash_profile
  3. Auto-start xmonad: exec xmonad in the ~/.xinitrc
  4. Start other programs, including the system tray and chromium in app-mode. This is done in a script which is spawn=ed from =~/.xmonad/xmonad.hs in the startupHook.

1.5 iCalendar (*.ics) to text on the Linux command line [2017-01-05 Thu]   linux haskell text

I googled for a command line tool to convert files from iCalendar format to plain text to analyze a calendar with tools like grep, sed, awk, cut, … I found nothing! At least not on the first result pages. The closest thing was an online tool to convert iCalendar to CSV, but it is not usable for the command line and also you would have to pass your calendar to an unknown webserver.

Luckily, Haskell has a great library to parse the iCalendar format. So I developed a tool following the UNIX philosophy: it's a filter program translating ics input to txt output. The output needs to be further processed with command line tools, or for example a statistical programming language like R.

Example usage:

# Display all meetings in December 2016
ical2text < calendar.ics | grep ^2016-12 | grep -i meeting | sort

More information and code can be found here:

For me it is really helpful in many use-cases.

1.5.1 Work hours using a shared calendar

We use a shared calendar to document work hours in our forest. In this calendar, an event title only consists of the first letters of the first name. For example, the event's title is "js" when Jakob and Simon worked at this time.

$ curl -s "$CALENDAR_URL" | ical2text | work-hours-statistics
Arbeitsstunden insgesamt: 44.5
B: 7.00 h (16 %)
H: 10.00 h (22 %)
J: 8.00 h (18 %)
K: 8.00 h (18 %)
S: 9.50 h (21 %)
Y: 2.00 h (4 %)

1.5.2 Vacation days at work

We use a shared calendar at work. In this calendar, we add events like "Urlaub Jakob" when I take days off. To get an overview of who took how many vacation days, we also use ical2text. There is a difficulty with multi-day events as well as weekends and holidays but some simple scripts overcome this problems:

ical2text < cal.ics | grep ^2016 \
  | grep Urlaub | grep Jakob \
  | expand-multiday-events \
  | remove-events-on-holidays german-holidays.ics \
  | remove-events-on-weekends \
  | wc -l
  • The program expand-multiday-events converts a line with a multi-day event to multiple lines of single full-day events.
  • The program remove-events-on-holidays removes lines with events that take place on a holiday.
  • The program remove-events-on-weekends does the same for events on weekends.

The final outcome is the number of Jakob's vacation days in 2016.

Note: There are holiday calendars on the web for download, e.g.

1.5.3 Acknowledging extraordinary work hours

We also use these programs at our start-up to acknowledge extraordinary work hours on holidays or weekends.

1.5.4 Yearly voluntary hours statistics at the Wasserwacht

We plan to use the program for statistics about voluntary hours for the Bayrisches Rotes Kreuz Wasserwacht in Holzkirchen. This will be a bit more complex because we need to include person names in the event description to get accurate statistics. The hours will also come from a couple sources, not only one calendar. This is because there is a variety of different events, trainings, classes, and rescue missions, and some processes (documentation, protocols) are complex.

1.6 Managing a file to only contain the latest output of a program [2017-01-23 Mon]   vim haskell text

It's a bit complicated to describe what this is and why it can be useful.

For example, you might start a command so that the GCC compiler automatically recompiles your source whenever you save the source file.1 Suppose you want to view the error output or use it in Vim for quickfix. You would need the output of a single compilation run, not the accumulated error output. This program fixes exactly that issue.

Consider this example:

# in one terminal:
cat | rewrite-after-timeout 4 /tmp/test.txt

# in a second terminal:
watch -n1 /tmp/test.txt

As long as you type text into cat, your input accumulates in the /tmp/test.txt output file. If you pause for 4 or more seconds and then start typing again, the output file is cleared before your new input is appended.

Now you can replace cat with the error output of a compiler to collect error messages from only one compilation run.

The code can be found here:

1.6.1 Use case: save error output of yesod devel or ghci to a file

For my Yesod web apps, I use yesod devel for running a test server and automatically recompiling the project. And I use ghci to do basically the same thing faster.2 I set up the following Bash aliases:

alias yesod-devel='stack exec -- yesod devel 3>&1 1>&2 2>&3 3>&- | tee >(rewrite-after-timeout 4 .ghc-errors.txt)'
alias ghci-devel='stack ghci                 3>&1 1>&2 2>&3 3>&- | tee >(rewrite-after-timeout 4 .ghc-errors.txt)'

With the weired 3>&1 ... I pipe stderr to tee without loosing stdout.3 In the tee command I use Bash process substitution which allows me to specify a command instead of a file. The command is my program which appends to or rewrites the error file.

In Vim, I :set makeprg=cat\ .ghc-errors.txt to import the error file for quickfix. When I execute :make, the errors are loaded in the quickfix list and I can start working on it.

I'm just getting started with the combination of Haskell, Yesod, GHCi, and Vim. I still have some problems with the Vim quickfix and the error format; e.g. multi-line error messages are not displayed properly in Vim, and GHCi-specific errors confuse Vim. But it's already better than locating the compiler erros by hand in Vim :)

1.7 Install onboard virtual keyboard on a Raspberry Pi [2017-04-28 Fri]   raspberrypi

I want the virtual keyboard Onboard on a Raspberry Pi 3.

This is my system:

$ uname -a
Linux intensobox4 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 8.0 (jessie)
Release:        8.0
Codename:       jessie

1.7.1 Installation

Onboard is not in Raspbian's package index (though it's in Debian's package index*). sudo apt-get install onboard says "package not found" and apt-cache search onboard returns nothing useful.

So this is how to install it manually.

Copy the download link of the archive:

tar xf onboard...
cd onboard...

Start Onboard's installer:

sudo ./ install

Here comes the first error:

To build Onboard you need

Since head shows that the setup tool uses Python 3, I install the package python3-distutils-extra with sudo apt-get install.

On the next try, the setup tells me: get_pkg_version('dconf'): pkg-config returned exit code 1

So I install the dconf package with sudo apt-get install.

Now the setup still gives the same error. The reason is that the setup uses FreeDesktop's pkg-config to test for the dconf package. However dconf (at least at Raspian) does not support FreeDesktops pkg-config specification1. Therefore pkg-config cannot find the package.

So we have to change setup's source: In search for get_pkg_version.*dconf, comment this line out and insert major, minor, revision = 1, 0, 0 instead. It's important that the next if condition is not satisfied, otherwise the environment variable DCONF_API_0 is defined which signals the use of an old dconf version which leads to more errors.

Now the setup comes up with a new error: pkg-config returned exit code 1 sdist needs libgtk-3-dev, libxtst-dev, libxkbfile-dev, libdconf-dev, libcanberra-dev, libhunspell-dev and libudev-dev

This is easy to fix: Just install the suggested packages using sudo apt-get install.

Now the setup actually compiles and installes successfully!

1.7.2 Start the virtual keyboard

Now I try to start Onboard with the command onboard. Don't expect it to work in the SSH session; it can only work if you are in a graphical environment (X server is running).

  File "/usr/local/lib/python3.4/dist-packages/Onboard/", line 38, in <module>
    from gi.repository import GLib
ImportError: No module named 'gi'

I tried and found out that I have to install two more packages (sudo apt-get install):


Now when try to start Onboard, the next error is:

ERROR Config: gsettings schema for org.onboard.keyboard is not installed

Apperently, Onboard's setup did not install the dconf config schema. The solution for this is described on reddit:

sudo cp data/org.onboard.gschema.xml /usr/share/glib-2.0/schemas/
sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

Finally it works!

1.7.3 Tipps for configuration

In Onboard's settings dialog, you can customize appearance and many other features.

If you use the keyboard in a kiosk application or something similar, there are some interesting configuration options2:

  1. In the general settings, I disabled the tray icon to prevent the enduser from opening settings and help windows.
  2. You can "lockdown" some features of Onboard, e.g. the settings dialog. This is done using (graphical) dconf-editor. Open the org.onboard.lockdown directory and disable what you don't want.

As I like reproducible configuration, I use dconf to dump and load Onboard's configuration:

# dump the settings
dconf dump /org/onboard/ > org.onboard.dconf-dump

# reset all settings to their defaults
dconf reset -f /org/onboard/

# load the settings
dconf load /org/onboard/ < org.onboard.dconf-dump

If you want to use the dconf tool from another tty (outside of the X session) or in an SSH session (?), prepend dbus-launch to the commands3.

1.8 Using xmonad in a restrictive touch user interface – part 2 [2017-09-18 Mon]   raspberrypi xmonad linux

As described earlier, we at Intensovet use a Raspberry Pi with a touch screen in our oxygen cage. As window manager (WM) I chose xmonad. I can not tell that it was easy to configure xmonad. There are many details to take care of and many cavets when trying to make different programs work well together.

I have never tried a different WM for this system. I think there are not so much alternatives to xmonad (I don't want to change WM source code). Maybe Openbox?

At this point I want to share some lessons learned when using xmonad for a very restrictive touch user interface.

1.8.1 Where to put the commands for start-up programs?

First, how to start X at all? You can start X with two commands: xinit or startx where startx is like a simplified version of xinit (man startx says it "is a front end to xinit").

There are multiple files related to X start-up:

  • ~/.xinitrc – the "run code" for X. It is read when you start X with startx=/=xinit.
  • ~/.xprofile – like a ~/.profile or ~/.bash_profile for X. But this file is only read by some display managers (i.e. the visual login screens)! For example, KDE and Gnome might execute the commands in ~/.xprofile but when you start a specific WM directly, the file will not be read at all.
  • xmonad's startupHook – this function will be called when xmonad starts. In this monadic function you can =spawn "~/.xmonad/"= to execute a script.

exec xmonad should be the last line in ~/.xinitrc to start the WM.

So which file to use for starting the UI software (e.g. the browser, the custom UI, the virtual keyboard, the system tray)?

~/.xprofile does not work as it is not read when we start a WM directly. Unless you have a line like [[ -f ~/.xprofile ]] && source ~/.xprofile in your ~/.xinitrc.

We could start UI software in ~/.xinitrc before we start the WM. Starting graphical programs before the WM is generally not a problem. We could also start UI software in the start-up script called by xmonad's startupHook.

However, ~/.xinitrc seems to be too early for some programs. For example a call to xinput to rotate the touch display seems to have no effect at this point. Therefore, I moved all UI software start-up to my script, including xinput, setxkbmap, and xset calls.

1.8.2 "Ignoring" windows like the virtual keyboard

The virtual keyboard and the system tray must be ignored by the WM, i.e. the WM should not manage these windows (no tiling, no automatic positioning, etc.).

In xmonad this is done in the manageHook with doIgnore.

But xmonad's behavior seems inconsistent and even non-deterministic at the first glance: Sometimes, ignored windows stay below tiled windows, sometimes they are always on top. Sometimes ignored windows disappear when opening certain dialogs (floating windows), sometimes they show up again when opening or closing other dialogs.

The reason for this seems to be the order in which windows are created. This determines the order in which xmonad's manageHook manages the windows.

Conclusion: Programs with windows that should be ignored must be started before all other programs! If this is guaranteed, my virtual keyboard and system tray work perfectly well and stable.

In practice it can still be a problem. My looks something like this:

trayer &
virtual-keyboard &
start-gui &

If, for example, trayer blocks for some reason a few microseconds too long during an I/O operation, the Linux kernel might give CPU time to start-gui which creates the main UI window before other, ignored windows. This would then result in the non-deterministic behavior described above.

1.8.3 Getting the virtual keyboard to work

Required was a virtual keyboard that can be toggled and that does not overlap with other windows. I already chose Onboard because it excels all other open source virtual keyboards I found in configuration options and design.

I'm not sure if ignoring the keyboard window is the only way to prevent it from getting the focus. Anyway, I have to ignore it and/or make it a dock (xmonad calls it struts). For example the status bar xmobar is a dock window and xmonad leaves this area free. The good thing is that I can toggle struts, i.e. hide or show docks. xmonad can even toggle only the buttom struts which would be the virtual keyboard.

Onboard has a option to make it a dock! It just don't work in version 1.4.1 under Raspbian (although it work on Arch). I already had a lot of trouble installing Onboard on Raspbian, see the earlier blog post.

The bug has already been documented and fixed but the fix seems to be not yet published:

I first tried to set the dock window properties manually which is pretty hacky and did not work properly (see notes below).

Then I found a work-around for using docks. It is a package called XMonad.Layout.Gaps and solved exactly my problem.

  1. Virtual keyboard as ignored window with toggleable gaps
    1. The virtual keyboard must be started as one of the first programs to behave correctly under xmonad.
    2. The virtual keyboard must be ignored (doIgnore) with a rule in xmonad's manageHook.
    3. xmonad's layoutHook must define a gap for the virtual keyboard at the bottom using the function gaps [(D, 160)] (D for "down").
    4. The virtual keyboard must be positioned in that gap. This can be done in Onboard's settings or with a rule in xmonad's manageHook.
    5. There must be a hotkey to toggle the gap. In my config it looks like this:
    -- ...
    , ("M-k", sendMessage $ ToggleGaps) -- toggle lower gap to show/hide the virtual keyboard
    -- ...
    1. There must be positioning rules for dialog windows. doCenterFloat might hide the virtual keyboard if it's visible.


    • When hidden, the virtual keyboard stays behind all other windows, especially behind the full-screen main UI window.
    • When showed, the full-screen area shrinks to leave space for the gap and the virtual keyboard is visible.

    Maybe this list is not fully complete. Please refer to the XMonad.Layout.Gaps package documentation on Hackage, it has good documentation.

    I can toggle the virtual keyboard from an external program with this command: xdotool key super+k (Provided that xmonad's mask key in ="M-k"= is the windows key aka super key.)

    Bonus: A advantage of this method is that the virtual keyboard is already running and shows up immediately.

  2. Trying to make a window a dock window

    This is not the preferred solution, just a note.

    Is there another way to define WM_STRUT and WM_WINOW_TYPE DOCK for window? Yes: xprop -set property-name value The exact properties I want to change are:

    $ xprop | grep -E 'DOCK|STRUT'
    _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 205, 0, 0, 0, 0, 0, 0, 0, 1919
    _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 205

    (copied from xprop output on my Arch computer)


    # sync -> block until onboard is started
    declare windowId=$(xdotool search --onlyvisible --limit 1 --sync --classname Onboard)
    xprop -id "$windowId" -format _NET_WM_WINDOW_TYPE 32a -set _NET_WM_WINDOW_TYPE _NET_WM_WINDOW_TYPE_DOCK
    xprop -id "$windowId" -format _NET_WM_STRUT 32c -set _NET_WM_STRUT '0, 0, 0, 205'
    xprop -id "$windowId" -format _NET_WM_STRUT_PARTIAL 32c -set _NET_WM_STRUT_PARTIAL '0, 0, 0, 160, 0, 0, 0, 0, 0, 0, 0, 300'
  3. A third method: starting and killing the virtual keyboard on demand

    This was the first way I tried: Starting and killing the virtual keyboard on demand. The WM had rules to tile the keyboard below the main window.

    Disadvantages are:

    • On a Raspberry Pi it takes a significant time to start or kill the keyboard process. As a consequence it happened that the user started the keyboard twice.
    • A tiled window is spawned above the current window so it replaced the main window and pushed the main window down to the virtual keyboard area. Special WM rules were necessary (keywords: swapDown and keepMaster). However both of these rules did not work reliable and well together with floating windows.
    • The tiling layout must include a place for the virtual keyboard. But it is better to have a layout that is independent of the virtual keyboard especially if the keyboard can be toggled.
    • A tiled window cannot be ignored at the same time so I had some focus problems.

1.9 Enable JavaScript syntax checking and more in Vim [2018-01-04 Thu]   vim

I'm starting to use JavaScript (JS) for scripting and mobile app programming. Of course I like to have a good syntax checker and linter. You can learn so much about good coding practices from great linters like hlint (Haskell) and shellcheck (Bash)!

I use Vim with the great asynchronous linter engine plugin ALE. This is how I managed to install the feature-rich ESLint as a linter in Vim.

  1. The Vim plugin ALE must be installed in Vim. From then, for almost all programming languages und file types you open in Vim, a great linter is enabled automatically – provided that the linter program is installed on your computer.
  2. Install ESLint (EcmaScript is like a specification of the JS language). On Arch Linux: sudo pacman -S eslint
  3. Initial configuration for the linter: eslint --init

    It will ask you a few questions. I chose the "standard" coding style.

  4. Test the linter: eslint /tmp/test.js

    It failed with the message ~Cannot find module 'eslint-config-standard'~.

  5. Install missing packages with npm globally: sudo npm install --global eslint-config-standard

    npm warned me that there are more packages missing which are dependenecies of the eslint-config-standard. (npm seems to not install dependencies at all.)

  6. Install required dependencies with npm in the same way you installed eslint-config-standard.
  7. Test again (hopefully with success).
  8. Test with Vim (vim test.js) by writing some "bad" lines of code e.g. declare but not use a variable.

Vim with ALE should now highlight erronous lines of code with a marker at the begin of the line, display errors (or warnings) in the current line at the bottom, and should have a list of problems in the location list (:llist, see also :help location-list).

Note: I installed ESLint with the system package manager Pacman and not with npm because I like the automatic and frequent updates of Arch Linux.

Author: Jakob Schöttl

Created: 2018-01-04 Thu 21:59

Emacs 25.3.1 (Org mode 8.2.10)