Your message dated Sat, 04 Nov 2017 09:52:51 +0100 with message-id <87wp36o270....@turtle.gmx.de> and subject line Re: Bug#880610: xterm -report-fonts spawns another xterm has caused the Debian Bug report #880610, regarding xterm -report-fonts spawns another xterm to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 880610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: xterm Version: 330-1 File: /usr/bin/xterm I did $ xterm -report-fonts and voila it spawns another xterm in the process. What if $ xterm -version did the same? You see I was reading https://unix.stackexchange.com/questions/96962/how-can-i-find-the-default-font-resource-xterm-is-using Because I want to tell you that of $ unicode 絶 絕|grep U+ U+7D76 CJK UNIFIED IDEOGRAPH-7D76 U+7D55 CJK UNIFIED IDEOGRAPH-7D55 I can see the first, but not the second. $ xrdb -q|grep font: *VT100.font: -misc-fixed-medium-r-normal--18-*-*-*-*-*-iso10646-1
--- End Message ---
--- Begin Message ---On 2017-11-03 02:54 +0800, 積丹尼 Dan Jacobson wrote: > Package: xterm > Version: 330-1 > File: /usr/bin/xterm > > I did > $ xterm -report-fonts > and voila it spawns another xterm in the process. As already mentioned by Thomas, this is expected behavior. If you change the font in the newly started xterm with Ctrl-mouse-3, it will report that on stdout which seems absolutely reasonable to me. > What if > $ xterm -version > did the same? The xterm version is a constant, whereas the loaded fonts are subject to change. Cheers, Sven
--- End Message ---
