From: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Technically correct or conceptually easier?
Date: Fri, 10 Apr 2020 11:00:11 -0300 [thread overview]
Message-ID: <87mu7jh250.fsf@oitofelix.com> (raw)
In-Reply-To: <jwvv9mhlh8x.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 02 Apr 2020 17:22:21 -0400")
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> If the value is a list, disregard ‘buffer-read-only’ and disregard a
>> ‘read-only’ text property if the property value is a member of the
>> list.
>> Well, nil is a list.
> I think this case is a documentation error: it should say "a non-empty
> list", although admittedly, the context makes it clearish what is meant.
Fair enough. Albeit ~(and (not null) list)~ and ~cons~ are the same
class of Lisp objects, perhaps the former appeals more to /intention,
intuition or common sense/ (and thus maybe it’s more appropriate for a
docstring)[1] than the latter --- even if formally more complex.
Footnotes:
[1] Although I’m inclined to think that in situations like this, if the
very same objects are seem as somewhat distinct things because of
different (but equivalent) descriptions, the problem is with the human
understanding and bias towards reality: distinction without a
difference.
--
Bruno Félix Rezende Ribeiro (oitofelix) [0x28D618AF]
<http://oitofelix.freeshell.org/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-10 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 20:23 Technically correct or conceptually easier? Bruno Félix Rezende Ribeiro
2020-04-02 21:22 ` Stefan Monnier
2020-04-04 2:09 ` chad
2020-04-10 14:00 ` Bruno Félix Rezende Ribeiro [this message]
2020-04-04 1:24 ` Richard Stallman
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=87mu7jh250.fsf@oitofelix.com \
--to=oitofelix@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.