Bug#247766: marked as done (multiple specifications for the same resource name not possible)
Your message dated Tue, 30 Nov 2010 10:06:25 +0100
with message-id <20101130090625.GA3928@PC17>
and subject line Re: Bug#247766: tetex-bin: only the last -xrm on the command line is effective
has caused the Debian Bug report #247766,
regarding multiple specifications for the same resource name not possible
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 owner@bugs.debian.org
immediately.)
--
247766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247766
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: tetex-bin: only the last -xrm on the command line is effective
- From: Matt Swift <swift@alum.mit.edu>
- Date: Thu, 06 May 2004 17:30:48 -0400
- Message-id: <87y8o5dz07.fsf@beth.swift.xxx>
Package: tetex-bin
Version: 2.0.2-10
Severity: normal
According to the manual page for X(1), you are supposed to be able to
put multiple "-xrm resourcestring" argument on the command line. When
you do this with xdvi, all but the last one specified are entirely
ignored.
I invoke the actual binary, just in case the wrapper is screwing up
the arguments:
/usr/bin/xdvi.real -xrm 'XDvi.mainTranslations: #override "x":quit()' -xrm 'XDvi.mainTranslations: #override "]":quit()' -xrm 'XDvi.mainTranslations: #override "m":quit()' test.dvi
That should make the 'x' and ']' and 'm' keys quit. In fact, only the
'm' key and the default 'q' key quit. If you switch them around, it
is always the last one specified that works. I say they are entirely
ignored because the normal binding of the 'x' key is what the 'x' key
does, if it is in any position other than the last.
I have no idea whether this is a problem with xdvi, with X, or with X
documentation. The documented behavior is the desired one; you
(supposedly) can only specify one resource at a time with -xrm, so to
be limited to one is inconvenient. More importantly, if there were a
limitation of one such argument, then the extra ones should raise an
error instead of be silently ignored.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-beth.4
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages tetex-bin depends on:
ii debconf 1.4.22 Debian configuration management sy
ii debianutils 2.8.1 Miscellaneous utilities specific t
ii dpkg 1.10.20 Package maintenance system for Deb
ii ed 0.2-20 The classic unix line editor
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an
ii libgcc1 1:3.3.3-6 GCC support library
ii libice6 4.3.0-7 Inter-Client Exchange library
ii libkpathsea3 2.0.2-10 path search library for teTeX (run
ii libpaper1 1.1.14 Library for handling paper charact
ii libpng12-0 1.2.5.0-6 PNG library - runtime
ii libsm6 4.3.0-7 X Window System Session Management
ii libstdc++5 1:3.3.3-6 The GNU Standard C++ Library v3
ii libt1-5 5.0.2-0pre1 Type 1 font rasterizer library - r
ii libwww0 5.4.0-9 The W3C WWW library
ii libx11-6 4.3.0-7 X Window System protocol client li
ii libxaw7 4.3.0-7 X Athena widget set library
ii libxext6 4.3.0-7 X Window System miscellaneous exte
ii libxmu6 4.3.0-7 X Window System miscellaneous util
ii libxt6 4.3.0-7 X Toolkit Intrinsics
ii mime-support 3.26-1 MIME files 'mime.types' & 'mailcap
ii perl 5.8.3-3 Larry Wall's Practical Extraction
ii sed 4.0.9-2 The GNU sed stream editor
ii tetex-base 2.0.2-6 Basic library files of teTeX
ii xlibs 4.3.0-7 X Window System client libraries m
ii zlib1g 1:1.2.1-5 compression library - runtime
-- debconf information:
* tetex-bin/hyphen:
tetex-bin/oldcfg: true
* tetex-bin/upd_map: true
tetex-bin/cnf_name:
* tetex-bin/fmtutil: true
* tetex-bin/use_debconf: true
* tetex-bin/groupname: users
* tetex-bin/userperm: false
* tetex-bin/groupperm: true
* tetex-bin/lsr-perms: true
* tetex-bin/texmf: true
--- End Message ---
--- Begin Message ---
- To: Matt Swift <swift@alum.mit.edu>, 247766-done@bugs.debian.org
- Subject: Re: Bug#247766: tetex-bin: only the last -xrm on the command line is effective
- From: Hilmar Preusse <hille42@web.de>
- Date: Tue, 30 Nov 2010 10:06:25 +0100
- Message-id: <20101130090625.GA3928@PC17>
- In-reply-to: <87y8o5dz07.fsf@beth.swift.xxx>
- References: <87y8o5dz07.fsf@beth.swift.xxx>
On 06.05.04 Matt Swift (swift@alum.mit.edu) wrote:
Hi,
> According to the manual page for X(1), you are supposed to be able to
> put multiple "-xrm resourcestring" argument on the command line. When
> you do this with xdvi, all but the last one specified are entirely
> ignored.
>
> I invoke the actual binary, just in case the wrapper is screwing up
> the arguments:
>
> /usr/bin/xdvi.real -xrm 'XDvi.mainTranslations: #override "x":quit()' -xrm 'XDvi.mainTranslations: #override "]":quit()' -xrm 'XDvi.mainTranslations: #override "m":quit()' test.dvi
>
> That should make the 'x' and ']' and 'm' keys quit. In fact, only
> the 'm' key and the default 'q' key quit. If you switch them
> around, it is always the last one specified that works. I say they
> are entirely ignored because the normal binding of the 'x' key is
> what the 'x' key does, if it is in any position other than the
> last.
>
Finally I asked the x-strike force to clarify if this is intended.
They quoted from X(7):
A resource database never contains more than one entry for a given
ResourceName. If a resource file contains multiple lines with the same
ResourceName, the last line in the file is used.
This is the behaviour you see here, you just specified the resources
at the command line.
Please note that the following command line suggested by Stefan does
the trick.
xdvi -xrm 'XDvi.mainTranslations: #override "x":quit()\n"]":quit()\n"m":quit()'
-> FAD, Closing.
H.
--
sigmentation fault
--- End Message ---
Reply to: