From: "Eli Zaretskii" <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: New primitive buffer-position-at
Date: Wed, 12 Jan 2005 08:08:16 +0200 [thread overview]
Message-ID: <01c4f86d$Blat.v2.2.2$40a07dc0@zahav.net.il> (raw)
In-Reply-To: <16868.24118.468795.219802@farnswood.snap.net.nz> (message from Nick Roberts on Wed, 12 Jan 2005 12:16:06 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Wed, 12 Jan 2005 12:16:06 +1300
> Cc: emacs-devel@gnu.org
>
> > Also, in what way is it different from (posn-point (posn-at-x-y X Y)) ?
> >
> >
> > Stefan "who's wondering what posn-at-x-y does on a tty"
>
> The posn-* family of commands (posn-point, posn-object etc) only work if Emacs
> provides the proper click event in the first place which it doesn't currently
> do on a text terminal or xterm.
??? Are you saying that posn-point would throw an error or otherwise
behave incorrectly if invoked on a tty without a mouse? I tried that,
and it seemed to work fine for me.
I think whether a mouse is connected or not is not an issue, since a
click event object can be created manually even if there's no mouse.
And posn-at-x-y does precisely that, doesn't it?
> My patches to xt-mouse.el and t-mouse.el
> provide them in lisp i.e with these patches the posn-* family of commands will
> work on a text terminal or xterm.
I'm puzzled why did you need to patch xt-mouse.el, since these 2
functions seem to work for me on a tty, even a tty that lacks the
mouse.
next prev parent reply other threads:[~2005-01-12 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 21:54 New primitive buffer-position-at Nick Roberts
2005-01-11 22:48 ` Stefan Monnier
2005-01-11 23:16 ` Nick Roberts
2005-01-11 23:32 ` Stefan Monnier
2005-01-12 6:11 ` Nick Roberts
2005-01-12 18:40 ` Stefan Monnier
2005-01-12 6:08 ` Eli Zaretskii [this message]
2005-01-12 6:58 ` Nick Roberts
2005-01-12 5:59 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4f86d$Blat.v2.2.2$40a07dc0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.