unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philip Kaludercic <philipk@posteo.net>,
	 mattias.engdegard@gmail.com, emacs-devel@gnu.org
Subject: Re: bind print-integers-as-characters to t in `describe-variable'?
Date: Thu, 16 May 2024 11:08:55 +0200	[thread overview]
Message-ID: <87y18ai0ns.fsf@gmail.com> (raw)
In-Reply-To: <865xvejgb2.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 May 2024 11:45:37 +0300")

>>>>> On Thu, 16 May 2024 11:45:37 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Philip Kaludercic <philipk@posteo.net>
    >> Cc: Mattias Engdegård <mattias.engdegard@gmail.com>,
    >> rpluim@gmail.com,
    >> emacs-devel@gnu.org
    >> Date: Thu, 16 May 2024 05:46:21 +0000
    >> 
    >> Eli Zaretskii <eliz@gnu.org> writes:
    >> 
    >> >> From: Mattias Engdegård <mattias.engdegard@gmail.com>
    >> >> Date: Wed, 15 May 2024 12:13:49 +0200
    >> >> Cc: emacs-devel@gnu.org
    >> >> 
    >> >> We could have stateful buttons controlling the display, which could
    >> >> also include things like printing numbers in hex and control chars
    >> >> in strings as escape sequences.
    >> >
    >> > Or maybe the doc string could provide meta-data about how to display
    >> > such values?
    >> 
    >> Why not bind it depending on the type of the user option?

    Eli> How do you tell "the type of the user option"?

(get 'electric-quote-chars 'custom-type)
=> (list character character character character)

Robert
-- 



  parent reply	other threads:[~2024-05-16  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  9:33 bind print-integers-as-characters to t in `describe-variable'? Robert Pluim
2024-05-15 10:13 ` Mattias Engdegård
2024-05-15 11:56   ` Eli Zaretskii
2024-05-16  5:46     ` Philip Kaludercic
2024-05-16  8:45       ` Eli Zaretskii
2024-05-16  9:05         ` Philip Kaludercic
2024-05-16 11:58           ` Eli Zaretskii
2024-05-16  9:08         ` Robert Pluim [this message]
2024-05-15 12:32   ` Robert Pluim
2024-05-15 11:55 ` 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=87y18ai0ns.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattias.engdegard@gmail.com \
    --cc=philipk@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).