aboutsummaryrefslogtreecommitdiffstats
path: root/crates (follow)
Commit message (Collapse)AuthorAge
* chore: update rusty_paseto and rusty_paserk (#2942)Ben Beasley2025-10-20
| | | | | | | | | | | | <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* feat: add import from PowerShell history (#2864)Lucas Trzesniewski2025-10-20
| | | | | | | | | | | | | | | | This adds an `atuin import powershell` command. Of course, it is related to #2543 but I'm submitting it as a separate PR since the code is self-contained and simple enough, and the feature could be useful on its own. /cc @ajn142 who [requested it](https://github.com/atuinsh/atuin/issues/84#issuecomment-3091692807). ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* feat: add commit to displayed version info (#2922)Lucas Trzesniewski2025-10-20
| | | | | | | | | | | | | | | | | | | | This adds the commit SHA to the following: - `atuin doctor` - `atuin info` (which already displays the version) - `atuin --version` (but not `atuin -V` in order not to affect `atuin --help`) I'm submitting this because I had issue reports in #2543 which were already resolved, so being able to easily ask for the commit id would have been helpful, as the version number isn't meaningful in a PR. Also, I suppose the info should have been included in `atuin doctor` in the first place, so that probably fixes an oversight. ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* chore(release): prepare for release 18.9.0 (#2952)Ellie Huxtable2025-10-20
| | | | | | | | | | | | <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [ ] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [ ] I have checked that there are no existing pull requests for the same thing
* feat: add shell pipelines to command chaining (#2938)Lucas Trzesniewski2025-10-06
| | | | | | | | | | I wanted to use `command_chaining` to write a pipeline (`cmdA | cmdB`) and was genuinely surprised it didn't work. ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* feat: more accurately filter secret tokens (#2932)Keith Cirkel2025-10-02
|
* feat: add various acceptance keys (#2928)Keith Cirkel2025-09-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change introduces (optional) acceptance keys of Backspace and Left Arrow, when at the start of a line. These two are common muscle memory actions for users. The configuration defaults to false so as not to disrupt existing user patterns. This also adds a test that exercises the various acceptance modes, which as it turns out was quite easy to do. I discussed this on discord where [Ellie suggested I raised an issue](https://discord.com/channels/954121165239115808/1421180955657244703/1422642337481228400), but I felt like a PR would be more tangiable. I've tested this locally and I'm very happy with how these keys work, it fits my needs well. `exit_past_line_start` and `accept_past_line_start` can technically co-exist. When this happens `accept_past_line_start` takes precedence. Is this okay, or should we reconsider the config? Perhaps `acceptance_keys = []` would be better here? I'm very open to changes here. <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* fix: fish up binding (#2902)Ramses2025-09-27
|
* chore: update to Rust 1.90 (#2916)Ray Kohler2025-09-26
| | | | | | | | | | | | | | | | <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [X] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [X] I have checked that there are no existing pull requests for the same thing Hopefully this one is mergeable as is, unlike the 1.89 upgrade. Fixes: #2915
* fix(dotfiles): properly escape spaces/quotes in varsBraxton Schafer2025-09-25
|
* feat(stats): add dotnet to default common subcommandsLucas Trzesniewski2025-09-25
|
* refactor: shell environment variablesLucas Trzesniewski2025-09-18
|
* fix: remove __atuin_chain_command__ prefixLucas Trzesniewski2025-09-18
| | | | The command chaining feature can be implemented without the prefix.
* fix: dissociate command_chaining from enter_acceptLucas Trzesniewski2025-09-18
|
* fix: clippy warningschitao12342025-09-15
|
* feat: add session-preload filter mode to include global history from before ↵chitao12342025-09-15
| | | | | | session start This mode mimics the default behavior for many shells.
* feat(tui): add show_numeric_shortcuts config to hide 1-9 shortcuts (#2766)sebbie2025-09-12
| | | | | | - Config option: show_numeric_shortcuts (default: true) - When false, hide 1–9 numeric badges; keep indicator on selected row - Example key added to example config.toml
* fix: clippy warnings I don't have on my version of clippyRay Kohler2025-09-10
|
* fix: run `cargo fmt`Ray Kohler2025-09-10
|
* fix: `cargo update` and changes needed to accomodate itRay Kohler2025-09-10
|
* fix: clean up new rustc and clippy warnings on Rust 1.89Ray Kohler2025-09-10
|
* fix: use fullscreen if `inline_height` is too large (#2888)Lucas Trzesniewski2025-09-09
| | | | | | | | | | | | This uses fullscreen mode if `inline_height` is larger than the terminal height. Currently, in that situation, the screen is always cleared upon exit from `atuin search -i`. This change will preserve the buffer when Atuin takes the whole screen, which is a much friendlier behavior. Demo by @LecrisUT: https://github.com/atuinsh/atuin/pull/2600#issuecomment-3228255130 Closes #2207 ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* feat(tui): select entries using number in vim-normal mode. closes #2368 (#2893)Adam Jahn2025-09-09
| | | | | | | <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* fix: expand path for daemon.socket_path (#2870)Paul Barton2025-08-23
| | | | | | | | | | | This parses the daemon.socket_path config item to allow it to be set to something like `"${XDG_RUNTIME_DIR}/atuin.sock"`. Fixes https://github.com/atuinsh/atuin/issues/2490. <!-- Thank you for making a PR! Bug fixes are always welcome, but if you're adding a new feature or changing an existing one, we'd really appreciate if you open an issue, post on the forum, or drop in on Discord --> ## Checks - [x] I am happy for maintainers to push small adjustments to this PR, to speed up the review cycle - [x] I have checked that there are no existing pull requests for the same thing
* feat: highlight matches in interactive search (#2653)Frank Hamand2025-08-04
| | | | | | | | | | | | | | | | | | | | | | | * feat: highlight matches in interactive search uses `norm` to do fzf-compatible matches when rendering history items in the search panel to highlight the matching ranges of the item this helps see _why_ certain history items have come up note that this will never be 100% perfect as we search on a sqlite query but it should be good enough in most cases * fmt * fix some clippy issues * refactor to pass in a history_highlighter instead of search and engine * improve the highlighting on the selected row --------- Co-authored-by: Ellie Huxtable <ellie@atuin.sh>
* fix: match logic of theme directory with settings directory, so ↵P T Weir2025-08-04
| | | | ATUIN_CONFIG_DIR is respected (#2707)
* fix: Make status exit 1 if not logged in (#2843)David Jack Wange Olrik2025-08-04
|
* fix: honor timezone in inspector stats (#2853)Ray Kohler2025-08-04
| | | | | | | | | * fix: honor timezone in inspector stats fixes: #2567 * docs: fix rustdoc warning about URL markup * fix: pass timezone by value, as suggested by clippy (oops)
* fix: clippy issues on Windows (#2856)Lucas Trzesniewski2025-08-04
|
* chore(release): prepare for release 18.8.0 (#2858)Ellie Huxtable2025-08-04
|
* feat: add IDX_CACHE_ROLLOUT (#2850)Ellie Huxtable2025-07-29
| | | | | | | | | | Only really useful for Atuin cloud Given a % chance, either use the idx cache or use the old aggregation query This is to enable us to test rollout the idx cache, without breaking all queries in weird ways. Can monitor for a change in http codes/etc, and easily roll back.
* fix(build): enable sqlite feature for sqlite server (#2848)Ellie Huxtable2025-07-29
|
* fix: ensure the idx cache is cleaned on deletion, only insert if records are ↵Ellie Huxtable2025-07-24
| | | | inserted (#2841)
* fix: use transaction for idx consistency checking (#2840)Ellie Huxtable2025-07-24
|
* feat: add inline_height_shell_up_key_binding option (#2817)Caio S. Rohwedder2025-07-23
|
* nushell: fix `get -i` deprecation (#2829)Joaquín Triñanes2025-07-23
| | | | | Since https://github.com/nushell/nushell/pull/16007, the recommended flag is `--optional`. To avoid compatibility issues, the builtin optional access syntax is used instead, which is backwards-compatible.
* fix: Make login exit 1 if already logged in (#2832)David Jack Wange Olrik2025-07-23
|
* feat: Support multi part commands (Fixes #2836) (#2837)Marko Bausch2025-07-23
| | | | | * feat: Support multi part commands * fix: Clippy
* feat: add info for 'official' plugins (#2835)Ellie Huxtable2025-07-22
| | | | | * feat: add info for 'official' plugins * fix default features
* feat: command chaining (#2834)Ellie Huxtable2025-07-22
| | | | | | | * feat: command chaining Allow for smart completion of commands ending in && or || * fmt
* chore: update to rust 1.88 (#2815)Ellie Huxtable2025-07-22
| | | | | | | | | * chore: update to rust 1.88 * clippy + fmt * update ci version * update flake
* Update indicatif to 0.18.0 (#2833)Ben Beasley2025-07-21
|
* chore(release): prepare for release 18.7.1 (#2826)Ellie Huxtable2025-07-16
|
* fix: add check for postgresql prefix (#2825)Scotte Zinn2025-07-16
| | | thanks for the speedy fix!
* chore(release): prepare for release 18.7.0 (#2823)Ellie Huxtable2025-07-16
| | | | | * chore(release): prepare for release 18.7.0 * lockfile
* fix: refuse "--dupkeep 0" (#2807)依云2025-07-03
| | | People may think it would keep only one copy, but it didn't work that way.
* feat: Add sqlite server support for self-hosting (#2770)Scotte Zinn2025-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Move db_uri setting to DbSettings * WIP: sqlite crate framework * WIP: Migrations * WIP: sqlite implementation * Add sqlite3 to Docker image * verified_at needed for user query * chore(deps): bump debian (#2772) Bumps debian from bookworm-20250428-slim to bookworm-20250520-slim. --- updated-dependencies: - dependency-name: debian dependency-version: bookworm-20250520-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(doctor): mention the required ble.sh version (#2774) References: https://forum.atuin.sh/t/1047 * fix: Don't print errors in `zsh_autosuggest` helper (#2780) Previously, this would result in long multi-line errors when typing, making it hard to see the shell prompt: ``` $ Error: could not load client settings Caused by: 0: could not create config file 1: failed to create file `/home/jyn/.config/atuin/config.toml` 2: Required key not available (os error 126) Location: atuin-client/src/settings.rs:675:54 fError: could not load client settings Caused by: 0: could not create config file 1: failed to create file `/home/jyn/.config/atuin/config.toml` 2: Required key not available (os error 126) Location: atuin-client/src/settings.rs:675:54 faError: could not load client settings ``` Silence these in autosuggestions, such that they only show up when explicitly invoking atuin. * fix: `atuin.nu` enchancements (#2778) * PR feedback * Remove sqlite3 package * fix(search): prevent panic on malformed format strings (#2776) (#2777) * fix(search): prevent panic on malformed format strings (#2776) - Wrap format operations in panic catcher for graceful error handling - Improve error messages with context-aware guidance for common issues - Let runtime-format parser handle validation to avoid blocking valid formats Fixes crash when using malformed format strings by catching formatting errors gracefully and providing actionable guidance without restricting legitimate format patterns like {command} or {time}. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Satisfy cargo fmt * test(search): add regression tests for format string panic (#2776) - Add test for malformed JSON format strings that previously caused panics - Add test to ensure valid format strings continue to work - Prevent future regressions of the format string panic issue 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Koichi Murase <myoga.murase@gmail.com> Co-authored-by: jyn <github@jyn.dev> Co-authored-by: Tyarel8 <98483313+Tyarel8@users.noreply.github.com> Co-authored-by: Brian Cosgrove <cosgroveb@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
* fix(search): prevent panic on malformed format strings (#2776) (#2777)Brian Cosgrove2025-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fix(search): prevent panic on malformed format strings (#2776) - Wrap format operations in panic catcher for graceful error handling - Improve error messages with context-aware guidance for common issues - Let runtime-format parser handle validation to avoid blocking valid formats Fixes crash when using malformed format strings by catching formatting errors gracefully and providing actionable guidance without restricting legitimate format patterns like {command} or {time}. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Satisfy cargo fmt * test(search): add regression tests for format string panic (#2776) - Add test for malformed JSON format strings that previously caused panics - Add test to ensure valid format strings continue to work - Prevent future regressions of the format string panic issue 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
* fix: `atuin.nu` enchancements (#2778)Tyarel82025-06-05
|
* fix: Don't print errors in `zsh_autosuggest` helper (#2780)jyn2025-06-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, this would result in long multi-line errors when typing, making it hard to see the shell prompt: ``` $ Error: could not load client settings Caused by: 0: could not create config file 1: failed to create file `/home/jyn/.config/atuin/config.toml` 2: Required key not available (os error 126) Location: atuin-client/src/settings.rs:675:54 fError: could not load client settings Caused by: 0: could not create config file 1: failed to create file `/home/jyn/.config/atuin/config.toml` 2: Required key not available (os error 126) Location: atuin-client/src/settings.rs:675:54 faError: could not load client settings ``` Silence these in autosuggestions, such that they only show up when explicitly invoking atuin.
generated by cgit v1.3.1 (git 2.54.0) at 2026-06-17 15:30:18 +0000