From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: bzg@gnu.org, 16493@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#16493: 24.3.50; (setq search-invisible t) is useless, let's allow to turn visible-mode temporarily on
Date: Sun, 12 May 2019 07:23:33 +0300 [thread overview]
Message-ID: <831s14cncq.fsf@gnu.org> (raw)
In-Reply-To: <jwvr29469uc.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Sat, 11 May 2019 16:06:12 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Noam Postavsky <npostavs@gmail.com>, bzg@gnu.org, 16493@debbugs.gnu.org
> Date: Sat, 11 May 2019 16:06:12 -0400
>
> >> Starting from t, (add-to-invisibility-spec 'foo) also has the weird
> >> result that it *reduces* the number of properties which cause
> >> invisibility (from infinity to 2).
> > Yes, but I don't see that as a problem.
>
> Here's another way to look at it:
>
> Give me a circumstance where an Elisp package can make use of the fact
> that buffer-invisibility-spec defaults to t?
That's the wrong way of looking at the issue, if you want to talk
about the aspects that I called "confusing". I see no technical
problems with using (t) instead of t, I just said that it confuses the
heck out of me, because its semantics is not clear by just looking at
the value.
next prev parent reply other threads:[~2019-05-12 4:23 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
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 [this message]
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=831s14cncq.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.