unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Stefan Kangas <stefankangas@gmail.com>
Cc: "laszlomail@protonmail.com" <laszlomail@protonmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: RE: [External] : Re: Would you say this information window is well designed?
Date: Tue, 23 Feb 2021 15:44:12 +0000	[thread overview]
Message-ID: <SA2PR10MB44740930C64914233C65836DF3809@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87pn0qdfzh.fsf@gnus.org>

> Yes, making symbols into links that go nowhere is an awful
> design, so the lookup has to be done before the buttonizing.

No, not necessarily; not IMHO.  There is no such
"has to be done".  _That_ is "an awful design",
AFAICT.

Users should themselves be able to decide this.
They're the ones who should decide what "has to
be done", and when.

In the design I use (one example; I don't claim
there is no better approach):

* A user can choose to never provide such links.

* Otherwise:

  . If a user doesn't want to pay a time penalty
    of finding out beforehand whether a given
    symbol is actually covered in (some set of)
    manuals (the set being decidable by the user),
    the action of the link is called out as
    _checking_ for the symbol in the manuals.
    IOW, the link is, in effect, a _search_ link.

  . If a user wants to pay a penalty of checking
    beforehand, a link is created only if a target
    is known.

Your "has to" approach seems to amount to that
last possibility: no link unless we're sure it
can take you to a relevant node of a manual.

IMHO, that's the _least_ useful of all the
possibilities we can (and I do) offer users.



  reply	other threads:[~2021-02-23 15:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 18:37 Would you say this information window is well designed? Peter Dean
2021-02-22 18:48 ` Eli Zaretskii
2021-02-22 19:23   ` Dmitry Gutov
2021-02-22 19:28     ` Eli Zaretskii
2021-02-22 20:28       ` Joost Kremers
2021-02-22 21:49       ` Dmitry Gutov
2021-02-22 21:57         ` Lars Ingebrigtsen
2021-02-22 22:30           ` [External] : " Drew Adams
2021-02-23  0:45             ` Stefan Kangas
2021-02-23  5:34               ` Drew Adams
2021-02-23  5:46                 ` Drew Adams
2021-02-23  5:54                 ` Peter Dean
2021-02-23 15:22                   ` Eli Zaretskii
2021-02-23 15:29                     ` Peter Dean
2021-02-23 16:00                       ` Eli Zaretskii
2021-02-23 17:32                         ` Peter Dean
2021-02-23 17:40                           ` Eli Zaretskii
2021-02-23 17:59                             ` Peter Dean
2021-02-23 18:26                               ` Eli Zaretskii
2021-02-23 19:36                                 ` Peter Dean
2021-02-23 19:46                                   ` Eli Zaretskii
2021-02-23 21:58                                     ` Peter Dean
2021-02-24  3:25                                       ` Eli Zaretskii
2021-02-27 21:44                                 ` Dmitry Gutov
2021-02-28 17:32                                   ` Eli Zaretskii
2021-03-01  5:22                                     ` Richard Stallman
2021-02-23  5:44               ` Drew Adams
2021-02-23 14:18               ` Lars Ingebrigtsen
2021-02-23 15:44                 ` Drew Adams [this message]
2021-02-23 16:15                   ` Stefan Kangas
2021-02-23 16:28                     ` Drew Adams
2021-02-22 21:19 ` Stefan Kangas

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=SA2PR10MB44740930C64914233C65836DF3809@SA2PR10MB4474.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=laszlomail@protonmail.com \
    --cc=stefankangas@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).