Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X
Design for the ideal text editor.

# Design for the ideal text editor

Last time I discussed my thoughts on the ideal text editor. I also mentioned that nothing quite fits the bill for me right now. Today, I want to discuss a possible design for an editor that I think allows for all the things that I look for and that is future proof.

I put a lot of thought into this lately - my frustration with Vim's shortcoming's in daily life and my experiences in writing one of the more successfull Vim plugins out there have given me some insights which I tried to distill in this design. I am currently exploring these ideas in code in Swiboe - my attempt at implementing the editor of by dreams. Contributions are welcome.

## The best editor is no editor at all

A simple idea got me started: everything is a plugin and a plugin has infinite power. In Swiboe, these are all plugins: the buffer management (editing, creating, loading), the fuzzy searcher, the git integration, the GUI program, the cursor handling in the gui, the plugin loading - every functionality. Swiboe is really just an operator on a switchboard:

That is where its name is coming from: Switch Board Editor.

But how does that work? Let's design two basic plugins that know how to open compressed files into buffers, one that can read Gzip, one that can read Bzip.

Swiboe listens on a socket and waits for plugins to connect. Once a plugin connects, it registers remote procedure calls (RPCs) which have a name and a priority.

# In gzip.py
plugin = connect_to_swiboe("/var/run/swiboe.socket")
plugin.register_rpc("buffer.open:gzip", priority = 800, buffer_open_gzip)

# In bzip.py
plugin = connect_to_swiboe("/var/run/swiboe.socket")
plugin.register_rpc("buffer.open:bzip", priority = 799, buffer_open_bzip)


We'll define the buffer_open_gzip function later - buffer_open_bzip follows by analogy.

Some other client (for example the GUI) now wants to open a file:

gui = connect_to_swiboe("/var/run/swiboe.socket")
gui.call_rpc("buffer.open", args = {
"uri": "file:///tmp/somefile.txt.gz"
})


The args will be converted to JSON and handed to the called function.

The name of the called RPC defines what will get called: Swiboe will find all registered RPCs that have the same prefix, so in our case both buffer.open:gzip and buffer_open:bzip match. The name of the RPCs are really just a convention: dot.separated.namespaces:name_of_implementing_plugin. This allows callers to call to a very specific function:

# I know that somefile.txt.bz is really a gzip file, so call the gzip
# handler directly. Signal it through 'i_know_what_i_am_doing' that we are
# aware that the extension does not match.
gui.call_rpc("buffer.open:gzip", args = {
"uri": "file:///tmp/somefile.txt.bz",
"i_know_what_i_am_doing": True,
})


It also allows to call a very broad range of functions:

# Call all buffer functions that start with o - that is not very useful
# probably.
gui.call_rpc("buffer.o", args = {
"uri": "file:///tmp/somefile.txt.bz",
})


After the functions are determined, Swiboe sorts them by priority and tries them one after the other. The functions work like event handlers in JavaScript or GUIs - they can choose to handle the call and return a value, or they can let the call through to the next. For example, the gzip handler could look like this:

import gzip

def buffer_open_gzip(rpc_context, uri, i_know_what_i_am_doing = False):
if not uri.endswith(".gz") and not i_know_what_i_am_doing:
# Let's inform Swiboe that we do not know what to do with this
# request.
return rpc_context.finish(NOT_HANDLED)
file_path = uri[7:]  # Removes file://

# Call an RPC to create a new buffer.
buffer_create_rpc = rpc_context.call_rpc("buffer.create", {
"content": content,
"uri": uri,
})

# Wait for it to succeed or fail and return this value to our caller.
return rpc_context.finish(buffer_create_rpc.wait())


### Pro: Events are nothing special

This design can also express something like Vim's autocommands - which are just callbacks, really.

A callback is just an ordinary RPC. For example, when the buffer plugin creates a new buffer, it calls on.buffer.created, but does not wait for this call to finish. Everybody interested in buffer creation can just register a matching RPC - with a I_DO_NOT_CARE priority. This signals Swiboe that all these functions can be called in parallel.

If that is not desired, a priority can be specified to decide when to run - if two plugins conflict they can fix their priority values to make things work.

### Pro: Extensibility

A plugin is all-mighty in this design. Want to add functionality to buffer.new:core? Just override it with something that has a higher priority and do something else in it. Want to filter out your .gitignore files from fuzzy find? Just write a fuzzy_find.files:git that is called before fuzzy_find:core, calls it directly and filters its results before passing them on. Want to use tab key for every kind of smart content expansion? No problem, just define the order of functions to call and Swiboe will handle it for you.

Everything is a plugin and therefore everything can be changed by other plugins.

### Pro: Simplicity

There is only one concept to understand in Swiboe: this layered RPC system. Everything else is expressed through it.

There is a little more to the story - for example RPCs can also stream results. For example the fuzzy files finder uses this to get partial results to the GUI as fast as possible. But the core philosophy is just this one concept.

## The big concern: Performance

