Re: xterm 320-1 won't start with XTerm*faceName set in .Xresources

2015-11-09 Thread Brian Neu
fc-list outputs nothing. this is strange Is it functional ? $ /usr/bin/fc-list --version fontconfig version 2.11.1 Yep. bneu@aos3 ~ $ /usr/bin/fc-list --version fontconfig version 2.11.1 I ran an strace on fc-list, and it really didn't yield any major finds. Then I used setup64.exe to

Re: xterm 320-1 won't start with XTerm*faceName set in .Xresources

2015-11-09 Thread Brian Neu
On 11/6/2015 5:19 AM, Thomas Dickey wrote: | Honestly, I'm not even sure how to get a list of available fonts. fc-list -- Thomas E. Dickey fc-list outputs nothing. So, again, sadly, I have no idea where to go from there. -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: xterm 320-1 won't start with XTerm*faceName set in .Xresources

2015-11-05 Thread Brian Neu
On 11/2/2015 4:23 PM, Yaakov Selkowitz wrote: Perhaps you are missing your preferred font. What had you specified for XTerm*faceName? BitStream Vera Sans Mono Is there something that I can do to produce more debug information out of xterm as it launches. Honestly, I'm not even sure how to

xterm 320-1 won't start with XTerm*faceName set in .Xresources

2015-11-02 Thread Brian Neu
Ran setup64.exe to update cygwin today, and then the xterm window wouldn't come up. I was able to troubleshoot it down to the XTerm*faceName in my ~/.Xresources Commented out, it works, but I much prefer the other font. Any ideas? 2015/11/02 12:55:45 Extracting _update-info-dir/_up