[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2 bugs in posn-at-x-y on a tty
From: |
Kim F. Storm |
Subject: |
Re: 2 bugs in posn-at-x-y on a tty |
Date: |
Fri, 14 Jan 2005 13:17:59 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) |
Nick Roberts <address@hidden> writes:
> There appear to be two bugs posn-at-x-y when used in an tty:
Actually, this behaviour is according to the doc string:
By default, X and Y are relative to text area of the selected window.
>
> 1) On the mode-line the string returned is one located one character to the
> left of the x co-ordinate (starts from one but should really start from
> zero?).
> So clicking on the colon of the mode-line in an xterm returns the buffer
> coding system rather than changing the eol style.
>
> 2) The margin is not recognised. If the left-margin is 2 characters wide then
> I think that x=0, y=10 should be recognised as being in the margin
> (POS-OR-AREA should be 'left-margin and not nil) and true window co-ordinates
> should start a 2.
I have added an optional fourth arg to posn-at-x-y to make the
coordinates relative to the whole window. You must set that
to t to get the correct position for a mode or header line.
--
Kim F. Storm <address@hidden> http://www.cua.dk