From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 51658@debbugs.gnu.org
Subject: bug#51658: [PATCH] Haiku port (again)
Date: Sun, 14 Nov 2021 12:54:32 +0200 [thread overview]
Message-ID: <83ee7juhw7.fsf@gnu.org> (raw)
In-Reply-To: <875ysv58dz.fsf@yahoo.com> (message from Po Lu on Sun, 14 Nov 2021 18:39:04 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: 51658@debbugs.gnu.org
> Date: Sun, 14 Nov 2021 18:39:04 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > How is POSITION used? Can't you fake POSITION, so we get the same
> > event as on other platforms?
>
> AFAIU, POSITION is used to determine the window where the file should
> appear. It should be possible to fake.
>
> We could get the mouse position on-screen, but it may lead to odd
> results if the user asks Emacs to open a file through the Tracker or the
> Recents menu, and the mouse is not on top of an Emacs frame, or if the
> system starts Emacs to open a file.
>
> What position do you think would be reasonable to report here?
The position in a window where your current code visits the file, I
guess? Because this feature already works in your modified Emacs,
right?
> BTW, it seems that the NS port has the same problem here: it defines the
> custom events `ns-open-file' and `ns-drag-and-drop' and `ns-power-off'.
Which is BAAAAD!
> > Every modern system has something similar, so it would make sense to
> > have a unified mechanism for handling those system messages in Emacs.
> > If xsmfns.c is too X-specific, we should build a layer above it, and
> > then implement th lower layer for Haiku. It makes no sense to me to
> > introduce new events for specific platforms when similar features
> > already exist and just need to be extended or abstracted.
>
> Yes, makes sense. It would be worthwhile just to solve this problem
> with the NS port. I will look into it.
Thanks.
next prev parent reply other threads:[~2021-11-14 10:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee7surtv.fsf.ref@yahoo.com>
2021-11-07 11:29 ` bug#51658: [PATCH] Haiku port (again) Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 17:58 ` Eli Zaretskii
2021-11-10 0:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 4:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 12:38 ` Eli Zaretskii
2021-11-10 12:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 14:19 ` Eli Zaretskii
2021-11-11 0:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-11 6:51 ` Eli Zaretskii
2021-11-11 7:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-13 18:31 ` Eli Zaretskii
2021-11-14 1:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 7:54 ` Eli Zaretskii
2021-11-14 9:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 10:28 ` Eli Zaretskii
2021-11-14 10:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 10:54 ` Eli Zaretskii [this message]
2021-11-14 11:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-15 2:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 7:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 8:33 ` Eli Zaretskii
2021-11-20 9:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 9:56 ` Eli Zaretskii
2021-11-20 13:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 13:30 ` Eli Zaretskii
2021-11-20 13:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 13:41 ` Eli Zaretskii
2021-11-20 13:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 13:55 ` Eli Zaretskii
2021-11-20 13:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 14:15 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee7juhw7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51658@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).