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.

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

Cannot enable symlink in status bar #13

Closed
zarifpour opened this issue Oct 26, 2023 · 5 comments
Closed

Cannot enable symlink in status bar #13

zarifpour opened this issue Oct 26, 2023 · 5 comments
Labels
waiting on op Waiting for more information from the original poster

Comments

@zarifpour
Copy link
Contributor

I have rewritten the Status:name() method and have saved it as a file with the following patch:

CleanShot 2023-10-26 at 11 27 35 on iTerm2 — zsh

Here is my yazi.toml:

CleanShot 2023-10-26 at 11 27 47 on Arc — New Issue · yazi-rsyazi-rs github io

I tried the following:

  • Copying the whole file over - removing Status = {}, as you indicated for manager (Cannot enable full border #10) - and modifying only the Status:name() method.
  • Naming it status.lua and updating the path in toml.
  • Including only the single plugin in the preload variable in toml.

Any ideas?

@sxyazi
Copy link
Member

sxyazi commented Oct 26, 2023

Hmm, this is exactly what I do, and it works for me. I need more information: Are you placing the cursor on a symlink? How is the status bar rendering? Is there any error in ~/.local/state/yazi/yazi.log?

@zarifpour
Copy link
Contributor Author

yazi.log is empty, not using my cursor, I'm using iterm2 with zsh.

@sxyazi
Copy link
Member

sxyazi commented Oct 27, 2023

nope, meaning that if you hover the cursor on a symlink file? and how about the status bar rendering?

@sxyazi sxyazi added the waiting on op Waiting for more information from the original poster label Oct 30, 2023
Copy link
Contributor

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Copy link
Contributor

I'm going to lock this issue because it has been closed for 30 days. ⏳ This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
waiting on op Waiting for more information from the original poster
Projects
None yet
Development

No branches or pull requests

2 participants