mirror of
https://blitiri.com.ar/repos/chasquid
synced 2025-12-23 15:37:01 +00:00
aliases: Simplify lookup logic, remove alias-exists hook
This patch simplifies the internal alias lookup logic, unifying it across Resolve and Exists. As part of this, the `alias-exists` hook is removed. It was redundant to begin with, although it enabled a potential optimization, it isn't worth the complexity. The timeout for execution of both was the same. This change should be backwards-compatible because `alias-resolve` is still used, and the semantics haven't changed.
This commit is contained in:
@@ -85,11 +85,11 @@ aliases.
|
||||
|
||||
## Hooks
|
||||
|
||||
There are two hooks that allow more sophisticated aliases resolution:
|
||||
`alias-exists` and `alias-resolve`.
|
||||
There is a hook that allows more sophisticated aliases resolution:
|
||||
`alias-resolve`.
|
||||
|
||||
If they exist, they are invoked as part of the resolution process and the
|
||||
results are merged with the file-based resolution results.
|
||||
If it exists, it is invoked as part of the resolution process, and the results
|
||||
are merged with the file-based resolution results.
|
||||
|
||||
See the [hooks](hooks.md) documentation for more details.
|
||||
|
||||
|
||||
@@ -73,17 +73,3 @@ without emitting any output.
|
||||
|
||||
There is a 5 second timeout for hook execution. If the hook exits with an
|
||||
error, including timeout, delivery will fail.
|
||||
|
||||
|
||||
## Alias exists hook
|
||||
|
||||
When chasquid needs to check whether an alias exists or not, it will run the
|
||||
command at `$config_dir/hooks/alias-exists` (if the file exists).
|
||||
|
||||
The address to check will be passed as the single argument.
|
||||
|
||||
If the commands exits successfuly (exit code 0), then the alias exists; any
|
||||
other exit code signals that the alias does not exist.
|
||||
|
||||
There is a 5 second timeout for hook execution. If the hook times out, the
|
||||
alias will be assumed not to exist.
|
||||
|
||||
Reference in New Issue
Block a user