From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Using rm -rf scares me. Is there a reasonable way to delete git repos without it?
I don't know what to tell you, that's the command you need to use.
If you're that worried you're going to nuke important stuff, make backups, and don't use sudo for user files.
So.... you're afraid of the command that does the thing you're trying to do?
More like, I'm afraid of the command doing more than I'm trying to do.
What I want to do is ignore prompts about write-protected files in the .git directory, what it does is ignore all prompts for all files.
You just need to do this then
cd git-project
rm -rf .git
cd ..
rm -r git-project
With rm -r is for (R)ecursion and -f is for F(force) disabled the prompting. So, use -f on the .git directory which has the files you want to obliterate, and leave it off for the safety prompts.
so why not rm -rf folder/.git/* then rm -r folder/*
Maybe they're afraid of accidentally writing rm -rf folder/.git /* or something
That's a good example. If I'm regularly running a command that is a single whitespace character away from disaster, that's a problem.
Imagine a fighter aircraft that had an eject button on the side of the flight stick. The pilot complains "I'm afraid I might accidentally hit the eject button when I don't need to", but everyone responds "why would you push the eject button if you don't want to eject?", or "so your concern is that the eject button will cause you to eject...?" -- That's how I feel right now.
I understand the mindset you have, but trust me, you'll learn (sooner or later) a habit to pause and check your command before hitting enter. For some it takes a bit longer and it'll bite you in the butt for few times (so have backups), but everyone has gone down that path and everyone has fixed their mistakes now and then. If you want hard (and fast) way to learn to confirm your commands, use dd a lot ;)
One way to make it a bit less scary is to 'mv /tmp' and when you confirmed that nothing extra got removed you can 'cd /tmp; rm -rf ', but that still includes the 'rm -rf' part.
How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like "Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?"
In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that's managed by the flight computer.
Are you regularly deleting git repos?
Generally that is not a concern because regular users won't be able to rm anything else other than those in his own $HOME.
Another thing I want to say is, command line is for careful users. If someone is careless, they should create a wrapper around rm, or just use a FM.
If someone is careless, they should create a wrapper around rm, or just use a FM.
I think that's the situation OP is in.. They don't trust themself with these kinds of commands, while other commenters here are trying to convince them that they should just use rm -rf anyway
What about adding the flags last?
rm deletethisrepo -rf
chmod -R the directory first?
This, lol just remove write protection if -f is too spooky
Maybe use a graphical file manager?
Or move the folder to /tmp or so.
Or a tui file manager like ncdu
The problem is that rm -rf shouldn't scare you?
What are the chances something like
~/projects/some-project $ cd ..
~/projects $ rm -fr some-project
may delete unexpected stuff? (especially if you get into the habit of tab-completing the directory argument)
A tip I saw some time ago is to do:
rm folder -rf
Additionally you could move the git folder to the trash folder. I think it's usually located at $HOME/.local/share/trash/files/
Then you can delete it from the trash once you're certain you got the right folder
Additionally you could move the git folder to the trash folder. I think it's usually located at $HOME/.local/share/trash/files/
Moving something to the trash files folder isn't the correct way to trash it, since the Trash specification requires storing some metadata for each trash item.
You should use eg. trash-cli instead.
xdg-trash
Use rm -rf. If you are scared of mistakes, type echo rm -rf nameofdirectory, check it, go back, delete the echo and press enter.
If you’re that worried, why not run chmod -R u+w .git inside the project dir to “un write-protect” the files, then just ascend to the directory containing the project dir (cd ..) and use rm -r without -f?
The force flag (-f) is the scary one, I presume?
chmod -R 777 my_project_managed_by_git && rm -r my_project_managed_by_git
Cd into the directory first, then run rm -rf, then cd back out and rm -r just the directory.
E:fb
You should have backups. Preferably also snapshots. Then rm will feel less scary.
its a bit verbose but my preference is rm -r --interactive=never directoryname
i really try to avoid rf for myself
If you're scared to do rm -rf, do something else that lets you inspect the entire batch of deletions first. Such as:
find .git ! -type d -print0 | xargs -0 -n1 echo rm -fv
This will print out all the rm -fv commands that would be run. It's basically rm -rf --dry-run, but rm doesn't have that common option. Once you've verified that that's what you want to do, run it again without echo to do the actual deletion. If you're scared of having that in your history, either use a full path for .git, or prepend a space to the non-echo version of the command to make it avoid showing up in your shell history (assuming you have ignorespace in your HISTCONTROL env var)
I use this xargs echo pattern a lot when I'm crafting commands that are potentially destructive or change lots of things.
You can use ls <PATH> first to check you are deleting the right files. I do this and I've never accidentally deleted the wrong files (using rm).
use relative paths (cd into the directory below your repository) and use tab completion, and you won't have problems.
honestly I don't think there is a better way, like others have said you can use a trash program or you can chmod the git directory before deleting but, I would recommend against the comments saying alias the command, that can lead to even bigger problems if you typo thr alias or mess up in the script. rf can't break anything unless you say the wrong directory which would be the same with aliases anyway,
My recommendation out of them all would be using a trash program to move it to the trash that way if you do screw up the location you have a way to restore it otherwise you could make a script to list the files affected using ls and then prompt a yes/no prompt using read before doing the rm script, but that's something you definitely want to test in a sandbox or user restricted environment if you're not used to scripting in case something breaks
OSX - mv my_project ~/.Trash
git rebase doesn't work?
That or an oil change