On Sun, Jan 14, 2007 at 12:27:35AM +, Thomas Adam wrote:
On Sun, Jan 14, 2007 at 12:50:57AM +0100, Dominik Vogt wrote:
On Sat, Jan 13, 2007 at 09:12:00PM +, Thomas Adam wrote:
On Sat, Jan 13, 2007 at 04:34:17PM +0100, Dominik Vogt wrote:
There appears to be a discrepency between
On 1/14/07, Dominik Vogt [EMAIL PROTECTED] wrote:
I don't understand what your problem is. When I start xterm like
this:
$ xterm -g 80x24+0+0
I get an 80x24 xterm at +0+0. FvwmIdent says:
X: 0 (frame x position)
Y: 0 (frame y position)
Width: 587 (frame width)
Height: 342 (frame
On Sun, Jan 14, 2007 at 03:54:23PM +, Thomas Adam wrote:
On Sun, Jan 14, 2007 at 04:33:56PM +0100, Dominik Vogt wrote:
With that, FvwmIdent prints the relevant information to the
console. Can you post the output and the (relevant) output of
xwininfo please?
Sure. I should just
There appears to be a discrepency between how FvwmIdent calculates the
geometry of the specified window, in relation to, say, how xwininfo
calculates it. In both cases, xwininfo's report of the geometry of a
window is correct. You just have to use a test case of:
xterm -g
On Sat, Jan 13, 2007 at 09:12:00PM +, Thomas Adam wrote:
On Sat, Jan 13, 2007 at 04:34:17PM +0100, Dominik Vogt wrote:
There appears to be a discrepency between how FvwmIdent calculates the
geometry of the specified window, in relation to, say, how xwininfo
calculates it. In both
