Skip to content

Releases: 9seconds/ah

Minor bugfix

31 Dec 08:59
Compare
Choose a tag to compare

Small fix for configuration file management

Configuration file

30 Dec 19:56
Compare
Choose a tag to compare

This release supports HomeBrew/LinuxBrew. You can use it as usual (please notice that 9seconds/homebrew-ah is separate repository)

$ brew tap 9seconds/homebrew-ah
$ brew install ah

Update with Brews are trivial

$ brew update
$ brew reinstall ah

Also there is support of config files. Config file is placed in ~/.ah/config.yaml and this is a really simple YAML config. Here is the full example:

shell: zsh
histfile: /home/9seconds/.zsh_history
histtimeformat: "%d.%m.%y %H:%M:%S"

tmpdir: /tmp

Bugfix

25 Nov 04:33
Compare
Choose a tag to compare

Small fix for the situation where you have a pipe in command execution.

Automatic execution for ZSH

24 Nov 19:59
Compare
Choose a tag to compare

This release bring you an ability to execute ah t with whitelisted commands automatically. Currently for ZSH only but I will try to make support for Bash if I will find a good way to do it (maybe you know how to do it? Contributions are welcome!)

Readme is updated so please find a description at the end.

This release is built with Go 1.4rc1. I have no problems but if you will find them, please fill the issue immediately!

Fix for trace output command detection

06 Nov 20:40
Compare
Choose a tag to compare

This release fixes potentially tricky situation (or at least, tries to fix) when ah is unable to detect which command it should use to refer output. It can happen only if you execute a lot of commands simultaneously (starting tmuxinator for example) but it cannot cover all possible cases without intergration into shell.

Why is it so hard and patch may looks fishy? Basically, the reason is simple: command you are going execute and command in history is not the same. Do you love $() or backticks? This is a reason why it can fail.

Let's say, you execute the command ah t -- $(/usr/bin/env python) bootstrap.py. Okay, history will store this line. But naturally, shell gives ah ah t -- /usr/bin/python bootstrap.py. See the difference?

ah is not precise here also: the root cause is... shell again. All shells store unix timestamps which are seconds but not nanoseconds. So if you've executed 10 ssh git@github.com in one seconds, it is impossible to detect what command do we need to bind to.

But these cases are pretty rare. In most cases everything should work.

Fish shell support

04 Nov 21:11
Compare
Choose a tag to compare

This release brings you support of Fish shell

Proper TTY support

02 Nov 23:06
Compare
Choose a tag to compare

Fixes #5. Basically it is a big deal, you can run htop, vim or any other curses with ah. Do not ask about output of course, but at least nothing bad will happen.

Fix for OS X build

02 Nov 14:34
Compare
Choose a tag to compare
  • Fix for broken OS X build (see issue #1)
  • Fix for temporary directory problem (see issue #3)

This release eliminates usage os/user to determine home directory (now ah uses homedir). It fixes problems with cross-platform releases (e.g for OS X)

Also, it gives you a possibility to set your custom temporary directory for storing ah-related information (-m flag). Use it if you have your $HOME and /tmp on different volumes. By default ah assumes that /tmp and $HOME are on the same device. It is reasonable default because a lot of Linux distributions (and possibly OS X) use that schema by default.

First official release

01 Nov 14:45
Compare
Choose a tag to compare

Trace output fixes

31 Oct 10:32
Compare
Choose a tag to compare
Trace output fixes Pre-release
Pre-release

Fixes an issue where output was not stored if exit code of external command != 0