Re: Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-18 Thread David Martínez Moreno
El Domingo, 17 de Julio de 2005 12:34, Thomas Dickey escribió: On Sun, Jul 17, 2005 at 10:17:32AM +0800, Eugene Konev wrote: The problem is font name stored in normal is being overwritten by a bold font name and then normal is used in comparison with a myfonts.f_b to decide whether they are

Re: Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-18 Thread Thomas Dickey
On Mon, Jul 18, 2005 at 12:46:49PM +0200, David Martínez Moreno wrote: El Domingo, 17 de Julio de 2005 12:34, Thomas Dickey escribió: On Sun, Jul 17, 2005 at 10:17:32AM +0800, Eugene Konev wrote: The problem is font name stored in normal is being overwritten by a bold font name and then

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-17 Thread Thomas Dickey
On Sun, Jul 17, 2005 at 10:17:32AM +0800, Eugene Konev wrote: The problem is font name stored in normal is being overwritten by a bold font name and then normal is used in comparison with a myfonts.f_b to decide whether they are the same and whether to turn on overstriking. The attached

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-16 Thread Tobias Diedrich
Thomas Dickey wrote: That sounds like what is being reported, but since I didn't touch _that_ part of the logic, I'm left with the impression that you have a slightly different set of fonts installed than I - and the modifications I made to the XLFD wildcards are breaking in that case. If I

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-16 Thread Thomas Dickey
On Sat, Jul 16, 2005 at 08:49:35AM +0200, Tobias Diedrich wrote: Thomas Dickey wrote: That sounds like what is being reported, but since I didn't touch _that_ part of the logic, I'm left with the impression that you have a slightly different set of fonts installed than I - and the

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-16 Thread Eugene Konev
The problem is font name stored in normal is being overwritten by a bold font name and then normal is used in comparison with a myfonts.f_b to decide whether they are the same and whether to turn on overstriking. The attached patch fixes it. Index:

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-15 Thread Thomas Dickey
On Thu, Jul 14, 2005 at 04:00:33PM +0200, Tobias Diedrich wrote: Package: xterm Version: 6.8.2.dfsg.1-2 Followup-For: Bug #318162 According to the xterm manpage, while boldMode is true by default, if a bold font variant is found for a given non-bold font or specified with -fb, boldMode

Bug#318162: xterm: boldMode enabled even if bold font is used

2005-07-14 Thread Tobias Diedrich
Package: xterm Version: 6.8.2.dfsg.1-2 Followup-For: Bug #318162 According to the xterm manpage, while boldMode is true by default, if a bold font variant is found for a given non-bold font or specified with -fb, boldMode should be turned off automatically. Apparently this is broken and xterm