From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: bzg@gnu.org, 16493@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#16493: 24.3.50; (setq search-invisible t) is useless, let's allow to turn visible-mode temporarily on
Date: Wed, 01 May 2019 20:02:07 +0300 [thread overview]
Message-ID: <83h8aeqfao.fsf@gnu.org> (raw)
In-Reply-To: <87lfzqo11s.fsf@gmail.com> (message from Noam Postavsky on Wed, 01 May 2019 07:40:31 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, bzg@gnu.org, 16493@debbugs.gnu.org
> Date: Wed, 01 May 2019 07:40:31 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stefan Monnier <monnier@iro.umontreal.ca>
>
> >> PS: To fix this quirk, we should change buffer-invisibility-spec's
> >> default value to nil (or `(t)`, maybe) instead of t.
>
> (t) makes sense, I'd say.
The difference (or lack thereof) between t and (t) is something that's
confusing, and should be preferably avoided.
> It's not a change to semantics though, just the default value. And
> starting from the current default of t, if some code does
> (add-to-invisibility-spec 'foo) followed by
> (remove-from-invisibility-spec 'foo) you get (t), so arguably just
> starting from there in the first place makes things less confusing than
> they are now.
I'd rather we fixed the remove-from-invisibility-spec result than
start promoting (t).
next prev parent reply other threads:[~2019-05-01 17:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 14:55 bug#16493: 24.3.50; (setq search-invisible t) is useless, let's allow to turn visible-mode temporarily on Bastien Guerry
2014-01-21 7:57 ` Juri Linkov
2014-01-21 11:15 ` Bastien
2014-01-21 11:19 ` Bastien
2014-01-21 13:54 ` Stefan Monnier
2014-01-21 14:20 ` Bastien
2014-11-05 15:30 ` Stefan Monnier
2014-11-09 19:30 ` Juri Linkov
2014-11-18 10:41 ` Bastien
2014-11-18 16:48 ` Stefan Monnier
2014-11-19 8:53 ` Bastien
2018-04-28 14:28 ` Bastien
2018-04-28 18:11 ` Stefan Monnier
2018-04-29 9:50 ` Bastien
2019-04-30 4:34 ` Noam Postavsky
2019-04-30 5:06 ` Eli Zaretskii
2019-04-30 11:15 ` Noam Postavsky
2019-04-30 12:13 ` Stefan Monnier
2019-04-30 12:24 ` Noam Postavsky
2019-04-30 12:45 ` Stefan Monnier
2019-04-30 15:21 ` Eli Zaretskii
2019-05-01 11:40 ` Noam Postavsky
2019-05-01 17:02 ` Eli Zaretskii [this message]
2019-05-01 17:29 ` Stefan Monnier
2019-05-11 15:27 ` Noam Postavsky
2019-05-11 15:50 ` Eli Zaretskii
2019-05-11 20:06 ` Stefan Monnier
2019-05-12 4:23 ` Eli Zaretskii
2019-05-12 15:35 ` Stefan Monnier
2019-05-12 15:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8aeqfao.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16493@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.