Why would Get-ChildItem -Recurse | Remove-Item work?












1














I've seen on a lot of places (for example, here, here, or here) where people suggest to use



Get-ChildItem -Path "Some path" -Recurse | Remove-Item


to recursively delete a directory, but why would this work?



When I run Get-ChildItem -Path "foo" -Recurse | % { "$_" }, I see directories were listed first, and then files follows.
It shows something like this:



1st_child_directory
2st_child_directory
...
1st_file_in_foo
2nd_file_in_foo
...
1st_file_in_1st_child_directory
2st_file_in_1st_child_directory
...
1st_file_in_2st_child_directory
...


And so on.



If these get piped into Remove-Item in the same order, then Remove-Item would remove directories first (which are still non-empty), and then remove files inside directories (but directories should already been removed), and this is a bit counter-intuitive...
So why would Get-ChildItem -Recurse | Remove-Item work, and how does it work?










share|improve this question




















  • 1




    Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
    – LotPings
    Dec 28 '18 at 0:31










  • You can find out: Create some sample directories and files and run the command, and see if it works or not.
    – Bill_Stewart
    Dec 28 '18 at 16:53
















1














I've seen on a lot of places (for example, here, here, or here) where people suggest to use



Get-ChildItem -Path "Some path" -Recurse | Remove-Item


to recursively delete a directory, but why would this work?



When I run Get-ChildItem -Path "foo" -Recurse | % { "$_" }, I see directories were listed first, and then files follows.
It shows something like this:



1st_child_directory
2st_child_directory
...
1st_file_in_foo
2nd_file_in_foo
...
1st_file_in_1st_child_directory
2st_file_in_1st_child_directory
...
1st_file_in_2st_child_directory
...


And so on.



If these get piped into Remove-Item in the same order, then Remove-Item would remove directories first (which are still non-empty), and then remove files inside directories (but directories should already been removed), and this is a bit counter-intuitive...
So why would Get-ChildItem -Recurse | Remove-Item work, and how does it work?










share|improve this question




















  • 1




    Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
    – LotPings
    Dec 28 '18 at 0:31










  • You can find out: Create some sample directories and files and run the command, and see if it works or not.
    – Bill_Stewart
    Dec 28 '18 at 16:53














1












1








1







I've seen on a lot of places (for example, here, here, or here) where people suggest to use



Get-ChildItem -Path "Some path" -Recurse | Remove-Item


to recursively delete a directory, but why would this work?



When I run Get-ChildItem -Path "foo" -Recurse | % { "$_" }, I see directories were listed first, and then files follows.
It shows something like this:



1st_child_directory
2st_child_directory
...
1st_file_in_foo
2nd_file_in_foo
...
1st_file_in_1st_child_directory
2st_file_in_1st_child_directory
...
1st_file_in_2st_child_directory
...


And so on.



If these get piped into Remove-Item in the same order, then Remove-Item would remove directories first (which are still non-empty), and then remove files inside directories (but directories should already been removed), and this is a bit counter-intuitive...
So why would Get-ChildItem -Recurse | Remove-Item work, and how does it work?










share|improve this question















I've seen on a lot of places (for example, here, here, or here) where people suggest to use



Get-ChildItem -Path "Some path" -Recurse | Remove-Item


to recursively delete a directory, but why would this work?



When I run Get-ChildItem -Path "foo" -Recurse | % { "$_" }, I see directories were listed first, and then files follows.
It shows something like this:



1st_child_directory
2st_child_directory
...
1st_file_in_foo
2nd_file_in_foo
...
1st_file_in_1st_child_directory
2st_file_in_1st_child_directory
...
1st_file_in_2st_child_directory
...


And so on.



If these get piped into Remove-Item in the same order, then Remove-Item would remove directories first (which are still non-empty), and then remove files inside directories (but directories should already been removed), and this is a bit counter-intuitive...
So why would Get-ChildItem -Recurse | Remove-Item work, and how does it work?







powershell get-childitem






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '18 at 0:20

























asked Dec 28 '18 at 0:10









LanYi

3625




3625








  • 1




    Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
    – LotPings
    Dec 28 '18 at 0:31










  • You can find out: Create some sample directories and files and run the command, and see if it works or not.
    – Bill_Stewart
    Dec 28 '18 at 16:53














  • 1




    Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
    – LotPings
    Dec 28 '18 at 0:31










  • You can find out: Create some sample directories and files and run the command, and see if it works or not.
    – Bill_Stewart
    Dec 28 '18 at 16:53








1




1




Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
– LotPings
Dec 28 '18 at 0:31




Your examples have either the -Force parameter applied or use an extension *.csv which folders rarely have.
– LotPings
Dec 28 '18 at 0:31












You can find out: Create some sample directories and files and run the command, and see if it works or not.
– Bill_Stewart
Dec 28 '18 at 16:53




You can find out: Create some sample directories and files and run the command, and see if it works or not.
– Bill_Stewart
Dec 28 '18 at 16:53












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53952255%2fwhy-would-get-childitem-recurse-remove-item-work%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53952255%2fwhy-would-get-childitem-recurse-remove-item-work%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Mossoró

Error while reading .h5 file using the rhdf5 package in R

Pushsharp Apns notification error: 'InvalidToken'