This is just a heads up: when you use the phrase "in terminal" and you actually mean working in the bash shell or on the command line, you're using very misleading terminology.
In BSD UNIX, which is what Mac OS X is, you're talking about working in one of the shells. The same is true for UNIX, and Linux, and all the other UNIX like systems.
How Did You get Here:
The "terminal" is a bit of software that emulates a hardware device. Back before computers got cheap and powerful they were shared by multiple users sometimes hundreds of users at the same time. And each user used a device called a terminal to access the computer. The terminal was nothing more than a CRT tube, and enough electronics to manage a keyboard and draw some characters on the screen. There was also some additional line logic and the ability to send addresses to the terminal to move the cursor around and clear the screen.
That's pretty much all a terminal can do. Writing a program that is smart enough to tell up terminal how to do what and when, so that you can have something like a screen editor such as VI or Emacs is a fairly complex task because of terminal is a fairly dumb device. (Some were smarter than others)
As a hardware got more powerful and we started getting graphics capable displays, and UNIX had X Windows ported to it, we discovered we needed to emulate the old-fashioned hardware terminals in order to run the commandline interpreters, i.e. the shell. Originally called the Bourne shell after Stephen Bourne who implemented it, and then of course we had all the other shows that have been added since, like csh, korn shell, zsh, pdksh and zsh. plus the many others.
So the program people call "terminal" is one of those hardware terminal emulators and it is not a shell. It is not a command line interpreter. All it does is emulate an old piece of hardware. So you are not using "terminal commands".
Is this really important? Well I've already seen two people who didn't get job offers because they used this terminology in an interview.
Why? Because the way they used the terminology implied they didn't understand what they were doing.
For example the phrase "I did that in terminal." caused the interviewers to believe, (true or not), that the candidate simply basically misunderstood what the command line is, what a shell is, and what the basic operating paradigm of a UNIX system is. From the point of view of the UNIX literate person, this is incorrect usage and indicates that the person who used it is either uneducated, or unaware.
Using the word terminal as a replacement for shell, or bash etc. is going to cause people with more experience to perceive you as less educated, or unaware, or less intelligent.
So to prevent this unnecessary harm from happening, you should try not to use the word terminal when you are actually referring to working in a shell. Use of the wrong terminology, can be terminal in a job interview.
