View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002088 | Double Commander | File operations | public | 2018-06-27 12:36 | 2021-09-05 15:11 |
Reporter | stef | Assigned To | Alexx2000 | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Projection | none | ETA | none | ||
Product Version | 0.8.3 | Product Build | 2018/06/03 | ||
Target Version | 0.9.0 | Fixed in Version | 0.9.0 | ||
Summary | 0002088: Can't rename file with leading blank | ||||
Description | Attempting to rename a file with a leading blank in the filename results in an error "Source and target file name are identical" | ||||
Steps To Reproduce | 1. Create file with leading blank in filename echo test > " test.txt" 2. Select the file in double commander window and press F2 3. Remove the leading blank 4. Press ENTER | ||||
Additional Information | Same problem when you enter ren " test.txt" test.txt in the integrated command line window at the bottom. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in Revision | 8533 | ||||
Operating system | Windows | ||||
Widgetset | Win32 | ||||
Architecture | 32-bit | ||||
has duplicate | 0002189 | closed | Ошибка переименования файла с пробелом в начале имени |
|
1. Cannot reproduce with doublecmd-qt (ver.0.8.3) on Linux / Debian Wheezy. A file created like echo test>' test.txt' is pretty possible to delete. 2. I wonder, what is the regular use case that leads to originating of a file with a leading blank (the filename beginning with a space) – could you please explain? Normally, to start a filename with a space is definitely not recommended for serious reasons and many systems simply do not allow it (or at least do not guarantee the correct behaviour) – maybe it can be a root of a described problem... |
|
It is Windows only. |
|
@robertn question 2: there is no use case for it, it just happened that I created by mistake a file with a leading blank in the filename and when I tried to delete it I ran into this bug. I agree that there's no good reason for intentionally using such a filenamen, but nethertheless I consider it a bug if such filenames cannot be handles by double commander, as they are perfectly legal filenames. |
|
I've attached the file to demonstrate some issues with folders that have space at the end. - Folder with space at the end can be created --> OK - Folder with space at the end can be deleted --> OK - Folder with space at the end can be moved --> OK - Folder with space at the end can be moved to other name --> OK - Folder with space at the end can be browsed --> OK - Folder with space at the end can not inline renamed --> Bug - Inline rename cannot create name with space at the end --> IMHO Bug, at least inconsistent behavior |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-06-27 12:36 | stef | New Issue | |
2018-07-03 01:45 | robertn | Note Added: 0002656 | |
2018-07-04 14:10 | Alexx2000 | Note Added: 0002664 | |
2018-07-04 14:10 | Alexx2000 | Status | new => acknowledged |
2018-07-04 14:10 | Alexx2000 | Status | acknowledged => confirmed |
2018-08-18 16:18 | stef | Note Added: 0002752 | |
2018-09-18 16:58 | kfranic | File Added: 2018-09-18 15-51-33.flv | |
2018-09-18 17:01 | kfranic | Note Added: 0002770 | |
2018-12-19 08:18 | Alexx2000 | Target Version | => 0.9.0 |
2018-12-19 08:18 | Alexx2000 | Relationship added | has duplicate 0002189 |
2018-12-22 11:15 | Alexx2000 | Fixed in Revision | => 8533 |
2018-12-22 11:15 | Alexx2000 | Status | confirmed => resolved |
2018-12-22 11:15 | Alexx2000 | Fixed in Version | => 0.9.0 |
2018-12-22 11:15 | Alexx2000 | Resolution | open => fixed |
2018-12-22 11:15 | Alexx2000 | Assigned To | => Alexx2000 |
2021-09-05 15:11 | Alexx2000 | Status | resolved => closed |