"Selection of current command" needs explanation of framing/dimming in Settings UI
The option "Clicking on a command selects it to restrict Find and Filter" needs more explanation in the UI. It neglects to mention the intrusive effects of highlighting the current command, putting a frame around it, and dimming the rest of the pane. This means that searching for the option by typing things like "current command" into the search box, in order to find this option, does not work. (It only gives the Advanced option for setting the dimming value.)
I finally figured out what it was by Googling (result here). As with the other people there, I was having it activate much too often unintentionally just by clicking on iTerm.
Very strangely, it does not do the dimming etc. on my other computer (running same versions of MacOS and iTerm), even though the option is turned on. (Doing some experimenting with the Find restriction shows me it could be very useful -- but I don't want a single click to turn it on, for me it comes up way to often when I don't want it to.)
Thanks!
Thanks for filing an ! Please answer the questions below so I can help you.
- iTerm2 version: Build 3.5.4
- OS version: 15.0 Beta (24A5331b)
- Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) Done.
- Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog
- Attach a screen capture video if it would make the reproduction steps clearer.
- Are you reporting a performance , excessive CPU usage, or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
- Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs
- Are you reporting excessive memory usage? Please attach a heap analysis: https://gitlab.com/gnachman/iterm2/wikis/heapshot
PLEASE ATTACH YOUR PLIST FILE FOR BUG REPORTS! Seriously! I'll probably ask you for it if you don’t.
NOTE: Your plist file may contain private information. Mark the issue private to avoid sharing it with the world. Alternately, email the plist to gnachman@gmail.com and include the issue number in the subject line.
Detailed steps to reproduce the problem: 1. 2. 3.
What happened:
What should have happened: