iterm2 issueshttps://gitlab.com/gnachman/iterm2/-/issues2015-05-01T20:05:44Zhttps://gitlab.com/gnachman/iterm2/-/issues/3452iterm2 appears to be leaking memory2015-05-01T20:05:44ZGeorge Nachmaniterm2 appears to be leaking memory*By j\.\.\.@sysmgr.org on March 16, 2015 05:51 (imported from Google Code)*
---
I've been running the latest nightly build for months, and have been experiencing what seems to be a memory leak. I have run iTerm under Instruments and h...*By j\.\.\.@sysmgr.org on March 16, 2015 05:51 (imported from Google Code)*
---
I've been running the latest nightly build for months, and have been experiencing what seems to be a memory leak. I have run iTerm under Instruments and have noticed a pattern.
I am "discarding events for freed memory", and just looking at the categories of allocation for which the Persistent# increases over time. After around 35 minutes of operation, there are ~35000 persistent objects in the "NSTrackingArea" category. Drilling down into the call tree, and pruning the paths that only had a couple of persistents, it seems that they're basically all coming out of [PSMTabBarControl _setupCells]. Screenshot attached.
I should note: I have a few split panes open, two of which redraw at least once a second (tmux with a HH:MM:SS clock status bar).
Other Details:
- Yosemite (10.10.2), though this has been happening on 10.9 as well.
- iTerm 2.9.20150309-nightly at present
- plist attached
Please let me know what data I should gather, or how else I can help out. Thanks!
---
![instruments01.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3452/comment-0/instruments01.png)
[ITERM2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3452/comment-0/ITERM2.plist)https://gitlab.com/gnachman/iterm2/-/issues/3451Fix keydown handling for AquaSKK2016-05-15T02:26:08ZGeorge NachmanFix keydown handling for AquaSKK*By mzp\.\.\. on March 15, 2015 12:11 (imported from Google Code)*
---
This patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Instal...*By mzp\.\.\. on March 15, 2015 12:11 (imported from Google Code)*
---
This patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Install AquaSKK.
2. Give focus a window of iTerm2 and make AquaSKK enable.
3. Change the mode to Japane Hirakana Input mode.
4. Press l to turn on ASCII input mode.
<b>What is the expected output?</b>
\--
The [A] icon with orange background is displayed at the location by the cursor in an iTerm window, and any characters are not inputted in the iTerm window.
<b>What do you see instead?</b>
\--
The [あ] icon with orange background is displayed at the location by the cursor in an iTerm window, and a newline character is inputted in the iTerm window.
<b>What version of iTerm2 are you using?</b>
\--
0232ba490ba855ca34bc23446bb1e6e13d7cfab9
<b>What OS version are you using?</b>
\--
MacOS X 10.10.2
<b>Please provide any additional information below.</b>
\--
This is caused, because This patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Install AquaSKK.
2. Give focus a window of iTerm2 and make AquaSKK enable.
3. Change the mode to Japane Hirakana Input mode.
4. Press l to turn on ASCII input mode.
<b>What is the expected output?</b>
\--
The [A] icon with orange background is displayed at the location by the cursor in an iTerm window, and any characters are not inputted in the iTerm window.
<b>What do you see instead?</b>
\--
The [あ] icon with orange background is displayed at the location by the cursor in an iTerm window, and a newline character is inputted in the iTerm window.
<b>What version of iTerm2 are you using?</b>
\--
0232ba490ba855ca34bc23446bb1e6e13d7cfab9
<b>What OS version are you using?</b>
\--
MacOS X 10.10.2
<b>Please provide any additional information below.</b>
\--
This is caused, because _inputMethodIsInsertingThis patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Install AquaSKK.
2. Give focus a window of iTerm2 and make AquaSKK enable.
3. Change the mode to Japane Hirakana Input mode.
4. Press l to turn on ASCII input mode.
<b>What is the expected output?</b>
\--
The [A] icon with orange background is displayed at the location by the cursor in an iTerm window, and any characters are not inputted in the iTerm window.
<b>What do you see instead?</b>
\--
The [あ] icon with orange background is displayed at the location by the cursor in an iTerm window, and a newline character is inputted in the iTerm window.
<b>What version of iTerm2 are you using?</b>
\--
0232ba490ba855ca34bc23446bb1e6e13d7cfab9
<b>What OS version are you using?</b>
\--
MacOS X 10.10.2
<b>Please provide any additional information below.</b>
\--
This is caused, because `_inputMethodIsInserting is not enough. AquaSKK use This patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Install AquaSKK.
2. Give focus a window of iTerm2 and make AquaSKK enable.
3. Change the mode to Japane Hirakana Input mode.
4. Press l to turn on ASCII input mode.
<b>What is the expected output?</b>
\--
The [A] icon with orange background is displayed at the location by the cursor in an iTerm window, and any characters are not inputted in the iTerm window.
<b>What do you see instead?</b>
\--
The [あ] icon with orange background is displayed at the location by the cursor in an iTerm window, and a newline character is inputted in the iTerm window.
<b>What version of iTerm2 are you using?</b>
\--
0232ba490ba855ca34bc23446bb1e6e13d7cfab9
<b>What OS version are you using?</b>
\--
MacOS X 10.10.2
<b>Please provide any additional information below.</b>
\--
This is caused, because `_inputMethodIsInserting` is not enough. AquaSKK use lThis patch is related with https://code.google.com/p/iterm2/issues/detail?id=2629 but not same.
<b>What steps will reproduce the problem?</b>
\--
1. Install AquaSKK.
2. Give focus a window of iTerm2 and make AquaSKK enable.
3. Change the mode to Japane Hirakana Input mode.
4. Press l to turn on ASCII input mode.
<b>What is the expected output?</b>
\--
The [A] icon with orange background is displayed at the location by the cursor in an iTerm window, and any characters are not inputted in the iTerm window.
<b>What do you see instead?</b>
\--
The [あ] icon with orange background is displayed at the location by the cursor in an iTerm window, and a newline character is inputted in the iTerm window.
<b>What version of iTerm2 are you using?</b>
\--
0232ba490ba855ca34bc23446bb1e6e13d7cfab9
<b>What OS version are you using?</b>
\--
MacOS X 10.10.2
<b>Please provide any additional information below.</b>
\--
This is caused, because `_inputMethodIsInserting` is not enough. AquaSKK use `l for changing input mode. So AquaSKK doesn't insert any text, but consume it.
To handle this, I add check for keybord type.
---
[aquaskk.patch](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3451/comment-0/aquaskk.patch)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3450Maximized window resizes when closing all but the first tab2017-07-01T19:40:11ZGeorge NachmanMaximized window resizes when closing all but the first tab*By yoaquim.cint\.\.\. on March 14, 2015 23:25 (imported from Google Code)*
---
<b>** READ THIS! **</b>
<b>Your report will not be accepted if you don't follow these instructions.</b>
<b>Seriously.</b>
<b>1) Attach your ~/Libr...*By yoaquim.cint\.\.\. on March 14, 2015 23:25 (imported from Google Code)*
---
<b>** READ THIS! **</b>
<b>Your report will not be accepted if you don't follow these instructions.</b>
<b>Seriously.</b>
<b>1) Attach your ~/Library/Preferences/com.googlecode.iterm2.plist to this</b>
<b>issue.</b>
***NO "com.googlecode.iterm2.plist" IN MY /tmp DIR***
<b>2) Create a debug log while reproducing the issue. Instructions are here:</b>
<b>https://code.google.com/p/iterm2/wiki/DebugLogging</b>
<b>3) If you are reporting a performance problem, do this:</b>
<b>https://code.google.com/p/iterm2/wiki/HowToSample</b>
<b>What steps will reproduce the problem?</b>
1.Open more than 1 tab in iTerm2.
2.Maximize window size (NOT fullscreen, using Slate for maximizing, but also used other tools: BTT, Size-Up)
3.Close all but the first tab
<b>What is the expected output?</b>
Tabs close normally; window isn't resized;
<b>What do you see instead?</b>
Once maximized, if you close all but the last tab, the window resizes about 100 pixels from the bottom of the maximized area up; have to re-maximize.
<b>What version of iTerm2 are you using?</b>
Build 2.0.0.20141103
<b>What OS version are you using?</b>
OSX Yosemite, v10.10.2 (14C1510)
<b>Please provide any additional information below.</b>
---
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3450/comment-0/debuglog.txt.gz)
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3450/comment-0/com.googlecode.iterm2.plist)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3448More window control in "tmux Dashboard"2017-09-22T13:48:23ZGeorge NachmanMore window control in "tmux Dashboard"*By m\.\.\.@camooflage.com on March 10, 2015 16:49 (imported from Google Code)*
---
Some of these enhancements would be fantastic for tmux users.
1) when a user selects a window, change the highlighted window in the dashboard to m...*By m\.\.\.@camooflage.com on March 10, 2015 16:49 (imported from Google Code)*
---
Some of these enhancements would be fantastic for tmux users.
1) when a user selects a window, change the highlighted window in the dashboard to match the same window.
2) context menu for window items in the tmux dashboard
2A) focus
2B) Hide
2C) Open Window
3) double click on Window name in dashboard: opens window if not open, raises window and sets focus.
These features would let me to the same with tmux that I do with /usr/bin/screen CTRL-A "
Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3447creating new tmux window via DashBoard causes some or all hidden windows to b...2015-05-01T20:04:54ZGeorge Nachmancreating new tmux window via DashBoard causes some or all hidden windows to become visible*By m\.\.\.@camooflage.com on March 10, 2015 16:30 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. start a new tmux session (tmux -CC)
2. open dashboard
3. hit the &quot;+&quot; key to open some ...*By m\.\.\.@camooflage.com on March 10, 2015 16:30 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. start a new tmux session (tmux -CC)
2. open dashboard
3. hit the "+" key to open some new windows
4. select each window in Dashboard and click "Hide"
5. hit the "+" key to open a new window
<b>What is the expected output?</b>
a single new window should appear
<b>What do you see instead?</b>
The window is created, but one or more of the hidden windows is opened too.
<b>What version of iTerm2 are you using?</b>
2.9.20150305-nightly
<b>What OS version are you using?</b>
OS X 10.9.5 Build 13F1066
<b>Please provide any additional information below.</b>
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3447/comment-0/com.googlecode.iterm2.plist)
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3447/comment-0/debuglog.txt.gz)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3445Show Hide Terminal window should have option to follow mouse focus2015-04-30T19:18:32ZGeorge NachmanShow Hide Terminal window should have option to follow mouse focus*By phin\.\.\. on March 06, 2015 19:16 (imported from Google Code)*
---
I am looking to find a way to get iTerm2 to follow mouse focus when I use the Show/Hide window option. No matter what options I have attempted to select, it seems...*By phin\.\.\. on March 06, 2015 19:16 (imported from Google Code)*
---
I am looking to find a way to get iTerm2 to follow mouse focus when I use the Show/Hide window option. No matter what options I have attempted to select, it seems as if it wants to always show in Screen 1. I run 3 monitors and this can be a tad cumbersome.
Thank you
iTerm2 Version: 2.0.0.20141103Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3442vim - scrolling with touchpad + shift shortcuts for text selection in terminal2015-05-01T20:04:39ZGeorge Nachmanvim - scrolling with touchpad + shift shortcuts for text selection in terminal*By tomasnove\.\.\. on March 05, 2015 11:49 (imported from Google Code)*
---
Hey,
I have this feature request to make working with iterm2 even more confortable.
currently i use Build 2.0.0.20141103
1. when i open vim, i'd l...*By tomasnove\.\.\. on March 05, 2015 11:49 (imported from Google Code)*
---
Hey,
I have this feature request to make working with iterm2 even more confortable.
currently i use Build 2.0.0.20141103
1. when i open vim, i'd like to be able to scroll in it via touchpad (with 2 fingers, like in a browser). now it doesnt do anything.
2. i'd like to be able to selct text even with keyboard with a simple shift+arrow. now instead, it just writes ;2D and ;2C chars into the prompt
thank you and best wishes :)https://gitlab.com/gnachman/iterm2/-/issues/3436Save environment vars on app exit and load them on restart2015-05-01T20:04:14ZGeorge NachmanSave environment vars on app exit and load them on restart*By efi.plot\.\.\. on March 02, 2015 14:51 (imported from Google Code)*
---
For each session, it would be nice if — in addition to saving and restoring its output — there would be a way to save and restore the environment.
Going ...*By efi.plot\.\.\. on March 02, 2015 14:51 (imported from Google Code)*
---
For each session, it would be nice if — in addition to saving and restoring its output — there would be a way to save and restore the environment.
Going further, paying special attention to $PS1, $PWD, etc., it would be a great step towards getting the user in exact the same spot the user was before the restart.
(I am not restarting my Mac all too frequent, but I'm on the nightly build and it updates itself every now and then.)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3435iTerm2 Shell Integrations don't play well with show-mode-prompt in Bash2017-07-31T05:24:58ZGeorge NachmaniTerm2 Shell Integrations don't play well with show-mode-prompt in Bash*By magic\.\.\.@overblown.net on February 27, 2015 01:25 (imported from Google Code)*
---
Recent versions of Bash (&gt;= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding Recent versions of Bash (&gt...*By magic\.\.\.@overblown.net on February 27, 2015 01:25 (imported from Google Code)*
---
Recent versions of Bash (>= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding Recent versions of Bash (>= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding set show-mode-prompt onRecent versions of Bash (>= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding `set show-mode-prompt on to your ~/.inputrc or /etc/inputrc file will cause Bash to prepend your prompt with a character indicating the current Readline mode: "@" for emacs, ":" for vi command, or "+" for vi insertion.
I've found that if I have iTerm2's shell integrations installed, then my prompt will be re-displayed every time the mode character changes.
The expected behavior is that, with Recent versions of Bash (>= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding `set show-mode-prompt on` to your ~/.inputrc or /etc/inputrc file will cause Bash to prepend your prompt with a character indicating the current Readline mode: "@" for emacs, ":" for vi command, or "+" for vi insertion.
I've found that if I have iTerm2's shell integrations installed, then my prompt will be re-displayed every time the mode character changes.
The expected behavior is that, with set editing-mode viRecent versions of Bash (>= 4.3, I believe) have added support for the Readline option 'show-mode-prompt'. Adding `set show-mode-prompt on` to your ~/.inputrc or /etc/inputrc file will cause Bash to prepend your prompt with a character indicating the current Readline mode: "@" for emacs, ":" for vi command, or "+" for vi insertion.
I've found that if I have iTerm2's shell integrations installed, then my prompt will be re-displayed every time the mode character changes.
The expected behavior is that, with `set editing-mode vi in my ~/.inputrc, my prompt will start with a "+" in front of it. Then, if I press "esc" to enter vi command mode, that "+" will turn into a ":", without anything else changing.
Instead, with the shell integrations installed, my shell opens with "+" displayed on the line above my prompt, not next to it. Then, when I press "esc", a ":" character overwrites the first character of my current prompt, then my cursor moves down a line my prompt is re-printed (without any mode character). If I have text on the current line and change modes, my cursor is still in the same horizontal position, but moved down vertically.
I am running "Build 2.9.20150224-nightly" on Mac OS X 10.9.5. My Bash version is "4.3.33(1)-release", and my Readline version is "stable 6.3.8 (bottled)", both installed via HomeBrew.
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3435/comment-0/com.googlecode.iterm2.plist)
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3435/comment-0/debuglog.txt.gz)Review for next versionhttps://gitlab.com/gnachman/iterm2/-/issues/3433Support xterm compatibility for proprietary escape codes2018-09-30T11:16:56ZGeorge NachmanSupport xterm compatibility for proprietary escape codes*By sbuzo\.\.\.@fancyguy.com on February 26, 2015 04:01 (imported from Google Code)*
---
This in regards to https://code.google.com/p/iterm2/wiki/ProprietaryEscapeCodes
The xterm+tmux termcap defines escape sequences for man...*By sbuzo\.\.\.@fancyguy.com on February 26, 2015 04:01 (imported from Google Code)*
---
This in regards to https://code.google.com/p/iterm2/wiki/ProprietaryEscapeCodes
The xterm+tmux termcap defines escape sequences for manipulating the clipboard, cursor shape, and cursor color.
Ms (modify selection/clipboard) works a little bit differently, but I think it's fine as is. I don't think there is wide support for this functionality, more of a capability advertisement to discover the escape codes. Adding selection capability would be a nice to have.
Cs and Cr set and reset the cursor color. iTerm2 is missing the reset counterpart.
Ss and Se set and reset the cursor shape. Same as the cursor color, the reset capability is missing.Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3431Provide distinction between modifiers.2015-05-01T20:03:16ZGeorge NachmanProvide distinction between modifiers.*By sbuzo\.\.\.@fancyguy.com on February 26, 2015 01:35 (imported from Google Code)*
---
I want to be able to map keys differently depending on whether or not the modifier combination is the left or right variant.
*By sbuzo\.\.\.@fancyguy.com on February 26, 2015 01:35 (imported from Google Code)*
---
I want to be able to map keys differently depending on whether or not the modifier combination is the left or right variant.
Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3430Split window without resizing other parts2015-05-01T20:02:54ZGeorge NachmanSplit window without resizing other parts*By luy\.\.\. on February 25, 2015 11:20 (imported from Google Code)*
---
I find splitting windows from &quot;1.png&quot; to &quot;2.png&quot; is not so natural. &quot;3.png&quot; is better. The other parts of windows are not supposed ...*By luy\.\.\. on February 25, 2015 11:20 (imported from Google Code)*
---
I find splitting windows from "1.png" to "2.png" is not so natural. "3.png" is better. The other parts of windows are not supposed to be resized.
See the files.
---
![1.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3430/comment-0/1.png)
![2.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3430/comment-0/2.png)
![3.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3430/comment-0/3.png)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3418Clear all panes (Cmd-Shift-K)2022-12-10T00:06:44ZGeorge NachmanClear all panes (Cmd-Shift-K)*By \.\.\.@arnellconsulting.com on February 16, 2015 12:46 (imported from Google Code)*
---
I am currently checking the logs on three servers and one client using split panes.
I would really love if it was possible to clear all pa...*By \.\.\.@arnellconsulting.com on February 16, 2015 12:46 (imported from Google Code)*
---
I am currently checking the logs on three servers and one client using split panes.
I would really love if it was possible to clear all panes in a window using a modified version of CMD-K.
For the moment I am navigating to all panes and use CMD-K to close each.
Best Regards,
JimFuture Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3417Profile->Window->Style->Fullscreen is a little bit from satisfying2015-05-01T20:02:38ZGeorge NachmanProfile->Window->Style->Fullscreen is a little bit from satisfying*By \.\.\.@introo.me on February 14, 2015 08:11 (imported from Google Code)*
---
Well. This report is quite mainfest and doesn't need a plist I think.
After you set the &quot;fullscreen&quot; under Pref-&gt;Profile-&gt;Window-&gt;...*By \.\.\.@introo.me on February 14, 2015 08:11 (imported from Google Code)*
---
Well. This report is quite mainfest and doesn't need a plist I think.
After you set the "fullscreen" under Pref->Profile->Window->Style->Fullscreen
when you open a new window, the intial window size is the one set in that tab, and then it will immediately become fullscreen.
This is easy to reproduce on the latest iTerm2 test version.
This quite annoying for me.
A fullscreen should be fullscreen when opening, not transitting to fullscreen immediately.
Hope you can fix this. Thanks!Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3412Unable to save window arrangement when in tmux session2016-03-16T15:47:22ZGeorge NachmanUnable to save window arrangement when in tmux session*By \.\.\.@google.com on February 10, 2015 16:10 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Open iTerm2
2. Load a profile
3. Restore a tmux session
4. Try to save a window arrangement
...*By \.\.\.@google.com on February 10, 2015 16:10 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Open iTerm2
2. Load a profile
3. Restore a tmux session
4. Try to save a window arrangement
<b>What is the expected output?</b>
Saved window arrangement appears as an option in the "Restore Window Arrangement >" list
<b>What do you see instead?</b>
Nothing is added to the restore list.
<b>What version of iTerm2 are you using?</b>
2.0.0.20141103
<b>What OS version are you using?</b>
Mac OS 10.9.5
<b>Please provide any additional information below.</b>
I did not attach .plist due to privacy concerns.
---
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3412/comment-0/debuglog.txt.gz)
[console_output.log](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3412/comment-0/console_output.log)Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3410text selection often fails when selecting in an upward direction2015-05-01T20:02:15ZGeorge Nachmantext selection often fails when selecting in an upward direction*By samwiz\.\.\. on February 09, 2015 16:19 (imported from Google Code)*
---
I have often noticed that when I select text in an upward direction (i.e. the start of the selection is lower in the screen than the end of the selection), th...*By samwiz\.\.\. on February 09, 2015 16:19 (imported from Google Code)*
---
I have often noticed that when I select text in an upward direction (i.e. the start of the selection is lower in the screen than the end of the selection), the selection will fail to copy and the paste buffer will be empty, even though the selection is still visually highlighted. I don't recall every having this problem when selecting in a downward direction. This appears to happen randomly and I cannot reliably trigger the bug.
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3410/comment-0/com.googlecode.iterm2.plist)https://gitlab.com/gnachman/iterm2/-/issues/3408Short pager output sticks to prompt rather than top of terminal2016-08-19T05:38:47ZGeorge NachmanShort pager output sticks to prompt rather than top of terminal*By alle\.\.\. on February 09, 2015 05:56 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Run <b>What steps will reproduce the problem?</b>
1. Run less<b>What steps will reproduce the problem?</b> ...*By alle\.\.\. on February 09, 2015 05:56 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Run <b>What steps will reproduce the problem?</b>
1. Run less<b>What steps will reproduce the problem?</b>
1. Run `less on some file whose number of lines is smaller than the height of the terminal.
<b>What is the expected output?</b>
The pager output should stick to the top of the screen. (try on Terminal.app to see how it should work, an animation of iTerm2's behavior is attached)
<b>What do you see instead?</b>
That the output sticks to bottom (where the prompt lies)
<b>What version of iTerm2 are you using?</b>
Build 2.9.20150206-nightly
<b>What OS version are you using?</b>
10.10.2
<b>Please provide any additional information below.</b>
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3408/comment-0/com.googlecode.iterm2.plist)
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3408/comment-0/debuglog.txt.gz)
![Untitled.gif](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3408/comment-0/Untitled.gif)Review for next versionhttps://gitlab.com/gnachman/iterm2/-/issues/3403Allow users config font fallback2017-09-22T13:49:10ZGeorge NachmanAllow users config font fallback*By the\.\.\. on February 04, 2015 12:35 (imported from Google Code)*
---
Nowadays, users often face the need to display the unicode character or powerline font on the screen. The tradition approach is to patch the font we current use....*By the\.\.\. on February 04, 2015 12:35 (imported from Google Code)*
---
Nowadays, users often face the need to display the unicode character or powerline font on the screen. The tradition approach is to patch the font we current use. But it has lots of disadvantages. I think the right approach is using font fallback. And it would be great to have such feature inside iTerm 2.Future Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3399Allow changing window style to any value [was: Full Screen Mode w/ Style Bott...2016-12-28T17:19:59ZGeorge NachmanAllow changing window style to any value [was: Full Screen Mode w/ Style Bottom/Top of Screen]*By jrod\.\.\. on February 02, 2015 14:31 (imported from Google Code)*
---
Open iTerm docked at bottom of screen, hit CMD-Enter - Nothing happens.
I've read in other areas that this was fixed in past versions... Did the issue fix ...*By jrod\.\.\. on February 02, 2015 14:31 (imported from Google Code)*
---
Open iTerm docked at bottom of screen, hit CMD-Enter - Nothing happens.
I've read in other areas that this was fixed in past versions... Did the issue fix regress in Mavericks?
I would love to be able to go Full Screen from docked/bottom screen... $100
CheersFuture Releasehttps://gitlab.com/gnachman/iterm2/-/issues/3397Garbage pixels on screen refresh with Lucida Console font2015-06-15T21:00:17ZGeorge NachmanGarbage pixels on screen refresh with Lucida Console font*By paul.b.hen\.\.\. on January 31, 2015 05:42 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Install Lucida Console font
2.Use various applications that refresh screen (mutt, vim, etc)
3.Notice...*By paul.b.hen\.\.\. on January 31, 2015 05:42 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Install Lucida Console font
2.Use various applications that refresh screen (mutt, vim, etc)
3.Notice broken refresh with fragments of previous screens displayed
4 Refresh screen (^L, or switch to another app then back) and notice fragments disappear
<b>What is the expected output?</b>
Each screen refresh should be clean, displaying only the fonts relevant to it.
<b>What do you see instead?</b>
Bits and pieces of previously displayed fonts scattered about screen.
<b>What version of iTerm2 are you using?</b>
2.0.0.20141103
<b>What OS version are you using?</b>
10.10.1, but I originally noticed the issue on 10.9 but didn't have time to report it.
<b>Please provide any additional information below.</b>
I've attached two screenshots. The first is of a corrupted mutt screen with random pixels on it from the previously displayed screen obtained by just switching between messages. The second is how the screen should look, after I press ^L to refresh the screen.
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3397/comment-0/com.googlecode.iterm2.plist)
![Screen Shot 2015-01-30 at 9.30.34 PM.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3397/comment-0/Screen Shot 2015-01-30 at 9.30.34 PM.png)
![Screen Shot 2015-01-30 at 9.31.30 PM.png](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3397/comment-0/Screen Shot 2015-01-30 at 9.31.30 PM.png)
[debuglog.txt.gz](https://storage.googleapis.com/google-code-attachments/iterm2/issue-3397/comment-0/debuglog.txt.gz)