unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 5743b74d4b 1/2: Improve mouse dragging
Date: Fri, 13 May 2022 01:49:42 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488EBCB66087BCC5D53B6D4F3CA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y1z6wa1k.fsf@yahoo.com>

> > Use `x-show-tip'.  Specify whatever you like.
> > E.g.:
> > (x-show-tip (propertize STRING 'face FACE-YOU-WANT)
> >             nil
> >             nil
> >             TIMEOUT-YOU-WANT)
> 
> Setting params to nil will cause various bugs,
> including the user's tooltip color customizations
> not being respected.

Really?

Setting an arg to nil _"causes"_ bugs?
And this though nil is a documented
valid value for optional arg PARMS?
Good golly!

And what do you mean by "the user's
tooltip color customizations"?  There's
nothing in that call that makes any use
or mention of anything user-defined.

With such a call no user should expect
anything related to anything they've
customized (unless it's FACE-YOU-WANT
that they've customized - and a face
customization is surely respected).

I wonder, did you actually try what I
suggested?

Anyway I don't see any such sky-falling.
I use such code with no problem.

But then, I don't use the latest and
greatest development of Emacs.

Perhaps some innovative regressions have
been introduced in Emacs 28, or later.
On n'arrete pas le progres...



  reply	other threads:[~2022-05-13  1:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  7:31 master 5743b74d4b 1/2: Improve mouse dragging Eli Zaretskii
2022-05-12 12:03 ` Po Lu
2022-05-12 12:47   ` Eli Zaretskii
2022-05-12 13:02     ` Po Lu
2022-05-12 13:12       ` Eli Zaretskii
2022-05-12 13:20         ` Eli Zaretskii
2022-05-12 13:25           ` Po Lu
2022-05-12 13:23         ` Po Lu
2022-05-12 13:51           ` Eli Zaretskii
2022-05-13  0:27             ` Po Lu
2022-05-13  6:00               ` Eli Zaretskii
2022-05-13  7:05                 ` Po Lu
2022-05-13  7:36                   ` Eli Zaretskii
2022-05-13  7:49                     ` Po Lu
2022-05-13 10:32                       ` Eli Zaretskii
2022-05-13 11:10                         ` Po Lu
2022-05-13 12:08                           ` Eli Zaretskii
2022-05-13 12:45                             ` Po Lu
2022-05-13 12:48                               ` Eli Zaretskii
2022-05-13 12:16                           ` Eli Zaretskii
2022-05-13 12:46                             ` Po Lu
2022-05-12 15:49       ` [External] : " Drew Adams
2022-05-13  0:28         ` Po Lu
2022-05-13  1:49           ` Drew Adams [this message]
2022-05-13  3:42             ` Po Lu
2022-05-13 15:30               ` Drew Adams
2022-05-14  0:56                 ` Po Lu

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=SJ0PR10MB5488EBCB66087BCC5D53B6D4F3CA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).