hatchling/vendor/ at main · oppi.li/hatchling · Tangled

oppi.li / hatchling

0

personal fork of atuin without AI stuff, sync stuff, script management stuff

0

hatchling / vendor

1 folder 2 files

at main

taylor.fish feat(bash): bundle bash-preexec with Atuin; automatically load if no other preexec backend is loaded (#3650) 10d ago

feat(bash): bundle bash-preexec with Atuin; automatically load if no other preexec backend is loaded (#3650) This PR bundles [bash-preexec](https://github.com/rcaloras/bash-preexec) with Atuin and updates `atuin init bash` to automatically load bash-preexec if no other preexec backend (ble.sh or an external copy of bash-preexec) has been loaded. This behavior can be overwritten by setting `ATUIN_NO_BUILTIN_PREEXEC=1`; ideally this is passed to `atuin init` directly: ```bash eval "$(ATUIN_NO_BUILTIN_PREEXEC=1 atuin init bash)" ``` since then we will avoid emitting an unused function containing the contents of bash-preexec, but we also check the variable dynamically in the init script, so if a user caches the result of `atuin init bash` and then later sets the override variable, it will still take effect. One thing to note: if you initialize a preexec backend in your .bashrc *after* Atuin, it will not be detected, and Atuin will load the builtin bash-preexec. In the case of another copy of bash-preexec, this is not an issue, as it contains its own include guard. In the case of ble.sh, I tested this locally and did not notice any issues; however, I am not a regular ble.sh user.

1 week ago

feat(bash): bundle bash-preexec with Atuin; automatically load if no other preexec backend is loaded (#3650) This PR bundles [bash-preexec](https://github.com/rcaloras/bash-preexec) with Atuin and updates `atuin init bash` to automatically load bash-preexec if no other preexec backend (ble.sh or an external copy of bash-preexec) has been loaded. This behavior can be overwritten by setting `ATUIN_NO_BUILTIN_PREEXEC=1`; ideally this is passed to `atuin init` directly: ```bash eval "$(ATUIN_NO_BUILTIN_PREEXEC=1 atuin init bash)" ``` since then we will avoid emitting an unused function containing the contents of bash-preexec, but we also check the variable dynamically in the init script, so if a user caches the result of `atuin init bash` and then later sets the override variable, it will still take effect. One thing to note: if you initialize a preexec backend in your .bashrc *after* Atuin, it will not be detected, and Atuin will load the builtin bash-preexec. In the case of another copy of bash-preexec, this is not an issue, as it contains its own include guard. In the case of ble.sh, I tested this locally and did not notice any issues; however, I am not a regular ble.sh user.

1 week ago

feat(bash): bundle bash-preexec with Atuin; automatically load if no other preexec backend is loaded (#3650) This PR bundles [bash-preexec](https://github.com/rcaloras/bash-preexec) with Atuin and updates `atuin init bash` to automatically load bash-preexec if no other preexec backend (ble.sh or an external copy of bash-preexec) has been loaded. This behavior can be overwritten by setting `ATUIN_NO_BUILTIN_PREEXEC=1`; ideally this is passed to `atuin init` directly: ```bash eval "$(ATUIN_NO_BUILTIN_PREEXEC=1 atuin init bash)" ``` since then we will avoid emitting an unused function containing the contents of bash-preexec, but we also check the variable dynamically in the init script, so if a user caches the result of `atuin init bash` and then later sets the override variable, it will still take effect. One thing to note: if you initialize a preexec backend in your .bashrc *after* Atuin, it will not be detected, and Atuin will load the builtin bash-preexec. In the case of another copy of bash-preexec, this is not an issue, as it contains its own include guard. In the case of ble.sh, I tested this locally and did not notice any issues; however, I am not a regular ble.sh user.

1 week ago

README.md

This directory contains vendored repositories.

Use vendor.sh to manage vendored repositories:

Usage:
  vendor.sh add <repo-url> <ref> [name]
  vendor.sh list
  vendor.sh update <name> <ref>

<ref> specifies which branch/tag/commit to check out in the vendored
repository.

<name> is the name of the subdirectory in 'vendor/'. By default, it is
inferred from the repository URL.