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

Colin Baxter <m43cap@yandex.com> writes:

>     > 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?

I suspect there are situations where having read-hide-char set causes
things to be hidden that shouldn't be, hence it should only be set
temporarily. Maybe someone on the list here knows.

Robert



      reply	other threads:[~2018-07-30 13:30 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
2018-07-30 13:30         ` Robert Pluim [this message]

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=874lgg97gx.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=m43cap@yandex.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).