unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: display value of links in mini-buffer (was: Re: bug archiving policy)
Date: Sun, 6 Dec 2020 06:35:02 -0500	[thread overview]
Message-ID: <20201206113502.uqqgde6zw5odzyry@E15-2016.optimum.net> (raw)
In-Reply-To: <83360jb2gm.fsf@gnu.org>

On 2020-12-06 13:26, Eli Zaretskii wrote:
> > From: Yuri Khan <yuri.v.khan@gmail.com>
> > Date: Sun, 6 Dec 2020 17:54:40 +0700
> > Cc: Emacs-Devel List <emacs-devel@gnu.org>
> >
> > However, some modes also put 'help-echo property over text in a
> > ...
>
> We already have the kbd-help property (display-local-help supports
> it); would that fit the bill?

Why need for two separate properties? Should the two be combined if they
serve essentially the same purpose?

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



  reply	other threads:[~2020-12-06 11:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 10:54 display value of links in mini-buffer (was: Re: bug archiving policy) Yuri Khan
2020-12-06 11:07 ` Boruch Baum
2020-12-06 11:26 ` Eli Zaretskii
2020-12-06 11:35   ` Boruch Baum [this message]
2020-12-06 11:39     ` Eli Zaretskii
2020-12-06 11:51       ` Yuri Khan
2020-12-06 12:03         ` Eli Zaretskii
2020-12-06 11:44 ` Eli Zaretskii
2020-12-06 12:04   ` Yuri Khan
2020-12-06 12:20     ` Eli Zaretskii
     [not found] <<CAP_d_8XG7BrPqC3ZsqijLZerTOgPwt_MeBZOkDCbCuk6_cgGKQ@mail.gmail.com>
     [not found] ` <<83zh2r9n26.fsf@gnu.org>
     [not found]   ` <<CAP_d_8WezomrMT6U+H5_R8P9d3=_Vm98S_4y0Hw-oTaL5n+hsA@mail.gmail.com>
     [not found]     ` <<83wnxv9lcy.fsf@gnu.org>
2020-12-06 16:42       ` Drew Adams
2020-12-06 18:27         ` Boruch Baum
2020-12-06 19:58           ` Drew Adams

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=20201206113502.uqqgde6zw5odzyry@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.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).