unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: emacs-devel@gnu.org
Subject: Re: Change stars as read-hide-char
Date: Mon, 30 Jul 2018 12:14:37 +0100	[thread overview]
Message-ID: <877eldnffm.fsf@yandex.com> (raw)
In-Reply-To: <87d0v581pz.fsf@gmail.com> (Robert Pluim's message of "Mon, 30 Jul 2018 12:19:52 +0200")

Dear Robert

>>>>> Robert Pluim <rpluim@gmail.com> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >>>>>>> Robert Pluim <rpluim@gmail.com> writes:
    >> 
    >> > Colin Baxter <m43cap@yandex.com> writes: >> My apologies for
    >> posting here, I can't get posting rights at >>
    >> gmane.emacs.help. My `return-confirmation' emails get bounced at
    >> >> that news-group.
    >> >> 
    >> >> The development emacs-27 version recently changed the default
    >> >> character seen when entering a password from `.' to `*'. I
    >> want >> to get back to the old default, but
    >> >> 
    >> >> (let (read-hide-char) "?.")
    >> >> 
    >> 
    >> > 'let' specifies a list of variable bindings, and you want the >
    >> character '.', not a string containing '?' and '.', so itʼs:
    >> 
    >> > (let ((read-hide-char ?. )) (message "%c" read-hide-char))
    >> 
    >> Unfortunately
    >> 
    >> (let ((read-hide-char ?. )) (message "%c" read-hide-char))
    >> 
    >> also doesn't work. It gives the error
    >> 
    >> Wrong type argument: characterp, "?."
    >> 
    >> as soon as I enter a password. The same error occurs if I use
    >> `emacs -q'. Could this be a bug?

    > Hmm. Could you show a full transcript of what youʼre doing? Donʼt
    > forget that the let-binding is only valid within the let, not for
    > the entire session. If you want it to valid all the time you'll
    > need to do

    > (setq read-hide-char ?.)

Ok, that explains things I think. At the beginning, I wanted to set `.'
as the read-hide-char in my emacs-init file, but the doc string for
read-hide-char says it should never be set globally. I took that to mean
never to set via a `setq'. This seemed to be confirmed in comments of
the lisp/subr.el file, where using a let-bind is suggested. Hence my
efforts at writing a `let' to my emacs-init, which maybe were a little
naive.

The (setq read-hide-char ?.) does indeed work, and seems to do so
without creating errors elsewhere. So I'll leave it in my ~/.emacs for
now. However, I am now curious as to what the sentence, `This variable
should never be set globally.' means in the doc-string for
`read-hide-char'. Perhaps the doc-string could be amplified slightly?

Thank you very much for your help.

Best wishes,

Colin.



  reply	other threads:[~2018-07-30 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30  7:23 Change stars as read-hide-char Colin Baxter
2018-07-30  8:01 ` Robert Pluim
2018-07-30  8:54   ` Colin Baxter
2018-07-30 10:19     ` Robert Pluim
2018-07-30 11:14       ` Colin Baxter [this message]
2018-07-30 13:30         ` Robert Pluim

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=877eldnffm.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.org \
    /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).