Hyper: Line at the bottom of the terminal is not aligned properly
The last line of my terminal is sometimes "cut", like we don't see the bottom of some characters like (q or p).
It's not always the case in all my terminal windows, maybe it's related when the terminal has tabs. Will try to find better repro.
tleunen
All 28 comments
That's even worse than what I'm seeing (in #373)
jamo
on 18 Aug 2016
Hello! Just wanted to report the same problem, it happens to me with powerline for tmux (pretty bad)
or with just tmux (not as bad, but still misaligned):
jairtrejo
on 31 Aug 2016
Can confirm that this happens with "Times New Roman" as well. The only fix I found was to adjust the line-height, as suggested by @davegomez in my "duplicate" ticket.
termCSS: 'x-row {line-height: 1}',
fingermark
on 26 Sep 2016
Awesome, I can confirm that it fixed it for me!
jamo
on 26 Sep 2016
Tested with the recent 0.8.1 version and still have the issue.
fontSize: 12,
fontFamily: 'Menlo, "DejaVu Sans Mono", "Lucida Console", monospace',
And I also confirm that changing the line-height fixes the issue.
tleunen
on 8 Oct 2016
I can't reproduce the issue @tleunen. Have you tried disabling your extensions in case you are using one or maybe tweaking you configuration (using the default one), etc?
I have tried different fonts (even the ones you mention) and themes but nothing.
davegomez
on 8 Oct 2016
It's not an issue that occurs 100% of the time :/ Maybe 3 times of 5 I'd say.
I believe I'm using the default config:
module.exports = {
config: {
// default font size in pixels for all tabs
fontSize: 12,
// font family with optional fallbacks
fontFamily: 'Menlo, "DejaVu Sans Mono", "Lucida Console", monospace',
// terminal cursor background color and opacity (hex, rgb, hsl, hsv, hwb or cmyk)
cursorColor: 'rgba(248,28,229,0.75)',
// `BEAM` for |, `UNDERLINE` for _, `BLOCK` for â–ˆ
cursorShape: 'BLOCK',
// color of the text
foregroundColor: '#fff',
// terminal background color
backgroundColor: 'rgba(0, 0, 0, 0.75)',
// border color (window, tabs)
borderColor: '#333',
// custom css to embed in the main window
css: '',
// custom css to embed in the terminal window
termCSS: '',
// custom padding (css format, i.e.: `top right bottom left`)
padding: '12px 14px',
// the full list. if you're going to provide the full color palette,
// including the 6 x 6 color cubes and the grayscale map, just provide
// an array here instead of a color map object
colors: {
black: '#000000',
red: '#ff0000',
green: '#33ff00',
yellow: '#ffff00',
blue: '#0066ff',
magenta: '#cc00ff',
cyan: '#00ffff',
white: '#d0d0d0',
lightBlack: '#808080',
lightRed: '#ff0000',
lightGreen: '#33ff00',
lightYellow: '#ffff00',
lightBlue: '#0066ff',
lightMagenta: '#cc00ff',
lightCyan: '#00ffff',
lightWhite: '#ffffff'
},
// the shell to run when spawning a new session (i.e. /usr/local/bin/fish)
// if left empty, your system's login shell will be used by default
shell: '',
// for setting shell arguments (i.e. for using interactive shellArgs: ['-i'])
// by default ['--login'] will be used
shellArgs: ['--login'],
// for environment variables
env: {},
// set to false for no bell
bell: 'SOUND',
// if true, selected text will automatically be copied to the clipboard
copyOnSelect: false
// URL to custom bell
// bellSoundURL: 'http://example.com/bell.mp3',
// for advanced config flags please refer to https://hyperterm.org/#cfg
},
// a list of plugins to fetch and install from npm
// format: [@org/]project[#version]
// examples:
// `hyperpower`
// `@company/project`
// `project#1.0.1`
plugins: [],
// in development, you can create a directory under
// `~/.hyperterm_plugins/local/` and include it here
// to load it and avoid it being `npm install`ed
localPlugins: []
};
on a fresh install (only changed the shell to tmux) I see the same issue. The termCSS fix above did it for me.
os: ubuntu 16.04 LTS
unicolet
on 19 Oct 2016
The termCSS setting did not fix this issue for me.
I've narrowed it down to a single character in my prompt:
ツ
I'm using a zstyle prompt theme by Nadav Shatz called "Smiley" which uses the katakana character to indicate that the previous command exited with a status of zero. Non-zero return codes (errors) are indicated on the prompt with the heavy multiplication sign ✖.
I'd imagine there are more than just katakana which would cause this, and it might even depend on the font configuration as well. Here's my Hyper configuration for good measure.
module.exports = {
config: {
// default font size in pixels for all tabs
fontSize: 14,
// font family with optional fallbacks
fontFamily: 'Cousine, Menlo, "DejaVu Sans Mono", "Lucida Console", monospace',
// terminal cursor background color (hex)
cursorColor: '#F81CE5',
// color of the text
foregroundColor: '#fff',
// terminal background color
backgroundColor: '#000',
// border color (window, tabs)
borderColor: '#333',
// custom css to embed in the main window
css: '',
// custom css to embed in the terminal window
termCSS: '',
// custom padding (css format, i.e.: `top right bottom left`)
padding: '12px 14px',
// some color overrides. see http://bit.ly/29k1iU2 for
// the full list
colors: [
'#000000',
'#ff0000',
'#33ff00',
'#ffff00',
'#0066ff',
'#cc00ff',
'#00ffff',
'#d0d0d0',
'#808080',
'#ff0000',
'#33ff00',
'#ffff00',
'#0066ff',
'#cc00ff',
'#00ffff',
'#ffffff'
]
},
// a list of plugins to fetch and install from npm
// format: [@org/]project[#version]
// examples:
// `hyperpower`
// `@company/project`
// `project#1.0.1`
plugins: [
'hyperterm-solarized-light'
],
// in development, you can create a directory under
// `~/.hyperterm_plugins/local/` and include it here
// to load it and avoid it being `npm install`ed
localPlugins: []
};
yock
on 27 Oct 2016
this cuts off my tmux status bar by about 1/3/
jsatk
on 28 Oct 2016
Same here you're supposed to see 2 underscore here. They are hidden
Version 0.7.1 (0.7.1.36)
borisrorsvort
on 28 Oct 2016
Can you guys provide steps to reproduce it? I couldn't so far.
davegomez
on 28 Oct 2016
Try adding the katakana character to your command prompt. @davegomez
yock
on 28 Oct 2016
@davegomez for me it's all the time. Though I just tried termCSS: 'x-row {line-height: 1}' and this fixes the problem
borisrorsvort
on 28 Oct 2016
I get this when I use Consolas as my font.
jimgraham
on 30 Oct 2016
In my case this seems to be caused by the CSS overflow: hidden being applied to the last line. This only happens why I set my font to "Ubuntu Mono" so I suspect it's something that only happens with certain fonts.
Thanks
robertmarsal
on 15 Dec 2016
I am facing the same issue on Version 1.0.1 (1.0.1.1369). I'm running zsh with only the hyperterm-material plugin. My case is similar to that of @borisrorsvort. I'll try the hack he suggested.
shreyasminocha
on 9 Jan 2017
Hi, have you tried adding padding: '12px 14px 18px 14px' to the~/.hyper.js? It helped me
aersoares81
on 21 Mar 2017
Steps to reproduce, If I change font-size to 14px and font-family is fontFamily: '"Lucida Console", monospace',, so the font on the last screen line is cutted, similar with Inconsolata for Powerline font. I think the problem will be that the height is not recomputed right.
silverqx
on 19 Apr 2017
Will maybe be resolved by #1745
chabou
on 19 Apr 2017
@szachara
I can't reproduce, can you give more details about your configuration (shell, OS, hyper version etc...)
chabou
on 19 Apr 2017
@szachara Can you try to reproduce on master? #1745 has been merged into it
chabou
on 19 Apr 2017
I tried with master and still cutted @chabou
Try your self with fontFamily: '"Lucida Console", monospace' and font-size 14px.
silverqx
on 21 Apr 2017
@szachara What os are you using?
MartyGentillon
on 25 Apr 2017
NodeJS: 7.8.0
Hyper: 1.3.1
OS: Windows 10
silverqx
on 25 Apr 2017
Same problem here with fresh install just changed font settingsInconsolata For Powerline font and 14px fontSize.
NodeJS: v7.10.0
Hyper: Version 1.3.3 (1.3.3.1754)
OS: MacOS Sierra 10.12.5
mihaliak
on 18 May 2017
I have the same problem with 1.3.3:
As you can see the underscore is hidden.
mojoaxel
on 5 Jun 2017
This: termCSS: 'x-row {line-height: 1}' in ~/.hyper.js used to fix it a while back
jamo
on 5 Jun 2017
Related issues
stan-stripe
·
3Comments
laur1s
·
3Comments
alejandrofloresm
·
3Comments
cooperpellaton
·
3Comments
legomushroom
·
3Comments
Most helpful comment
Can confirm that this happens with "Times New Roman" as well. The only fix I found was to adjust the line-height, as suggested by @davegomez in my "duplicate" ticket.