From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: rms@gnu.org, jonas@bernoul.li, samologist@gmail.com,
emacs-devel@gnu.org, karthikchikmagalur@gmail.com,
visuweshm@gmail.com, raman@google.com
Subject: Re: Alternative defaults for visually impaired users? (was: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?))
Date: Mon, 23 Dec 2024 15:47:20 +0200 [thread overview]
Message-ID: <86plli4il3.fsf@gnu.org> (raw)
In-Reply-To: <87bjx2ls6k.fsf@localhost> (message from Ihor Radchenko on Mon, 23 Dec 2024 08:28:03 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: rms@gnu.org, jonas@bernoul.li, samologist@gmail.com,
> emacs-devel@gnu.org, karthikchikmagalur@gmail.com, visuweshm@gmail.com,
> raman@google.com
> Date: Mon, 23 Dec 2024 08:28:03 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I imagine adding "alternative" default value to `defcustom':
> >>
> >> (defcustom variable default-value
> >> :alt-default
> >> (("blind" . value2)
> >> ("large-fonts" . value3))
> >> ...)
> >> ...
> >
> > If this means that, for example, each face and defcustom we define
> > will need to have such alternatives defined in advance, I think it's a
> > non-starter. People will forget to define those, and having such a
> > definition for each face/defcustom is extremely inconvenient and hard
> > to maintain.
>
> I believe that only a small subset of options/faces will need to specify
> the alternative defaults. Why do you think that _each_ face/defcustom
> will require that?
Because each face can appear on display, and we want all of them to be
visible.
Or maybe I'm missing something: why do you think only a small subset
of faces and options will need to have special defaults?
> > What I think we need is some infrastructure which will automatically
> > react to a setting from the accessibility set. For "large fonts",
> > this is almost trivial, but other settings might be harder.
>
> I doubt that such _universal_ infrastructure that will not require
> manual intervention can exist wrt Emacs options. Maybe for faces. But
> 100% not for user options.
If we agree that this is reasonable for faces, we should be able to do
that already.
As for user options, we should first have an idea what kind of options
will need to be affected. If you know, please tell. Then we can
discuss what needs to be done about them, and then we could see if
some mechanism will be needed or will be useful.
> > Perhaps a useful first step would be for someone to see what other
> > systems and applications offer in this department, and post the
> > findings. Then we could discuss how to incorporate the relevant parts
> > into Emacs.
>
> I CCed Samuel and Raman because they probably know best about
> Emacs-specific customization and maybe also about other apps.
Thanks.
next prev parent reply other threads:[~2024-12-23 13:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8734m28l9a.fsf@gmail.com>
[not found] ` <874j6h3rw8.fsf@localhost>
[not found] ` <877cbamq2q.fsf@gmail.com>
[not found] ` <87cykvrgwr.fsf@localhost>
[not found] ` <8734lpmkjn.fsf@gmail.com>
[not found] ` <87r08lqlbu.fsf@localhost>
[not found] ` <87a5ewfvo1.fsf@gmail.com>
2024-10-22 17:58 ` Org-cite: Replace basic follow-processor with transient menu? Ihor Radchenko
[not found] ` <87wmhlmp83.fsf@gmail.com>
[not found] ` <871pzte929.fsf@localhost>
[not found] ` <87v7x548ri.fsf@gmail.com>
[not found] ` <87y120daue.fsf@localhost>
[not found] ` <874j4m9ep6.fsf@gmail.com>
[not found] ` <87h68gfqj1.fsf@localhost>
[not found] ` <CAO0k701CGFnQwCCuODjTFuf=OTsj9Vdqg+COP8nkpJg0wL_hQg@mail.gmail.com>
[not found] ` <87pln3f3cc.fsf@localhost>
[not found] ` <CAO0k7006goK-AfhG+3PVwhz=4QU_DMm+5edmATZpjdRHkj61Bg@mail.gmail.com>
[not found] ` <87jzd9ojj0.fsf@localhost>
[not found] ` <87cyj0ajm9.fsf@gmail.com>
[not found] ` <87zfm4s50x.fsf@localhost>
[not found] ` <CAO0k703a5SCv4Eaogjs-14zgmTi-pK5qqG=8VzB8+7h-kcC8yg@mail.gmail.com>
[not found] ` <87wmh8s358.fsf@localhost>
[not found] ` <87y11nwp9z.fsf@gmail.com>
[not found] ` <CAO0k702GsRi-h8BEY08kpf5FzMxi_MvRygNXJCyFnbtaC-a59w@mail.gmail.com>
[not found] ` <87v7wd9a2h.fsf@localhost>
[not found] ` <878qt7fbki.fsf@gmail.com>
[not found] ` <87o71jwdxz.fsf@localhost>
[not found] ` <87wmg6edr0.fsf@gmail.com>
2024-12-13 18:41 ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Ihor Radchenko
2024-12-13 22:09 ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? Gabriel Santos
2024-12-14 9:57 ` Ihor Radchenko
2024-12-14 10:59 ` Gabriel Santos
2024-12-14 13:10 ` Ihor Radchenko
2024-12-13 22:57 ` Suhail Singh
2024-12-14 9:59 ` Ihor Radchenko
2024-12-14 14:30 ` Suhail Singh
2024-12-14 1:16 ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Panayotis Manganaris
2024-12-14 10:08 ` Ihor Radchenko
2024-12-15 21:20 ` Samuel Wales
2024-12-16 17:54 ` Ihor Radchenko
2024-12-17 2:08 ` Samuel Wales
2024-12-17 2:24 ` Samuel Wales
2024-12-17 18:04 ` Transient: accessibility problems for users who need to use large fonts (was: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?)) Ihor Radchenko
2024-12-18 7:19 ` Samuel Wales
2024-12-18 10:52 ` Jonas Bernoulli
2024-12-19 1:42 ` Samuel Wales
2024-12-19 1:50 ` Samuel Wales
2024-12-18 17:59 ` Ihor Radchenko
2024-12-19 1:48 ` Samuel Wales
2024-12-18 10:47 ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Jonas Bernoulli
2024-12-19 17:42 ` Internal variables and symbols in transient (was: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?)) Ihor Radchenko
2024-12-19 18:11 ` Alternative defaults for visually impaired users? " Ihor Radchenko
2024-12-22 4:49 ` Richard Stallman
2024-12-22 9:29 ` Ihor Radchenko
2024-12-22 12:25 ` Eli Zaretskii
2024-12-22 18:17 ` Ihor Radchenko
2024-12-22 18:54 ` Eli Zaretskii
[not found] ` <87bjx2ls6k.fsf@localhost>
2024-12-23 13:47 ` Eli Zaretskii [this message]
2024-12-23 16:47 ` Ihor Radchenko
[not found] ` <CAJcAo8vFHgC=B44_Zpawj=ZOKAW2viFT62cxddq6Q=d7PQF50A@mail.gmail.com>
2024-12-24 9:23 ` Ihor Radchenko
2024-12-14 10:50 ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? indieterminacy
2024-12-14 17:53 ` Juri Linkov
2024-12-15 9:07 ` Ihor Radchenko
2024-12-16 7:46 ` Juri Linkov
2024-12-16 18:06 ` Ihor Radchenko
2024-12-22 12:16 ` Tor-björn Claesson
[not found] ` <87h66ult46.fsf@localhost>
2024-12-24 7:04 ` Juri Linkov
2024-12-24 11:39 ` Tor-björn Claesson
2024-12-15 18:23 ` Kierin Bell
2024-12-17 17:23 ` Ihor Radchenko
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=86plli4il3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=karthikchikmagalur@gmail.com \
--cc=raman@google.com \
--cc=rms@gnu.org \
--cc=samologist@gmail.com \
--cc=visuweshm@gmail.com \
--cc=yantar92@posteo.net \
/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).