Swiboe is an RPC system using Unix domain sockets right now. A RPC is more overhead than a simple function call. My benchmark is creating a buffer and immediately deleting it - these are 4 round trips:

client (create request) -> Swiboe
Swiboe (create request) -> buffer plugin
buffer plugin (create response) -> Swiboe
Swiboe (create response) -> client

client (delete request) -> Swiboe
Swiboe (delete request) -> buffer plugin
buffer plugin (delete response) -> Swiboe
Swiboe (delete response) -> client


Quick tangent. This displays well why I choose Swiboe as name. It connects plugins until they found the right partner to talk to, enabling communication with discretion and speed.

This flow takes ~290μs on my system - roughly 500 times slower as doing the same with python function calls. However, I did not try to speed it up in any way yet - both the protocol and the encoding are naive right now.

Also, I believe the RPCs are mainly gluing functionality together. Most computation will be run in the plugins, in separate processes, in parallel. I believe that sufficient performance for a fluent and responsive experience can be reached.

And of course, performance is temporary, design is permanent. So let's start with getting this right first.

## Disclaimer

There is a lot of dreaming in this post. There is no python client yet for Swiboe. (Update: no longer true). This design is still subject to change and not completely implemented in Swiboe. There is no gzip or bzip plugin.

Also, the exact design and protocol of the layered RPC system is not written down anywhere yet. (Update: no longer true)

Swiboe is open for contributions! If you want to design a cool text editor with me, feel free to reach out.

The ideal text editor

# The Ideal Text Editor

I am a Vim user and have been for more than 15 years now - with short stints to other editors from time to time. I also wrote a popular plugin for Vim - so I understand it's internals better than most. Still, I feel that Vim is showing it's age - and it is hardly the ideal editor.

I also used TextMate for a while. I tried Sublime for a week or so and am trying Atom right now - I am writing this post in it. There is also a new kid on the block (sorta) with Brackets which seems to be very focused on web design. All of them are impressive editors, but all fall short in some ways for me. Here are my musings about the ideal text editor.

Here are the most important properties of an ideal text editor for me, in sorted order.

## Free

This includes free as in free-beer and free as in free-speech. I used TextMate for about a year and got plenty annoyed that I was unable to fix bugs since it was closed sourced. The developer loosing interest in the project and basically walking away also kinda sealed it's death. Imagine spending time learning a powertool, just to see it abandoned and left to bit rotting - and there is nothing you can do. TextMate seems to be back after some years now - but I would never set on a closed source editor again.

