Bug 393799 - Parent folder creation not working anymore
Summary: Parent folder creation not working anymore
Status: RESOLVED FIXED
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-03 10:52 UTC by Levente Varga
Modified: 2018-05-06 00:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Levente Varga 2018-05-03 10:52:48 UTC
When trying to create multiple folders recursively using the New Folder dialog (like using the mkdir -p command), each descending folder is created in the current location one after the other instead of creating them recursively one into the other (i.e. in case of a/b/c a, b and c folders are created in the current location instead of a/b/c folder(s)).

This feature was working in Krusader 2.4 (this was the version in Kubuntu 14.04 if I'm not mistaken) but doesn't work anymore in 2.6 (current version in Kubuntu 18.04, Kubuntu 17.10 and Kubuntu 17.10 backports).

Steps to reproduce:
1. Open New Folder dialog
2. Enter a/b/c and press OK

Actual results:
Folders a, b and c appear in the current folder one after the other beside an error message that varies either that last folder doesn't exists (in the case folder c)
If the creation is repeated more than once (n times where n is the number of folders) the folders are created in the following way
── a
│   ├── b
│   │   └── c
│   └── c
├── b
└── c

Expected Results:
After created the folder tree should look like this:
└── a
    └── b
        └── c
Comment 1 Martin Kostolný 2018-05-03 13:00:17 UTC
Hi! Thanks for report. This is fortunately already fixed in Krusader git. We plan to release a new version of Krusader around May the 13th including this fix.

Please reopen if you find this not working in git version or future 2.7 version.