generated from cockpit-project/starter-kit
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Renaming a file to the name of a current directory moves it there #399
Labels
bug
Something isn't working
Comments
The same happens with the creation of symlink and likely copy / pasting. |
jelly
added a commit
to jelly/cockpit-navigator
that referenced
this issue
Apr 25, 2024
We rename in Files by moving the file to the new filename but when this is a directory `mv` moves the file to that directory instead. This is quite logical in a shell but not in a GUI, there it is unexpected behaviour. Closes: cockpit-project#399
jelly
added a commit
to jelly/cockpit-navigator
that referenced
this issue
Apr 26, 2024
We rename in Files by moving the file to the new filename but when this is a directory `mv` moves the file to that directory instead. This is quite logical in a shell but not in a GUI, there it is unexpected behaviour. Furthermore when renaming an existing file we replace it, that is unexpected as well and should be possible but in the first place should warn. Closes: cockpit-project#399
jelly
added a commit
to jelly/cockpit-navigator
that referenced
this issue
May 8, 2024
We rename in Files by moving the file to the new filename but when this is a directory `mv` moves the file to that directory instead. This is quite logical in a shell but not in a GUI, there it is unexpected behaviour. Related: cockpit-project#399
martinpitt
pushed a commit
that referenced
this issue
May 9, 2024
We rename in Files by moving the file to the new filename but when this is a directory `mv` moves the file to that directory instead. This is quite logical in a shell but not in a GUI, there it is unexpected behaviour. Related: #399
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That's because we
mv
without thinking too much about it.The text was updated successfully, but these errors were encountered: