Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

yazi 0.2.4 #165615

Closed
wants to merge 1 commit into from
Closed

yazi 0.2.4 #165615

wants to merge 1 commit into from

Conversation

Porkepix
Copy link
Contributor

@Porkepix Porkepix commented Mar 9, 2024

Created by brew bump

Created with brew bump-formula-pr.

release notes 
This version adds support for [cross-directory selection](https://github.com/sxyazi/yazi/pull/693), which means you can select files from multiple different directories and perform operations on them.

Yazi's accessibility also has been greatly improved, including adding color to icons, a new file selection counter, improved visibility of hovered files, enhanced keyword recognition in finds, long path truncation, and a new color system.


As for the plugin system, we have rewritten Yazi's Lua binding using Unsafe Rust, making the initialization process of plugins very inexpensive by lazy-loading app data. This fundamentally solves the difficulty of cross-tab data access, making future plans for dual-pane/tree-view possible, as they can be efficiently implemented as a plugin!


In addition, loaded plugins are now cached, meaning that plugin loading speed will be faster. The improvement in plugin performance directly reflects the overall performance of Yazi because in Yazi, plugins are first-class citizens, with most UI being drawn by built-in UI plugins, and previews and preloads also being done through plugins, which is the biggest driving force for us to constantly improve plugin performance.


Finally, we have added some new APIs that we hope plugin developers will find useful:


    

  • ya.input(): Request user input;
    • 

  • ya.notify(): Send a foreground notification to the user, which is useful for background tasks;
    • 

  • ya.hide(): Request terminal control and hide Yazi in the background. This is useful for calling interactive programs like fzf, zoxide, etc., in plugins;
    • 

  • ui.Clear(): Clear a specific UI area, which is useful for implementing custom UI layouts.
    • 



To implement ya.notify(), we have added a new Vim-like notification component:



  
    
    Vim-like.notification.mp4
    
  

  




For more changes, please read "What's Changed" below.


Heads up


The exec property will be deprecated in the next major version, v0.3, and will be replaced by run.


Please replace all instances of exec = ... with run = ... in your yazi.toml and keymap.toml if any.


What's Changed



New Contributors



Full Changelog: sxyazi/yazi@v0.2.3...v0.2.4

@github-actions github-actions bot added rust Rust use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Mar 9, 2024
@chenrui333
Copy link
Member 

  ==> /opt/homebrew/Cellar/yazi/0.2.4/bin/yazi --version
  Killing child processes...
  Error: yazi: failed
  An exception occurred within a child process:
    Timeout::Error: execution expired

@chenrui333 chenrui333 added the test failure CI fails while running the test-do block label Mar 9, 2024
@chenrui333
Copy link
Member

@sxyazi looks like for yazi --version it also needs to check keychain, any idea? Thanks!

@sxyazi
Copy link
Contributor

sxyazi commented Mar 9, 2024

Hi @chenrui333, it seems that macOS's security policy is intercepting the binary from running. I think re-running the CI should solve this issue.

@chenrui333
Copy link
Member

yeah, I did run the build in my local, had the same issue.

@chenrui333 chenrui333 added the CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. label Mar 9, 2024
@chenrui333
Copy link
Member

cc @sxyazi again

@sxyazi
Copy link
Contributor

sxyazi commented Mar 10, 2024

Weird, not sure why it still failed... I tested it locally, the security alert only appeared the first time it was opened. Maybe we can simply remove this test? I'm not quite sure what I can do here, sorry.

@chenrui333
Copy link
Member

I tested it locally, the security alert only appeared the first time it was opened

yeah, that is what I commented above, this behavior did not happen for the previous release?

@sxyazi
Copy link
Contributor

sxyazi commented Mar 10, 2024

Yes, in previous releases, that hasn't happened/I haven't noticed.

The security policy of macOS is a black box to me, I'm not sure what checks it does internally.

@github-actions GitHub Actions
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.

@github-actions github-actions bot added the stale No recent activity label Mar 13, 2024
@sxyazi sxyazi mentioned this pull request Mar 14, 2024
Closed
@github-actions github-actions bot closed this Mar 15, 2024
@sxyazi sxyazi mentioned this pull request Mar 24, 2024
Closed
@github-actions github-actions bot added the outdated PR was locked due to age label Apr 14, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. outdated PR was locked due to age rust Rust use is a significant feature of the PR or issue stale No recent activity test failure CI fails while running the test-do block
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@Porkepix @chenrui333 @sxyazi