[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#447519: marked as done (x11-common: [Xresources] doesn't support '*' as a 'common' wildcard)

Your message dated Sun, 6 Jan 2008 13:18:06 +0100
with message-id <20080106121758.GA12561@patate.is-a-geek.org>
and subject line Bug#447519: xterm: [UXTerm] doesn't support *XTerm class in ~/.Xresources
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xterm
Version: 229-1
Severity: normal


I'm not sure this is really a bug, but I cannot find anything in the
documentation.  In case it's there, can anyone point me at it, please?

Basically, I'd like to define UXTerm resources in the *XTerm form
(which is perfectly valid for xterm itself), in order to avoid
resource duplications.  As I wrote, it seems that xterm supports
*XTerm, while uxterm no.

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xterm depends on:
ii  libc6                     2.6.1-6        GNU C Library: Shared libraries
ii  libfontconfig1            2.4.2-1.3      generic font configuration library
ii  libice6                   2:1.0.4-1      X11 Inter-Client Exchange library
ii  libncurses5               5.6+20071013-1 Shared libraries for terminal hand
ii  libsm6                    2:1.0.3-1+b1   X11 Session Management library
ii  libx11-6                  2:1.0.3-7      X11 client-side library
ii  libxaw7                   2:1.0.4-1      X11 Athena Widget library
ii  libxext6                  1:1.0.3-2      X11 miscellaneous extension librar
ii  libxft2                   2.1.12-2       FreeType-based font drawing librar
ii  libxmu6                   1:1.0.3-1      X11 miscellaneous utility library
ii  libxt6                    1:1.0.5-3      X11 toolkit intrinsics library
ii  xbitmaps                  1.0.1-2        Base X bitmaps

Versions of packages xterm recommends:
pn  xutils                        <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, Oct 27, 2007 at 00:41:06 +0200, Luca Capello wrote:

> Since the problem isn't in xterm, but in Xt resources, I reassigned
> the bug to x11-common (because it's the package that ships
> /etc/X11/Xresources).

It doesn't ship libXt, though, which is what you're talking about here.

> I haven't closed this bug yet because I don't really know how to
> proceed: either we just close this bug as a not-a-bug or we leave this
> bug opened as a wishlist, tagging it upstream, too.  In the latter
> case, since I think it's quite difficult that Xt resources will be
> changed to use 'common' wildcards, the bug is eligible for a wontfix
> tag, too.
Indeed, the semantics of Xt resources won't change, so I don't think
it'd be useful to keep this bug open.  I'm thus closing it with this


--- End Message ---

Reply to: