all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 29721-done@debbugs.gnu.org
Subject: bug#29721: 26.0; doc string of `invisible-p'
Date: Sat, 16 Dec 2017 12:22:00 +0200	[thread overview]
Message-ID: <83k1xnrn07.fsf@gnu.org> (raw)
In-Reply-To: <e026aea4-575f-4d2e-ac92-218f7799539d@default> (message from Drew Adams on Fri, 15 Dec 2017 09:41:55 -0800 (PST))

> Date: Fri, 15 Dec 2017 09:41:55 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> The doc string is unclear.
> 
>   "(invisible-p POS-OR-PROP)
> 
>    Non-nil if the property makes the text invisible."
> 
> What property?  What text?

Thanks, fixed.

>   "The non-nil value returned can be t for truly invisible text or
>    something else if the text is replaced by an ellipsis."
> 
> Huh?  What is "truly invisible"?

"Truly" because text with 'invisible' property could be still visible,
depending on buffer-invisibility-spec.  I added the reference to that.

> What "something else"?  Does "something else" include `nil'?  [...]
> What does the (unspecified!) value signify in the case of "the text"
> (?) being "replaced by an ellipsis"?

The value itself is of no significance, besides the fact that it's not
nil and not t, so I see no reason to document what it is, exactly.  If
you are really interested, you can read the code, or try calling that
function on invisible text replaced with an ellipsis, then you will
see that the value is truly of no importance.

> What does it mean for "the text" to be replaced by an ellipsis?

That is a well-known feature, see (elisp)Invisible Text.  I hope a
reference to buffer-invisibility-spec makes it even more clear.





      reply	other threads:[~2017-12-16 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 17:41 bug#29721: 26.0; doc string of `invisible-p' Drew Adams
2017-12-16 10:22 ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k1xnrn07.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29721-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.