Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
But no success. Any help is appreciated thank you.
Solution:
Quote:
Code:
rm ~/"Da File"
Reasons explained in the BASH reference guide (or man bash at your pleasure):
Quote:
If a word begins with an unquoted tilde character (‘~’), all of the characters up to the first unquoted slash (or all characters, if there is no unquoted slash) are considered a tilde-prefix.
Last edited by youarefunny; 05-27-2010 at 04:44 PM.
Reason: Solved
Reasons explained in the BASH reference guide (or man bash at your pleasure):
Quote:
If a word begins with an unquoted tilde character (‘~’), all of the characters up to the first unquoted slash (or all characters, if there is no unquoted slash) are considered a tilde-prefix.
Yes. If enclosed in double quotes ~ retains its literal meaning. If not quoted, bash performs tilde expansion and considers the tilde-prefix up to the first unquoted /. This means that in commands like
Code:
ls ~user/directory/*.png"
ls ~user/"dir with spaces"/*.ps"
ls ~user
~user is the tilde-prefix expanded to the user's home, whereas in
Code:
ls ~"user"
ls ~"/dir with spaces"
nothing is treated as a tilde-prefix and therefore there isn't any tilde expansion.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.