While using the terminal I accidentally typed Cmd + up-arrow and saw that my previous commands got highlighted. I was wondering if I accidentally discovered a cool hack for something (other than just highlighting previous commands), but I wasn't able to figure out what exactly the hot key is doing.
Related
I'm trying to setup the terminal on my new Mac to match the behavior of my old Mac, however I have run into an issue with my multiline prompt that has me stumped. I remember having this issue when I setup my old Mac several years ago, however I don't remember how I solved it.
My prompt (without color) looks like this:
╭─username ~ 130 ↵
╰─
When I press ⌘commandK in iTerm2 on my old Mac it clears the terminal window so that both lines of the prompt are shown at the top.
When I press ⌘commandK in iTerm2 on my new Mac it clears the terminal window so that only the second line of the prompt is shown at the top.
I have tried checking everything I could think of, I have checked:
Every dot file/directory in my home directory (copied them to the new Mac).
iTerm2 settings.
System settings (primarily keyboard shortcuts).
Various websites with instructions about setting up multi-line prompts.
Interestingly I have discovered that if I type clear iTerm2 will clear the screen and leave the top line showing on both Macs. However it first clears the entire screen, including the prompt, before bringing the prompt back (looks bad imo). However since it works differently ⌘commandK does I don't think that's what my old Mac is doing.
It's possible that I installed some program/script that somehow does this, but if so I'm not finding it locally or referenced online.
Does anyone know how I can get ⌘commandK working to clear the screen while keeping the top line of my prompt? I still have the old Mac so I can check/compare anything on it to the new Mac if there are any guesses about what settings I changed.
Edit:
I was able to find something that worked, however if anyone has any other suggestions I'll be happy to try them and accept any that I can make work that are less hacky than this (e.g. don't require another 3rd party app).
Edit: This doesn't work while a command is running, nor does it clear the scrollable history. So it's better than nothing but still doesn't behave like I want it to.
After coming back to my question SO associated a new question with an answer I was able to make work, although it feels extra hacky and wasn't what I had working before.
I found this answer which suggests using ⌃controlL to clear the screen. That does exactly what I want it to do (leaves the top prompt visible and doesn't flash) but with the wrong keybinding. Fortunately I was able to use an app I already have installed (BTT) to make ⌘commandK map to ⌃controlL only in iTerm2.
When I'm using vim alone, it's fine. I can suspend it by pressing Ctrl+z, work with bash, then return by typing fg.
When I'm trying to use vim along with gnu-screen, it's buggy.
First, pressing Ctrl+z does not show me all previous commands in console, it shows remains of vim screen instead(see pic).
Second, and worse, hotkeys, starting with Ctrl does not work in Vim. For example, Ctrl+PgUp to see previous tab.
Am I doing something wrong?
Previously, my PowerShell client would clear all text upon pressing Ctrl+L, effectively executing a clear/cls.
Seemingly out of the blue Ctrl+L clears the terminal but upon typing, all the text comes back to fill the prompt.
How may I go about debugging this issue? Using "Enable legacy console" fixes it, but I'd rather use latest. I could always override the Ctrl+L chord but I'd rather try and determine how it got to this state in the first place.
I am playing around a little with the mongo shell, but I have quite a tedious problem.
After I've switched to the database I'm working with using "use nameOfDatabase", and I issue my first command, the shell won't respond to any further commands after giving me the first response. I have to CTRL + C or CTRL + Z out of it, reconnect, switch to the db again and then issue another command to keep working.
Also, accessing commands from the history does not work since this just moves the cursor around the shell window (this also makes the shell stop responding).
Anyone have any ideas what might be wrong?
Ctrl+Z is for 'suspend'. Try Ctrl+D to exit the mongo prompt.
I recently got a mac. I was previously working on a laptop with ubuntu and I was using vim.
I now will discuss about vim in console (iTerm2 or the default terminal) and macvim.
The problem is that some binding don't work under mac. For example I had CTRL left/right for navigating between splits, CTRL up/down to move lines or blocks of code up and down, etc. They don't work anymore.
I had a bunch of plugins (nerdtree, powerline, etc.) that now look weird. Powerline doesn't display special characters in macvim and in terminal they are question marks.
In console, nerdtree looks weird and it doesn't display the special triangle character. If I hit return to open a file selected from nerdtree, it doesn't do anything. In macvim, it works ok.
Is there any guide on how to use vim on mac? Or what is the recommended way?
Nerdtree : let g:NERDTreeDirArrows=0
Powerline : Take a look at the part of strange characters in the document https://github.com/Lokaltog/vim-powerline
Navigating within splits with Ctrl + arrows work on mine. Can you post your vimrc, or try running vim without any configuration.
Ctrl+arrows to move lines and block doesn't work on mine.
Did you check which key was sent by your terminal to vim ?
Did you tried to set it manually ?
I had similar problems with emacs, including one keybinding I'm still not able to reproduce :(
I have the exact same config on my Mac and a Windows box at work, my Ubuntu box at home and a couple of VPSes. It works exactly the same on every platform in GVim/MacVim or in plain Vim.
Unfortunately I don't use either NERDTree nor Powerline but Vdt's answer seems to have all the info needed.
Some of the behaviors you describe are custom mappings. You should show us your ~/.vimrc (the old one on linux and the new one on the Mac, if there are differences) so that we can help you make it more portable.
Also, "looks weird" means nothing: please add a screenshot or two.