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

Strange behaviour when renaming a file with only case changes #1147

Closed
thomasschafer opened this issue Jun 11, 2024 · 4 comments · Fixed by #1151
Closed

Strange behaviour when renaming a file with only case changes #1147

thomasschafer opened this issue Jun 11, 2024 · 4 comments · Fixed by #1151
Labels
bug Something isn't working

Comments

@thomasschafer
Copy link

What system are you running Yazi on?

macOS

What terminal are you running Yazi in?

alacritty 0.13.2 (bb8ea18)

Did you try the latest code to see if this problem got fixed?

Tried, but the problem still

yazi --debug output

Yazi
    Version: 0.2.5 (189cb81 2024-06-11)
    Debug  : false
    OS     : macos-aarch64 (unix)

Ya
    Version: No such file or directory (os error 2)

Emulator
    Emulator.via_env: ("tmux-256color", "tmux")
    Emulator.via_csi: Ok(Unknown([Sixel]))
    Emulator.detect : Unknown([Sixel])

Adapter
    Adapter.matches: Sixel

Desktop
    XDG_SESSION_TYPE: None
    WAYLAND_DISPLAY : None
    DISPLAY         : None

SSH
    shared.in_ssh_connection: false

WSL
    /proc/sys/fs/binfmt_misc/WSLInterop: false

Variables
    SHELL              : Some("/bin/zsh")
    EDITOR             : Some("hx")
    ZELLIJ_SESSION_NAME: None
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None

Text Opener
    default: Some(Opener { run: "hx \"$@\"", block: true, orphan: false, desc: "hx", for_: None, spread: true })
    block  : Some(Opener { run: "hx \"$@\"", block: true, orphan: false, desc: "hx", for_: None, spread: true })

tmux
    TMUX   : false
    Version: 3.4

Dependencies
    file             : 5.41
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: 2.2.2
    magick           : No such file or directory (os error 2)
    fzf              : 0.52.0
    fd               : 10.1.0
    rg               : 14.1.0
    chafa            : No such file or directory (os error 2)
    zoxide           : 0.9.4
    unar             : 1.10.7
    jq               : 1.7.1


--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/Users/tschafer/.local/state/yazi" directory.

Logs:

  2024-06-11T16:02:19.239647Z  WARN yazi_adapter::emulator: [Adapter] No special environment variables detected
    at yazi-adapter/src/emulator.rs:70

  2024-06-11T16:02:19.239725Z  WARN yazi_adapter::emulator: [Adapter] Unknown TERM_PROGRAM: tmux
    at yazi-adapter/src/emulator.rs:84

  2024-06-11T16:02:19.239729Z  WARN yazi_adapter::emulator: [Adapter] Unknown TERM: tmux-256color
    at yazi-adapter/src/emulator.rs:92

Describe the bug

When changing a filename with a case-only change (e.g. foo too foO), a prompt is shown asking Overwrite an existing file? (y/N), and then both the new file name and the old file name are shown, even though only the new file exists.

The screen recording below shows the issue when renaming foo to foO, and then a rename from foO to foOa which shows the expected behaviour:

Screen.Recording.2024-06-11.at.16.58.20.mov

Expected Behavior

Case changes should behave the same as other name changes

To Reproduce

Rename a file with a case-only change, e.g. foo to foO

Configuration

No config

Anything else?

No response

@sxyazi
Copy link
Owner

sxyazi commented Jun 12, 2024

Please try #1151

@sxyazi sxyazi added the waiting on op Waiting for more information from the original poster label Jun 12, 2024
@thomasschafer
Copy link
Author

Please try #1151

That works! Thank you so much for getting this sorted so quickly 🙌

@github-actions github-actions bot removed the waiting on op Waiting for more information from the original poster label Jun 12, 2024
@mikavilpas
Copy link
Contributor

Nice - I think I saw this at some point but realized it too late, and didn't figure out this was the cause 👍🏻

Copy link

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 Jul 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
3 participants