Activating this xontrib breaks the behavior of cd without arguments, as explained in this xonsh issue: xonsh/xonsh#1484
In the comments, near the end, the culprit line in autoxsh is specified (related to an import).

Hi! Thank you for the xontrib!

Please add xonsh and xontrib tags to the repo:

It helps spread the word about xontrib on Github.

Thanks!

Hi! Great xontrib!

To increase security:

1. Save md5 hash and approval date of .autoxsh file with the path
2. Check md5 hash before running
3. If there is mismatch of hash then show prompt: with the time of change, the way to see the diff.

Example:

cd /project
# The autoxsh file in this directory was approved 2 months ago but was changed 5 days ago. 
# What's next? [Approve / Decline / Show diff / Skip autoxshing]

Thanks!

Is it possible to implement auto command when leave dir too? Just asking for this implementation because for several venvs it would be very helpfull.

Instead of overwriting the cd alias, save the old value and call it instead of xonsh.dirstack.cd().

This is to cooprerate better with xontrib-avox and xontrib-z (both of which also override cd).

Hi! Great xontrib!

It will be good:

1. To use the value from $XONSH_DATA_DIR (i.e. /home/user/.local/share/xonsh/, it's XDG_DATA_HOME) to saving data.
2. Name the files as xontrib_autoxsh_ignore instead of .autoxonsh_ignore to make it visible and sane.

Thanks!

Hi!

Could you create Github releases for this? I'm using some automated tools to get latest release, update some JSON that's read by Nix expressions to generate my Xonsh dependencies and they fail when there's no release to use :)

Thanks! 😄

Instead of aliasing cd, use the on_chdir event (new to v0.4.6).