Keeps typing CLS instead of clear? Well here is your fix...
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by TobiSGD
Sorry, but I fail to see the whole point of this discussion. The command is cls on Windows and clear on Linux. Full stop. If you are not able to handle those two simple commands when you have to work on both systems, how do you handle more complex commands? Isn't it counterproductive to set it up that way (thinking that it tricks your brain to assume you are on a Windows machine when you actually are not, just because a few Windows commands work)?
That's what I meant by confusing other users by doing it.
Edit: My apologies, I did say "mess things up for other users" earlier so was being a little silly in my phrasing, making it sound like a problem rather than a preference.
Wow you guys really into this stuff...
I just cassualy use linux as a dual boot off windows 7. I pretty much know nothing about linux and the termianl and found this helpfull to me (which is why I posted it in the newbie section)
I (hopefully not anyone) would change stuff like this if it was a system wide event like a main server... that is dumb, but its just for people with one computer, and doesnt know much about .bashrc (I never even kew it was there)
CLS is actually better if you think about it, (it doesnt mean your too dumb for even the simple things...) I hate to keep typing clear its un-comfortable... maybe ill just make it clearthisprompt who cares if you like it, use it. if not errrrrrr
Wow you guys really into this stuff...
I just cassualy use linux as a dual boot off windows 7. I pretty much know nothing about linux and the termianl and found this helpfull to me (which is why I posted it in the newbie section)
I (hopefully not anyone) would change stuff like this if it was a system wide event like a main server... that is dumb, but its just for people with one computer, and doesnt know much about .bashrc (I never even kew it was there)
CLS is actually better if you think about it, (it doesnt mean your too dumb for even the simple things...) I hate to keep typing clear its un-comfortable... maybe ill just make it clearthisprompt who cares if you like it, use it. if not errrrrrr
The parts highlighted in bold are the reasons why you should be putting this in your startup script, and not in a system-wide bin folder. As I said before, what if somebody else uses this system and wants "cls" to do something completely different than what you want it to do?
What if you get used to using cls all the time, and then set up a new server, or get access to another server? Are you going to request root access so you can stick your cls script into the system's bin? What if you use Linux quite a bit, and end up with 15 or 20 of these little one-liners in your bin folder? Are you going to scp all of them over to each machine you start to use, requiring root access for all of them?
It's so much easier and simpler to put a quick alias in your startup script. If you move to a new machine, scp your old startup script over and you're done. No root access required, and one easy startup script that contains all of these little tweaks.
TBOne,
The easiest way has already been given in 2nd and 4th post.
No, ONE easy way of doing it has been given in those posts. Others have also been given. And again, please stop posting what others have already posted.
There are pros and cons for ANYTHING. What I prefer on systems I administer may be different than what someone else prefers. BOTH methods work, and BOTH are equally effective (and pointless). I've never had a problem with using 'cls' system wide (in over 20 years of being an admin), and never have written a script that calls a clear or cls. Don't like the ln method? Don't use it. Simple.
Distribution: RHEL, CentOS, Debian, Oracle Solaris 10
Posts: 1,420
Rep:
Quote:
And again, please stop posting what others have already posted.
What I have posted again, that others have posted?
And ofcourse both methods work equally and effectively. And wouldn't it be good that the easiest method to use, saving time also. It depends on individual how they want to use a command. I just put my point of view. That's it!
What I have posted again, that others have posted?
This is not the thread or place to get into that. I suggest you look at your previous posts (not only in this thread), and find out.
Quote:
And ofcourse both methods work equally and effectively. And wouldn't it be good that the easiest method to use, saving time also. It depends on individual how they want to use a command. I just put my point of view. That's it!
Not sure what you mean by that sentence, as it's a bit confusing.
The parts highlighted in bold are the reasons why you should be putting this in your startup script, and not in a system-wide bin folder. As I said before, what if somebody else uses this system and wants "cls" to do something completely different than what you want it to do?
What if you get used to using cls all the time, and then set up a new server, or get access to another server? Are you going to request root access so you can stick your cls script into the system's bin? What if you use Linux quite a bit, and end up with 15 or 20 of these little one-liners in your bin folder? Are you going to scp all of them over to each machine you start to use, requiring root access for all of them?
It's so much easier and simpler to put a quick alias in your startup script. If you move to a new machine, scp your old startup script over and you're done. No root access required, and one easy startup script that contains all of these little tweaks.
So many what if's if cls isn't usable to some one than they can go cry about it elsewhere, there is olny an indefinite amount of other aliases out there, besides its my server... and if i were to use some one else's server with out a CLS than it would be quite easy to type CLEAR for the time being... And the only /bin modification I would be doing is on my own system...
If you knew it, why did I have to explain it to you?? You've been asked by myself and others to stop repeating what others have already posted, but you continue.
Please read previous replies to an OP's question, and if the advice has already been given, don't post it again.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by Sydney
I like ctrl and the letter l in Linux to clear the screen. Maybe that will be more convenient for some.
Thanks, I didn't know that despite coming into contact with unix and unixalikes for years. I think I prefer that to the muscle-memory typing it twenty times method.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.