At 2023-01-02T18:54:02+0100, Fabio Pedretti wrote:
> upstream bug report was closed with:
> "This code has been rewritten since and almost certainly fixed,
> closing."
Jesus. I'd never trust a claim like that without output from a formal
verification suite to confirm it.
I think we may have a
Hi Thomas,
Congratulations on another xterm release!
There are some instances of hyphens used in a literal context in the
xterm man page that should be escaped for reliable copy and paste. Most
of these are in the names of actions that can be bound to translation
resources.
There are a few
Package: xterm
Version: 337-1
Severity: normal
Tags: upstream
The man page says *saveLines defaults to 64. But it really defaults to
1024.
Patch attached. It also synchronizes xterm.dat, whatever that is, with
the application defaults file.
-- System Information:
Debian Release: buster/sid
At 2018-11-13T10:37:20+0100, Łukasz Stelmach wrote:
> +// Pressing the Shift+Win (left or right, respectively) acts as Menu
> +// while Shift+Win acts as Menu.
I don't understand this comment; it seems tautologous.
Shouldn't it be more like:
// Pressing left or right Win acts as Win, while
At 2018-06-28T11:31:30+0200, Michel Dänzer wrote:
>
> Please send this kind of change directly upstream to the
> amd-...@lists.freedesktop.org list for review, split up into one patch
> per logical change.
Well, a lot of these changes aren't "logical", they're stylistic.
> On 2018-06-27 09:07
At 2017-11-07T08:10:40-0500, G. Branden Robinson wrote:
> Here's an updated version of the patch, reverting the de-boldfacing of
> action names (and some token names) in resource translations.
Of course, by sending that I guaranteed I'd find a problem with it.
Here's my next try. The p
Here's an updated version of the patch, reverting the de-boldfacing of
action names (and some token names) in resource translations.
My additional fixes are described at the end, numbered 21-25.
Please find two attachments:
1. The actual diff.
2. A diff of the nroffed output of the two pages
At 2017-11-06T18:51:32-0500, Thomas Dickey wrote:
> > > > 10. Remove boldfacing from portions of code examples; these escapes
> > > > changed the font family back to Times from Courier. If this change
> > > > is unacceptable, I can come up with one that will stay within the
> > > >
At 2017-11-05T15:11:13-0500, Thomas Dickey wrote:
> On Thu, Nov 02, 2017 at 02:20:54AM -0400, G. Branden Robinson wrote:
> > 10. Remove boldfacing from portions of code examples; these escapes
> > changed the font family back to Times from Courier. If this change
> >
Hi Thomas,
At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).
Thanks to a bug in
At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).
Yeah, I've noticed those. When I
Package: xterm
Version: 327-2 (but I prepared the diff against xterm-330)
Severity: normal
Tags: upstream
Hi Thomas,
Here's a patch for various markup bugs and inconsistencies in the xterm
man page.
01. The local macro definitions for bP and NS were testing the values of
registers which
At 2017-07-26T11:51:10+0200, Nicolas George wrote:
> Package: xdm
> Version: 1:1.1.11-3
> Severity: normal
>
> Dear Maintainer,
>
> When somebody tries to log in and fails, xdm writes the given user name in
> the system logs. Unfortunately, typing the password in the login field is a
> common
At 2017-06-12T19:34:17+0200, Sven Joachim wrote:
> Debian unstable i386, but I get the same error on amd64.
>
> > XTerm 329 builds fine for me on Debian 9 amd64.
>
> Maybe you have configured with --enable-regis-graphics? This makes the
> problem go away.
Only if it's the default. I
At 2017-06-12T18:48:37+0200, Sven Joachim wrote:
> This does not build for me:
>
> ,
> | gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2
> -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False
>
At 2017-04-23T11:45:03+0200, Julien Cristau wrote:
> The wrapper was moved to the xserver-xorg-legacy package, and I'm a bit
> worried removing the configuration file in the x11-common maintainer
> scripts would break that transition.
Ahhh. Did we never get solid support in dpkg for migrating
At 2017-04-09T13:34:44+0200, Andreas Beckmann wrote:
> 1m37.2s INFO: Warning: Package purging left files on system:
> /etc/X11/Xwrapper.config not owned
It appears the old Xwrapper was killed off at some point.
The patch should be trivial enough that I can do it. This would also
serve as
At 2017-04-07T12:08:58-0400, James McCoy wrote:
> On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
> > However, my xterms are somewhat customized. I'm attaching my
> > .Xresources file.
>
> Perfect! That seems to be the difference. I, and presumably Fran
At 2017-04-06T21:56:13-0400, James McCoy wrote:
> On Fri, Apr 07, 2017 at 12:54:19AM +0200, Francesco Poli wrote:
> > On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote:
> >
> > > At 2017-04-06T13:33:58-0400, James McCoy wrote:
> > > > On Thu, Apr 06,
At 2017-04-06T13:33:58-0400, James McCoy wrote:
> On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote:
> > The below is not a sufficient reproduction receipe for me.
> >
> > I'm running Debian Stretch (testing).
> >
> > Things do not go wrong at
The below is not a sufficient reproduction receipe for me.
I'm running Debian Stretch (testing).
Things do not go wrong at step #5, nor afterward.
At 2017-04-05T22:03:50-0400, James McCoy wrote:
> On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute) wrote:
> > I finally found a
This bug has been marked as needing help for a while.
Guillem Jover wrote:
> On Thu, 2013-04-25 at 14:51:29 +0200, Andreas Beckmann wrote:
> On 2013-04-25 10:39, Guillem Jover wrote:
> > > I guess the correct solution though, is to change update-fonts-*
> > > and any other script in xfonts-utils
On Tue, Mar 21, 2017 at 11:59:09AM +0900, Michel Dänzer wrote:
> Just modify or create /etc/X11/xorg.conf directly. The xorg.conf.d
> mechanism is for snippets shipped in packages.
[...]
> The identifier doesn't matter, it would only be used for referring to
> the Section "Device" from other
[redirecting side topic to mailing list]
On Mon, Mar 20, 2017 at 08:56:58PM +0100, Sven Joachim wrote:
> On 2017-03-20 15:18 -0400, G. Branden Robinson wrote:
>
> > I'm at a loss, then. As you originally suspected, maybe it is a
> > graphics driver issue. Attaching Xorg.log[2
On Mon, Mar 20, 2017 at 08:02:29PM +0100, Sven Joachim wrote:
> On 2017-03-20 14:42 -0400, G. Branden Robinson wrote:
> > I think you may be getting FreeMono.ttf instead of DejaVuSansMono.ttf.
>
> I don't think so, the screenshot I included in
> <8760j3hklk@turtle.gmx.de&
On Mon, Mar 20, 2017 at 07:24:55PM +0100, Sven Joachim wrote:
> No, attached is a screenshot of "xterm -fa DejaVuSansMono -fs 14".
I think you may be getting FreeMono.ttf instead of DejaVuSansMono.ttf.
> > [1] On my Debian Stretch system installed freshly as of Friday, 17 March,
> > "matching"
On Mon, Mar 20, 2017 at 06:17:42PM +0100, Sven Joachim wrote:
> On 2017-03-20 13:05 -0400, G. Branden Robinson wrote:
> > On Mon, Mar 20, 2017 at 05:58:27PM +0100, Sven Joachim wrote:
> >> On 2017-03-18 16:37 -0400, Branden Robinson wrote:
> >> > but "xfd -fa Fr
On Mon, Mar 20, 2017 at 05:58:27PM +0100, Sven Joachim wrote:
> On 2017-03-18 16:37 -0400, Branden Robinson wrote:
>
> > Package: xterm
> > Version: 327-2
> > Severity: normal
> > Tags: upstream
> >
> > Observe screenshot. Wouldn't surprise me in the least if the problem is
> > really with
28 matches
Mail list logo
