On Fri, Oct 27, 2017 at 03:00:32PM +0200, Philipp Marek wrote: > Package: xterm > Version: 330-1 > Severity: normal > > Having an xterm with "Allow font ops" being enabled, it happens to quit > after some of these: > > * use "xtermcontrol --font=<N>" with <N> being eg. 0 or 5 > * choose a different size from the font menu > > "xterm" doesn't crash, it just gives the above message and quits - which > would've been unfortunate, hadn't I be running tmux at the time ;)
I don't see a crash (it probably depends on whether you have the bitmap fonts installed). Instead, it gives a message: xterm-dev: cannot load font "2" In the manual for xtermcontrol: --font=FONT Set font name (see also FONT NAMES). Alternatively it is possi‐ ble to specify a fontmenu index as ´#[0-6]´ or navigate the fontmenu by relative sizes as ´#+N´ or ´#-N´, where N is an optional integer. the "#" is literally part of the parameter (though the quotes are misleading). > Still, simply quitting just because the user asks for a different font size > is bad behaviour - and real data might be lost (generated but not-yet-saved > console output). If there's no bitmap fonts, xterm's supposed to recover (and gray-out the items for the missing fonts). But I don't recall someone using xtermcontrol to test that with. If I knew the fonts you're using, I could reproduce this. > Versions of packages xterm depends on: for whatever reason, xterm doesn't depend on any fonts... -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature