Jonathan Daugherty

Hah! Well, let's see if I can remember. At the time I was writing the library, I wanted a tool name that was very short and memorable. Tool names with...

Thanks for the report! If I understand this correctly, the fix is just to qualify all operations on the `installed_migrations` table with the `public` schema. Right? I would also be...

Welcome back. I recall that you opened #27, which eventually got closed due to inactivity (rather than opposition). As far as I'm concerned `dbmigrations` is still capable of doing what...

@basti1302 judging by this, > I'd like to capture all my migrations directly in source code I think @3noch intends to literally keep the migrations in his program sources rather...

@3noch Okay. Is this something you're interested in contributing? Or would you prefer that someone else take care of this?

> From what I can tell, it seems that dbmigrations' approach is properly suited to serious server setups where you are likely to have multiple DB servers that can end...

As per #559: we should also support "acronym" matching of users (e.g. "John Doe" should be matchable with "JD"). Apparently the official client supports this.

Oh! Nickname rendering and matching is already supported. If your account preferences (or server preferences) are set to display nicknames instead of usernames, Matterhorn will honor that. Matterhorn's channel selection...

It's possible to search for users by any string if you use the `@` autocompletion, but when searching the channel list, only what's displayed can be searched. (Otherwise it would...

@pieqq You are right - Matterhorn does not yet support displaying users by full name. It *does* support searching for them in tab-completion by full name, but Matterhorn only supports...