Being monetary free is important to get people involved. An editor that is just 100% free is less risk to try out than one that you might need to shell out to use. ## Responsive A text editor must react as fast as I can think. It is not acceptable to wait for simple tasks like switching a tab or running a command. I must never be interrupted while the editor needs to finish some computation - like auto completion results or a make command. ## Modal Vim's best feature is its UI. Modal editing opens up so much more abilities to control functionality. There are alternatives that are really good too - for example a fuzzy selector over all available commands. But even when this feature is available: with normal mode you have the full keyboard available for shortcuts. It also clearly defines cutting points for what undo/redo/repeat does. And Vim's editing language (e.g. daw - delete a word) is intuitive, precise and quick. I will never ever consider an editor that does not have strong modal support build in. It is fine if it can be turned off of course - as long as it is not implemented as an afterthought. ## Easy to extend This is a biggy. It should not matter what my main language is - as long as it is turing complete I should be able to add new features to my editor. These features should be arbitrarily powerful and seemlessly integrated, i.e. they should be indistinguishible from build in commands. Atom and Sublime are good examples of editors that get this second part pretty right. What they both get wrong is the choice of language: Atom is JavaScript and Sublime is Python. If you do not speak the language of your editor out, you are demoted to User status. Vim does a little better: It has support for Python, Ruby, Lua, Lisp ... you name it. Unfortunately all of these integration are second class: You cannot write a full plugin in either of these languages - you need a fair amount of VimScript to glue it together. And after 7 years of UltiSnips I can confirm that VimScript is no fun to write. So a good editor should support as many languages as possible and all of them should be first class citizens. ## Cross platform I never work on Windows, but I work on Mac OS and on Linux a ton. I need an editor that runs on both. I think cross platform is also really important to atract people - so Windows support is important too. ## Console/Remote editing I do not enjoy working in console Vim. I like my Editor to support me with a rich GUI and I enjoy that my editor saves whenever I switch to the shell. Howevr, occasionally I need to remote edit files on a server - I use console Vim there. That is a really important feature for me. But even better would be if I could remote edit the files: having the nice gui on my laptop talk (securely) to the editor core running on the server would be great. A console GUI is still important, since many people still like to work in the console using tmux to never switch the program they are using. That is cool, and I think an editor should support it. ## Beautiful There, I said it. I stare at my text editor 8 hours per day - it should better look nice. ## Collaborative I love working on documents with others in Google Docs. Every collaborater can edit the document live and sees the cursor and the edit actions of others at the same time. Imagine how cool pairing would be in an editor that supports that nicely and natively. I know that there are plugins/hacks for existing editors - but it needs to be there out of the box and easy to setup for people to actually pick it up. ## Conclusion These are the things I ask from an editor. I might have forgotten some stuff, but these are the important things. I will continue this series of blog posts with looks at the editors that are currently out and how they fare. Also I want to present a design that I think works to implement an editor close to my heart. Technology revamp on the blog # Technology revamp The technology on the blog bit rotted quite a bit lately. And of course it has not seen any update or new content in years, but that is an entirely different story. To make sure the content still looks good in modern browsers, I revamped some of the tech behind the site a bit now. For starters, I removed Cufon - a library to render fancy texts client side. I did not use it a lot and it made some text on the page look blurred on my phone. I also switched from pre-rendered images for math display to using MathJax. MathJax is not fully convincing - pretty heavyweight in terms of size, tons of features I do not need and rather slow rendering. But it works well on my phone and desktop and the math looks better than the images did, so I'll stick with it for now. The alternative I looked at was KaTeX. It is way faster than MathJax, but unfortunately does not support the TeX align environment, which is a show stopper for me. Text Layouting Status Report # Text Layouting Status Report So, it took me two weeks to finally get around to a status report, and Peter even had to request it forcefully. But I have not been idle in this time. Let's see. ## Pango? Harfbuzz? SDL_TTF! I spent quite some time investigating Pango and Harfbuzz, I blogged about it in my previous post. I knew back then already that Pango was not ideal and that even Wesnoth was not using Pango for their fancy help rendering (they use if for some other types of text though). I then investigated Harfbuzz further and though it seems like it will one day become what we need, it is not there. In fact, it does not even have a stable version currently released. It can handle international text pretty well, but it does not help in the left-to-right, top-to-bottom rendering of text, nor with the breaking of text into paragraphs. So we are back to square one: The old-and-trusted SDL_TTF. I designed my code around SDL as graphics engine, the text rendering is kinda plugged in and uses SDL_TTF, but it should be easy to replace this with any other text engine when one establishes itself as the one - be it Pango or Harfbuzz or anything else in the future. ## What works? I just finished my initial implementation of the engine - It has all the feature that Venatrix and myself have marked as desirable. Some of the feature (like tables) are rather rudimentary, but I think it should be enough for us. The whole engine is currently a stand alone library - in the next step, I will plug it into the Widelands code. But let's move on to pretty pictures. Here are some examples. <rt> <sub padding=5 background=000000> <sub width=350 background=win_bg.png padding=2> <p align=center> <font size=30 color=F2DF91 underline=true>This is a heading</font> </p> <vspace gap=2> <sub margin=5 padding=5 background="ffffff" float=left> <p><img src="wl-ico-128.png"></p> <p align=center> <font size=10>This is the subtext for the image. Kinda like a caption.</font> </p> </sub> <p indent=5> <font color=FEFE00 size=14> Lorem ipsum dolor sit amet, consetetur sadipscing elitr, <font italic=true ref="hyperlink">sed diam nonumy</font> eirmod tempor <font underline=1 ref="somereference">invidunt ut labore et</font> dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo <font bold=true>duo dolores et ea rebum</font>. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. </font> </p> </sub> </sub> </rt>  This code renders to the following picture: This already shows off some of the features: changing fonts inside a paragraph, sub layouts that can float inside the text. Margins and paddings for some elements (though this is not as fully featured as in HTML) and of course images. It also contains a ref attribute for a font tag which makes this part of the text clickable. This will make hyperlinks in the help possible. Tables are kinda possible as well: <rt> <sub width=10></sub><sub width=240> <p> <sub width=80 background=638c57><p>Hello</p></sub><space><sub width=80 background=42deb7><p>Nice</p></sub><space><sub width=80 background=43f447><p>World</p></sub> <br> <sub width=80 background=404542 valign=center><p align=center>Upsy</p></sub><space><sub width=80 background=e21038><p>And more</p></sub><space><sub width=80 background=0c7e8f valign=center><p>Thats all</p></sub> <br> </p> </sub> </rt>  Each row is a set of three fixed width cells separated by a <space> tag which expands as needed (in this case not at all). The lines are separated by a linebreak tag <br>. This kinda results in a table with fixed column count and width. Good enough for Widelands I hope: Bullet point lists are possible as well: <rt> <p><font size=20 underline=1>A bullet list</font></p> <sub padding=10 width=490> <p> <sub valign=top><p><space fill=" "><img src=bullet.png></p></sub><sub width=450> <p> Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor. </p> </sub> <sub valign=top><p><space fill=" "><img src=bullet.png></p></sub><sub width=450> <p> Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. </p> </sub> <sub valign=top><p><space fill=" "><img src=bullet.png></p></sub><sub width=450> <p> Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor. </p> </sub> </p> </sub> </rt>  This uses a lot of sub layouts to achieve the desired result. It does not read very nice, but which markup does? I plan to hide this all in some Lua functions, just as we are already doing for scenarios to make it all nice to use as well. This wall of text renders as ## What's next? The next step is to integrate this layout engine into Widelands. Caching will be really important here, because rendering with SDL_TTF is very slow. I feel that the technical challenges of getting this engine on board will be surmountable, the one thing I am really not looking forward to is changing all rich texts that we already have to work with the new engine. Especially the hard coded texts inside the source, the files in txts/ and the early campaigns (barbarians and empire) will be a lot of tedious work. I hope some people hop on board to help me out with that. Soo, expect a branch with this engine soonish on launchpad. Widelands Marathon Begins # My personal Widelands Marathon So, I finally handed in my PhD thesis. That does not mean that everything is said and done, there is still an oral examination, a 30 minutes talk and some demonstration stuff to be done. But it means that I am now officially out of my previous job. That means, before I will start at Google in September, I have around three months to use for whatever I see fit (okay, okay, I also need to find a flat, move, prepare for the oral examination, prepare the demo, and organize a huge celebration. And I have some other obligations remaining). I want to use a lot of time for Widelands in these three months. To keep me on track and motivated, I decided to keep a development diary on this blog. ## First Project: Make the Widelands Help awesome Venatrix, Astuur and others have begun the immense project to write a help for Widelands. I have provided a minimal framework to give buildings a help window via a Lua script in the building's directory. This is already immensely useful and significantly better than no help at all, but it feels rather limited: Widelands text handling and layouting capabilities are rather limited and there is currently no way to document other stuff than buildings. My first project for now is to improve this situation. ## Text layouting Text layouting is a difficult problem, especially when we also consider internationalization (just think chinese for example). I started out by learning the various libraries that are around for this problem. There are two contenders, the fist is Pango, the second harfbuzz. ### Pango Pango is the text layouting engine from the Gnome desktop environment. And it is well suited for this task. Using Cairo for rendering and its own (limited) markup language it is next to trivial to render a UTF-8 string with various languages to a rectangular grid. This is not enough for what I want though: Just think about an image inside a paragraph. Text should flow around it, therefore it needs to be broken into a non rectangular shape. This is not easy with Pango: It does provide a low level API to reflow text independently, but it is awkward and one looses at lot of what Pango is good at (like transparent handling of right-to-left text blocks). Also, Pango does not allow to choose the TTF font file to use for rendering directly, instead relying on fontconfig to find a suitable system font. In Widelands, we would prefer to feed in our font files ourselves - so we can be sure that it looks the same, no matter what OS is used. Pango is stable and used in a lot of products like Gnome. It is also what Wesnoth uses for most of its rendering needs. But for the (cool) Wesnoth help, it is in fact not used, likely because of the reflow problem I mentioned earlier. Documentation for Pango is available in the form of a Doxygen output. This is a nice reference, but hardly more useful than the source code itself. There is also no easy tutorial that goes beyond the PangoLayout example that can only render in rectangles. Especially, there is no example how to add custom markup tags or how to do low(er) level layouting. The best I found is an old mailing list post that explains the steps needed to layout text oneself. I was able to stitch those hints together to a binary that does just that. But it is really awkward and it does not offer a lot of the functionality that the PangoLayout wrapper offers. I kinda feel this is a dead-end for now. ### Harfbuzz Harfbuzz is a slightly lower level API that is in fact used by Pango. It allows to load TTF directly and offers more control over layouting. For rendering it also uses Cairo. Problem here is that there is no stable version - according to the homepage, the API might change till 1.0, the current version is 0.6. And there is no docu. Nada! Luckily, there is a github user that provided an example that is very close to what I want to achieve and that shows off a lot of the features of harfbuzz. The API changes were already felt in this one year old example: some of the functions take other arguments now than they did back then, but it was really easy to figure out with the harfbuzz source code nearby. When run, the program shows the following window: I am yet unaware if harfbuzz is also able to break text according to grammatic rules, but this looks promising. Alright, so far for my two hours of Widelands for today. Fourth episode of UltiSnips Screencast # UltiSnips Screencast Episode 4 I got around doing the final episode of my little screencast series on UltiSnips. This time I talk about Python interpolation and give an example of a snippet that really makes my life easier. I always wanted to have a few screencasts showing off the main features of UltiSnips but nobody was willing to take the time and effort to produce them. Now that I've done it myself I can understand why: It takes a lot of time. From start to finish - planing, recording, cutting, uploading and promoting one screencast of roughly ten minutes takes approximately six to eight hours. It was a lot of fun doing the casts though and I learned a lot. I am also reasonably pleased with the final results. If someone suggest a really good topic for a fifth screencast, I will consider making one. But I feel that UltiSnips' main features are well covered now. Thanks for sticking with me throughout the series! Third episode of UltiSnips Screencast # UltiSnips 2.0 and Screencast Episode 3 I just release UltiSnips 2.0 together with a short screencast to run you through the new features. 2.0 is a killer-feature release for me: Having normal mode editing and VISUAL support adds a lot of value to UltiSnips for me. UltiSnips now has all the features I initially expected from a snippet plugin when I started out writing it. It was not an easy road getting here but I am proud what we have achieved. I consider it now mostly feature complete - I will not object to good ideas for new features that enhance the user experience but we will try as best as we can to avoid feature creep. UltiSnips wants to be only one thing - the ultimate solution for snippets in Vim. The Statistical View on Least Squares # Least Squares and Statistics Last time I talked about the beautiful linear Algebra interpretation of Least Squares which adds a wonderful geometric interpretation to the analytical footwork we had to do before. This time I will borrow from a video I saw on Khan Academy a long time ago. I connects some of the elemental principles of statistics with regression. The basic idea is similar to the analytical approach. But this time, we will only try to fit a line toMx$/$ypairs. So, we have a model of the form \begin{equation*}y(x) = m x + c.\end{equation*} The squared errors between model and data is then \begin{align*}S := \sum_i \epsilon_i^2 &= \sum_i (m x_i + c - y_i)^2 \\ &= \sum_i m^2 x_i^2 + 2 c m x_i + c^2 - 2 m x_i y_i - 2 c y_i + y_i^2\end{align*} Of course, we search for the global minima of this solution with respect to the parametersm$and$c. So let's find the derivations: \begin{align*}0 \stackrel{!}{=} \frac{\partial S}{\partial m} &= \sum_i 2 m x_i^2 + 2 c x_i - 2 x_i y_i \\ 0 \stackrel{!}{=} \frac{\partial S}{\partial c} &= \sum_i 2 m x_i + 2 c - 2 y_i\end{align*} We can conveniently drop the 2 that appears in front of all terms. We will now rewrite these equations by using the definition of the sample mean: \begin{equation*}\overline{x} = \frac{\sum_i x_i}{M}\end{equation*} This gives: \begin{align*}0 \stackrel{!}{=} m M \overline{x^2} + M c \overline{x} - M \overline{x y} \\ 0 \stackrel{!}{=} m M \overline{x} + M c - M \overline{y}\end{align*} Let's loose theM$s and solve for$m$and$c. \begin{align*}m &= \frac{\overline{x}\,\overline{y}- \overline{x y}}{\overline{x}^2 - \overline{x^2}} \\ c &= \overline{y} - m \overline{x}\end{align*} If you look closely at the term for the slopem$you see that this is actually just the covariance of$x$and$y$divided by the variance of$x$. I find this very intriguing. Second episode of UltiSnips Screencast # UltiSnips Screencast Episode 2 Second screencast is done and ready! If you have not yet seen the first, look over here. This was done under the maxim Done is better than perfect. I had more advanced explanations planed, but the screencast turned out to be longer than expected. I therefore opted for a complete overview over the most common features of UltiSnips and will explain some cooler stuff in this blog post. So here is the video. You can find some snippets with their explanation below. ## Elements inside of default text Placeholders can contain other UltiSnips elements. This is totally cool and very useful. For example, the following snippet is defined for the html file type and ships with UltiSnips: snippet a <a href="1"{2: class="{3:link}"}> 0 </a> endsnippet  It allows to either delete the complete tabstop 2 with one keystroke. Or you can jump to tabstop 3 and replace the CSS class name. Another example: snippet date {2:{1:date +%d}.date +%m}.date +%Y endsnippet  This snippet will enter the current date in the format that is used in Germany: dd.mm.yyyy. Jumping forward will allow you to either overwrite the day or the day and the month. I use this in my todo files to enter due dates. ## Complete Scripts in Shell Interpolation Shell interpolation is as powerful as the shell itself. Here is a silly example that is basically a complete Perl script: snippet random #!/usr/bin/perl use LWP::Simple qw(get); my page = get "http://www.random.org/integers/?num=1&min=1&max=100&col=1&base=10&format=plain&rnd=new"; print page endsnippet  This snippet will insert a truly random number between 1 and 100 fetched from random.org. Useful? Maybe not, but a good example. ## Transformations are more powerful than you might think This transformation shows the transformation option g which means global replace. It will uppercase every word in the first tabstop while mirroring its content. snippet title "Titelize in the Transformation" {1:a text} {1/\w+\s*/\u0/g} endsnippet  In the replacement part of this transformation, the u means "uppercase the next character" and the 0 matches everything found. The complete transformation basically says: find a word \w+ and any number of whitespace \s* and replace them through what you found, but uppercase one char. The g at the end makes sure that not only the first but all words are uppercased. ### Conditional replacements One feature that I didn't mention in the screencast are conditional replacements. When you capture a group in the search part of a replacement, you can check if it was matched in the replacement like so: (?<number>:yes text:no text). yes text will be inserted if the group was matched, otherwise no text will be inserted. A quick example: snippet cond {1:some_text}{1/(o)|(t)|..*/(?1:ne)(?2:wo)/} endsnippet  The transformation will match a o at the beginning into group 1 or a t at the beginning in group 2. The rest of the search string just matches everything of the first tabstop. The replacement will either be ne when a o was matched, wo when a t was matched or an empty string. That means that you can just type a t to quickly get two as the complete content of the snippet or a o to get one. If you type anything else, you only get the content of the place holder, i.e. the verbatim of what you typed. ## Inword triggers The snippet option 'i' stands for inword trigger. Let's say for some coding project, I often want to get variables that end on izer: maperizer, vectorizer... I want to define a snippet with ri which should expand to izer. Triggers are always matched to full words though - except for when you use the i option for your snippet: snippet ri "rizer" i rizer endsnippet  This does what I want: maperi<tab> -> maperizer. ## Regular Expression triggers Regular expression triggers can be used with the r option to a snippet. Note that you have to add delimiters around your trigger when using regular expression triggers. I use the following snippet because I can never remember on which exact trigger I set my$\textrm{\LaTeX{}}$chapter snippet: snippet "chap?t?e?r?" "Latex chapter" rb \section{chapter} 0 \end{chapter} endsnippet  This will expand on either cha, chap, chapt, chapte or chapter. Regular Expression triggers are even more powerful because you can get access the to match object inside your python interpolation blocks. More on that in the next episode. Regular expression triggers also allow to define triggers with special characters, whitespace or multi word triggers. snippet " this is a trigger" "Multiword & Whitespace" r Hello World endsnippet  # Conclusion The features we discussed so far are enough to make crazy snippets and will suffice for most uses. If you ever feel lost or forget how to use one of the features, take a look into UltiSnips help document, either via :help UltiSnips  or here online. Next time we will discuss python interpolation which brings even more power to snippets. With it, some of the features we discussed so far will become easier to read with and others will only then become possible. With python interpolation there is basically nothing that a snippet can't do. As always, leave comments and let me know what you think about the screencast and the tips. Also let me know what you are interested in and what you would like to see in future screencasts. I have no more topics for a fourth screencast, so if you want one, let me know what you want to see in it. Move window done right # Move window to the rescue Overlapping windows are a bad invention. Frankly, the one UI that works are virtual desktops with non overlapping windows (e.g. window managers). Given, the world becomes sane slowly with iOS leading the way: every application is full screen there. On Mac OS X, the situation is dire: windows just open wherever they want to. I wrote a python script a while ago that can be called quickly from Quicksilver or LaunchBar which took a simple syntax to describe where you want your window and moved it there. Problem: it was rather slow. It needed to run and parse a command line tool to get number of screens and resolutions and it had to ask for the frontmost application via AppleScript. I got fed up with that yesterday and made it fast. Getting the frontmost application and the number of screens and their resolution is now done via the Carbon Framework in a C Extension. You can find the source code on GitHub, download from there and use pip to install: https://github.com/SirVer/move_window ## Usage You want to call this from LaunchBar or Quicksilver, so install/make a proper AppleScript (I ship one in contrib). The tool takes the following syntax: move_window <screen_id><nr of x parts><x span><nr of y parts><y span>  Some examples move_window 0 # Disp 0, full Screen move_window 02 # Disp 0, left half of screen move_window 030 # Disp 0, left third of screen move_window 031-2 # Disp 0, rightmost two thirds of screen move_window 12121 # Disp 1, bottom right quarter of screen  Feedback and pull request are very welcome! First episode of UltiSnips Screencast # UltiSnips Screencast Episode 1 I finally got the technicalities sorted out, some inspiration and the time to make a first screencast about UltiSnips. It is not so much about the specifics in UltiSnips but rather an overview what snippets are and a demo reel of some of UltiSnips features. Let me know in the comments what you would like to see in future episodes! Update: There is now a second screencast. The Linear Algebra View on Least Squares # A Linear Algebra View on Least Squares Last time, we introduce the least squares problem and took a direct approach to solving it. Basically we just minimized the$y$-distance of a model to the data by varying the parameters of the model. Today, we find a completely different, but very neat interpretation. Suppose we have the following problem: There is a set of linear equations without a solution, e.q. a matrix$\mat{A}$and a vector$\vec{b}$so that no vector$\vec{x}$exists that would solve the equation. \begin{equation*}\mat{A} \vec{x} = \vec{b}.\end{equation*} Bummer. What does that actually mean though? If we use every possible value of$\vec{x}$in this equation, we get essentially all linear combinations of the column vectors of$A$. That is a span of vectors. That is a subspace. So,$\vec{b}$is not in our subspace, otherwise we would find an$\vec{x}$that would solve our linear equation. Here is a visualization in 3D when A is a two dimensional matrix: The column space of the matrix is a plane and$b$is not in the plane. A natural question now is: what is the vector in the column space of$\mat{A}$that is the best approximation to$b$. But what is a good approximation? Well, how about the Euclidian distance between the endpoints of the vectors. If we choose this criteria, there is a simple solution: the projection of$\vec{b}$to$\mat{A}$will give the best approximation. Here is another image: We have decomposed$\vec{b}$into its best approximation in$\mat{A}$which we call$\vec{b_\parallel}$and a component that is orthogonal to it called$\vec{b_}\perp$. At the end of the day, we are interested in a best approximated solution to our original equation, so we are not really interested in finding$\vec{b}_\parallel$, but rather an$\vec{x^*}$so that \begin{equation*}\mat{A} \vec{x}^* = \vec{b}_\parallel\end{equation*} Lets look for an equation for this$\vec{x}^*$. We will start out by using that the two components of$\vec{b}$are perpendicular to each other. And we will also express$\vec{b}_\perpthrough vector addition. \begin{align*}0 &= \vec{b}_\parallel ^T \vec{b}_\perp \\ &= (\mat{A} \vec{x}^*)^T \vec{b}_\perp \\ &= (\mat{A} \vec{x}^*)^T (\vec{b} - \mat{A} \vec{x}^*) \\ &= \vec{x}^{* T} \mat{A}^T (\vec{b} - \mat{A} \vec{x}^*) \\ &= \vec{x}^{* T} ( \mat{A}^T \vec{b} - \mat{A}^T \vec{A} \vec{x}^*)\end{align*} Since\vec{x}^*$can't be zero, the term in parenthesis must be. This directly yields the least squares formula again: \begin{equation*}\vec{x}^* = (\mat{A}^T \mat{A})^{-1} \mat{A}^T \vec{b}\end{equation*} ## Conclusion We did the exact same thing as in the last post, but this time we took another approach and quite a different world view on the problem. The least squares solution came up very naturally here and with a very simple geometric interpretation (at least in the 3d case, the approach is also valid for other dimensions though). The last iteration of this series will take a look at least squares in statistical models. A direct look on least squares # Least squares Here we go again. After a long time of travelling and illness something new on this blog. Today, I start a new mini series that takes a look at Least Squares in various ways. I want to show how least squares arises naturally in various areas - of course this will look at little similar all the time because it stays the same principle; but the basic approach depends on the context. Today we start with a simple example and the method I'll call the direct approach. # The direct method Suppose we have some kind of measurement process that measures every second and we know that the system we measure follows a model of third order, that is the values we expect are \begin{equation*}m(t) = p_1 t^2 + p_2 t + p_3.\end{equation*} But obviously, our measurement process is in some way noisy. Our aim is now to find good values for$p_1, p_2$and$p_3$. But what is good? Well, why not start by minimizing the distance between our model prediction and the measurement values? In this plot we see our measurements as blue dots and we see an awful model fit as red line. And we see various$\epsilon$bars. Those are the errors we want to minimize, the model prediction at a point$t_i$: minus the value that we measured at this point$v_i: \begin{equation*}\epsilon_i = m(t_i) - v_{i} = p_0 t_i^2 + p_1 t_i + p_3 - v_i = \begin{pmatrix} t_i^2 & t_i & 1 \end{pmatrix} \begin{pmatrix} p_1 \\ p_2 \\ p_3 \end{pmatrix} - v_i\end{equation*} It seems like a bit of a stretch to write this simple equation in a matrix notation there in the last step. But it will benefit us in a moment. We do not want to minimize the straight sum of those because positive and negative values might zero out. The absolute value is also not so easy because our error function is then non-smooth... Let's summarize the sum of squares of the individual errors: \begin{equation*}S := \sum_{i=1}^5 \epsilon_i^2\end{equation*} Minimization is best when we have a quadratic error function because there is only a single global minimum which can be found by setting the gradient to zero. The notation of this minimization becomes a bit tedious, that's why we go back to the matrix notation we used earlier and realize that we can stack all measurements we have into one matrix. Working with vectors will make the derivatives easier to do: \begin{align*}\vec{\epsilon} &= \begin{pmatrix} m(t_1) - v_1 \\ \vdots \\ m(t_5) - v_5 \end{pmatrix} \\ &= \begin{pmatrix} p_1 t_1^2 + p_2 t_1 + p_3 - v_1 \\ \vdots \\ p_1 t_5 ^2 + p_2 t_5 + p_3 - v_5 \end{pmatrix} \\ &= \underbrace{\begin{pmatrix} t_1^2 & t_1 & 1 \\ \vdots \\ t_5 ^2 & t_5 & 1 \end{pmatrix}}_{:= \mat{M}} \underbrace{\begin{pmatrix} p_1 \\ p_2 \\ p_3 \end{pmatrix}}_{:= \vec{p}} - \underbrace{\begin{pmatrix} v_1 \\ \vdots \\ v_5 \end{pmatrix}}_{:= \vec{v}}\end{align*} Our error functionSthen becomes \begin{align*}S & = \vec{\epsilon}^T \vec{\epsilon} \\ &= (\mat{M} \vec{p} - \vec{v})^T (\mat{M} \vec{p} - \vec{v}) \\ &= \vec{p}^T \mat{M}^T \mat{M} \vec{p} - \vec{p}^T \mat{M}^T \vec{v} - \vec{v}^T \mat{M} \vec{p} + \vec{v}^T \vec{v}\end{align*} Finding the gradient of S with respect to the parameter vector\vec{p}$is now easy. We also immediately set this equal to the zero vector to find the minimum of this function: \begin{equation*}\nabla S = 2 \mat{M}^T \mat{M} \vec{p} - \mat{M}^T \vec{v} - \mat{M}^T \vec{v} \stackrel{!}{=} \vec{0}\end{equation*} And so we find the parameters that minimizes the error to be \begin{equation*}\vec{p} = (\mat{M}^T \mat{M})^{-1} \vec{M}^T \vec{v}\end{equation*} Using this with the above example we get the following best fit # Conclusion I call this the direct approach because we directly set out to minimize the quantity and the least square formula pops out. There are other goals one can set out to achieve which leads to the same formula which I will show in some of the next posts. Hopefully it will not take as long again till I find some time to post again. The bridge between Lagrange and Bezier interpolation # Comparing Lagrange and Bezier interpolation Let's continue our discoveries in Chapter 7 of the Book by discussing my solution to 7.P1. We have talked the de-Casteljau algorithm before. It is an expensive but numerically stable way to calculate the points on a Bézier curve given it's control Polgon. Just to remember, this is how it is calculated: Given the points$\vec{b}_0 ... \vec{b}_n \in \mathbb{R}^m$,$t \in \mathbb{R}$. Set \begin{eqnarray*}\vec{b}_i^0(t) & := & \vec{b_i} \\ \vec{b}_i^r(t) & := & (1-t) \vec{b}_i^{r-1}(t) + t\,\vec{b}_{i+1}^{r-1}(t)\end{eqnarray*} Then$\vec{b}_0^n(t)$is the point with the parameter$t$on the corresponding Beziér curve. Another common approach to interpolation is to use Polynoms of degree$n$. We than also need some$t_i \in \mathbb{R}$that corresponds to the given$\vec{b}_i$, if they aren't given we can just set them so that they are equally distributed betwenn$[0,1]$. Aitken's Algorithm is than defined by Given the points$\vec{b}_0 ... \vec{b}_n \in \mathbb{R}^m$, with corresponding$t_i \in \mathbb{R}^n$and the position of the interpolation$t \in \mathbb{R}$. Set \begin{eqnarray*}\vec{b}_i^0(t) & := & \vec{b_i} \\ \vec{b}_i^r(t) & := & \frac{t_{i+r} - t}{t_{i+r} - t_i} \vec{b}_i^{r-1} (t)+ \frac{t - t_i}{t_{i+r} - t_i}\,\vec{b}_{i+1}^{r-1}(t)\end{eqnarray*} Then$\vec{b}_0^n(t)$is the point with the parameter$t$on the corresponding interpolating Polynom. The geometric interpretation is the following: We start out with point 0 and 1 and interpolate linearly between them, than we take 1 and 2 and so on. In the next step, we linearly interpolate between the linear interpolations of the last round by blending the one into the other. The degree of the interpolation polynom increses in each step by one. The differences between de-Casteljau and Aitken's algorithm in each step are quite simple: The first one is a mapping from$[0,1] \to \mathbb{R}^m$while the second one is mapping from$[t_i, t_{i+r}] \to \mathbb{R}^m$. We can provide a straight forward combination of those two algorithms by mapping from the interval$[ 0\alpha + (1-\alpha) t_i, 1 \alpha + (1-\alpha) t_{i+r} ]$with an$\alpha \in \mathbb{R}_+$, that is, we linearly interpolate between the two intervals. Let's define a quick helper function: \begin{equation*}W_i^r(t) := \frac{\alpha + (1-\alpha) t_{i+r} - t}{\alpha + (1 - \alpha) (t_{i+r} - t_i)}.\end{equation*} Using this, the generalized algorithm looks like this Given the points$\vec{b}_0 ... \vec{b}_n \in \mathbb{R}^m$, with corresponding$t_i \in \mathbb{R}^n$, a blending factor$\alpha \in \mathbb{R}$and the position of the interpolation$t \in \mathbb{R}$. Set \begin{eqnarray*}\vec{b}_i^0 (t) & := & \vec{b_i} \\ \vec{b}_i^r(t) & := & W_i^r(t) \vec{b}_i^{r-1}(t) + (1 - W_i^r(t))\,\vec{b}_{i+1}^{r-1}(t)\end{eqnarray*} Then$\vec{b}_0^n(t)$is the point with the parameter$t$on the corresponding blend between Bézier and Polynomial interpolation. The De-Casteljau algorithm is the special case for$\alpha = 1$, Aitken's Algorithm is the special case for$\alpha = 0$. Here is a plot of a planar interpolation: See how the curve for$\alpha = 0$passes through all 4 points. This is a property of Lagrange interpolation (polynomial interpolation). The curve for$\alpha = 1 is the only one that stays in the convex hull of the points; this is a property of Bézier curves.

As always, you can find the complete code for this post in the GitHub repository under chap07. Also, Farin has written a paper on this very topic. You can find it here.