I have Ubuntu 16.04. After some time of working, the terminal behavior has been changed:   "/" sign is not working "e" sign works the same as "↑" sign for  history navigation   What kind of mode is this? How to quit it?
85383
Update I can't even paste a b. I am trying to upgrade to Ubuntu 15.04 but I need to delete some files in the /boot directory. When I cd /oot I can't type a b. So, I thought, I will list the files in the / directory and copy/paste, but to no avail. I can't even paste a b. Update 2 I recently added some lines to the /etc/inputrc file in order to get better tab auto-completion: set completion-ignore-case on set show-all-if-ambiguous on TAB: menu-complete bind TAB:menu-complete   Original Question When I ssh into my ubuntu server I can't type the letter &quot;b&quot;. I can however type a capital &quot;B&quot; using either shift keys. I'm using a MacBook Pro with Retina display from 2012, and I'm ssh-ing into a custom built ubuntu box. It is here that I can't type a lower case &quot;b&quot;. I have restarted the server and yet I still can't type a &quot;b&quot;. Every other letter is fine. It hasn't done that before, I've had the server up and running for about two years and haven't come across an issue like this before. I also haven't done anything notable to cause it to do that. At first I thought the keyboard was a little sticky but when I closed the connection it works fine. I've restarted the server, ssh'd back in and the &quot;b&quot; key stops working again. I've tried my bluetooth keyboard and still no luck. Could this be something that is a rule in a .profile or .bashrc file or something similar? A setting to not allow certain characters. When I try to type the letter &quot;b&quot; I get the terminal bell sound as if it is not allowed.
25849
Can anyone tell me the difference between ctrl+z and ctrl+c?  When I am in the terminal, both the combinations stop the current process, but what exactly is the difference between both?
120878
I'm moving across from Mac OSX and am quite used to using the Cmd-Q shortcut to quit apps. I appreciate that Linux is set up differently and that different apps have different shortcuts for quitting (e.g. some use Ctrl-Q while others might be Alt-Q, etc.). I'm currently using Ubuntu GNOME.  Would it be possible to create a standard keyboard shortcut for quitting all apps easily and safely in Ubuntu? I'm happy to use a third-party tool or do a bit of further digging.  M
113935
I'm trying to write a function to replace the functionality of the exit builtin to prevent myself from exiting the terminal.  I have attempted to use the SHLVL environment variable but it doesn't seem to change within subshells:  $ echo $SHLVL 1 $ ( echo $SHLVL ) 1 $ bash -c 'echo $SHLVL' 2   My function is as follows:  exit () {     if [[ $SHLVL -eq 1 ]]; then         printf '%s\n' "Nice try!" &gt;&amp;2     else         command exit     fi }     This won't allow me to use exit within subshells though:  $ exit Nice try! $ (exit) Nice try!   What is a good method to detect whether or not I am in a subshell?
23391
I'm using Ubuntu 12.04, and till day before yesterday, the shortcut was working perfectly. But when today I pressed it, it didn't open terminal. The terminal app still works. I am on GNOME3 3.4.2, and I updated recently using apt-get install gnome-shell  The Keyboard shortcuts window shows no problem -    Pls. help, what should I do now?
107705
I use Terminal a lot, and sometimes I am running commands, which aren't things I don't want others to see, but more commands that if I accidentally arrowed up to and accidentally executed would cause a lot of trouble.  So I am wondering if there is, or I can make, some sort of Terminal 'incognito mode' which would allow me to, upon the execution of a certain command, stop recording my history, and then only start recording after I either execute a start recording history again command and exit 'incognito mode', or I simply restart the Terminal?  Because I find myself later on going and removing stuff from my .bash_history, when it would be much easier if I could have stopped it recording there in the first place, or at least got it to try to record it somewhere where it just wouldn't be allowed to, and would just end up not recording it.
88479
Is it possible to quit applications while switching through them with Alt+Tab? When I used a Mac many years ago and you were switching through open applications with (let's say Command+Tab) you could let go off tab and then hit Q to quit the app.  How can I do this same thing in Ubuntu 14.04?
108138
I'm learning about Linux, started yesterday. I have a question which I couldn't answer from my book or Google. What is the difference between  ./ and / in the shell?  I'm asking this because when I run, for example, the command ./home/yogesh/Desktop/Books, I get this error:  bash: ./home/yogesh/Desktop : No such file or directory   However, on removing the dot it gives  /home/yogesh/Desktop/Books : Is a directory   Or, if I run /Desktop, it returns   /Desktop : No such file or directory   But on adding a dot before /, I get  ./Desktop: is a directory   What is the difference between ./ and /?
99423
Is there a way that I can stop the Ctrl+Alt+F4 key combination from switching to a virtual terminal?  I still want the other key combinations to switch to terminals - I just want to change the F4 one because I often use that keyboard shortcut in a Windows VM.
64487
OS X terminal is not using colors for highlighting output from different commands, for example ls.   When compared with other systems like Ubuntu, this is a big loss of accessibility/productivity.  What solutions do I have to improve this experience? For the moment I found only this guide for  but I am looking for a more complete solution.
65697
I accidentally executed the following command on the etc directory:  sudo chmod -R 700 /etc   I know that I have done something very wrong. My terminal now prints:  I have no name!@ubuntu: /$   How can I revert my etc directory to its earlier state?  I tried changing the permissions but it is failing now. Also, it would be very helpful if someone can explain what actually went wrong when I executed that command on etc. It was only file permissions. Then why does the whole system seems completely blown up? Why is it that no login passwords are working now? I know that there is a file in etc directory that has to do with users. But how did changing permissions jeopardize everything? Some technical details about this would be very helpful.
30406
I have a simple one line command which works perfectly in terminal, but does not work in the "Startup Applications" app thing.  The line of code is : xmodmap /home/seph/Code/Ubuntu\ Scripts/Xmodmap  It's not that much of a hassle to copy it from "Startup Applications" and paste it into terminal, but I don't really get why it isn't working.  I followed someone else's instructions to do it in the first place, so maybe I did something wrong?  In any case, wouldn't it be the obvious and logical assumption that it just types whatever you put in it into Terminal?
94237
I was trying to find how to pass some text to a file without overwriting what's there already using the > command and I realised I don't know what it's called. Searching for right arrow or right chevron or more than command didn't show up anything. I've always just called it pass to.
87833
I switched to zsh completely on a previous arch install and I LOVED it mainly because arch is one of the distros that capitalizes your Documents, Downloads, Music and such directories in your ~ directory. Since I wasn't used to that and I use tab completion for almost everything in the terminal zsh was like heaven for me compared to bash.... I swear this feature used to be active automatically because I don't remember having to tweak anything to make it work that way. I probably figured it out on accident. xD But I would greatly like to have this feature restored on my new pc using zsh as my main shell, and if anyone knows how to do this I would really appreciate a reply. I tried activating every option in the completion configuration and that didn't seem to do the trick... so that brought me here. PS: I used to be a lot more up to date with my Linux know-how, and my knowledge has grown stale... I'm trying to remedy that... (without the use of the shift key, as much as possible... haha)
1049
I use Ubuntu on a daily basis, recently I've seen that the terminal on Kali Linux behaves differently from the terminal on Ubuntu... I can see the end of the command that I'm typing based on the history of commands that I've typed like the following:  I know I can use autocompletion by pressing tab, but this feature is something else since I can see the command before pressing tab... That's not a Kali related question too since I just want to replicate this feature on Ubuntu 20.04. Is it a feature that I can easily install on Ubuntu by installing some tool with apt install? Or is it a configuration that I need to do?
789
Something I have noticed in Ubuntu for a long time that has been frustrating to me is when I am typing a command at the command line that gets longer (wider) than the terminal width, instead of wrapping to a new line, it goes back to column 1 on the same line and starts over-writing the beginning of my command line. (It doesn't actually overwrite the actual command, but visually, it is overwriting the text that was displayed).  It's hard to explain without seeing it, but let's say my terminal was 20 characters wide (Mine is more like 120 characters - but for the sake of an example), and I want to echo the English alphabet.  What I type is this:  echo abcdefghijklmnopqrstuvwxyz   But what my terminal looks like before I hit the  key is:  pqrstuvwxyzghijklmno   When I hit enter, it echos  abcdefghijklmnopqrstuvwxyz   so I know the command was received properly.  It just wrapped my typing after the "o" and started over on the same line.    What I would expect to happen, if I typed this command in on a terminal that was only 20 characters wide would be this:  echo abcdefghijklmno pqrstuvwxyz   Background: I am using bash as my shell, and I have this line in my ~/.bashrc:  set -o vi   to be able to navigate the command line with VI commands.  I am currently using Ubuntu 10.10 server, and connecting to the server with Putty.  In any other environment I have worked in, if I type a long command line, it will add a new line underneath the line I am working on when my command gets longer than the terminal width and when I keep typing I can see my command on 2 different lines.  But for as long as I can remember using Ubuntu, my long commands only occupy 1 line.  This also happens when I am going back to previous commands in the history (I hit Esc, then 'K' to go back to previous commands) - when I get to a previous command that was longer than the terminal width, the command line gets mangled and I cannot tell where I am at in the command.  The only work-around I have found to see the entire long command is to hit "Esc-V", which opens up the current command in a VI editor.  I don't think I have anything odd in my .bashrc file.  I commented out the "set -o vi" line, and I still had the problem.  I downloaded a fresh copy of Putty and didn't make any changes to the configuration - I just typed in my host name to connect, and I still have the problem, so I don't think it's anything with Putty (unless I need to make some config changes)  Has anyone else had this problem, and can anyone think of how to fix it?  Edit  It was my .bashrc file.  I've copied the same profile from machine to machine, and I used special characters in my $PS1 that are somehow throwing it off.  I'm now sticking with the standard bash variables for my $PS1.  Thanks to @ændrük for the tip on the .bashrc!  ...End Edit...
24524
Is there any way to disable Command+W in the terminal?   On several occasions I have accidentally closed a terminal window containing important information when I meant to close a Safari tab and did not realize that the terminal was the active window.