From: Xu Chunyang <mail@xuchunyang.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30816@debbugs.gnu.org
Subject: bug#30816: 27.0.50; Info documentation of previous-property-change is not very clear
Date: Thu, 15 Mar 2018 03:04:30 +0800 [thread overview]
Message-ID: <m2h8pieawx.fsf@xuchunyang.me> (raw)
In-Reply-To: <833712sjw9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Mar 2018 18:26:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Xu Chunyang <mail@xuchunyang.me>
>> Date: Wed, 14 Mar 2018 17:58:32 +0800
>>
>>
>> (info "(elisp) Property Search") has the following:
>>
>> -- Function: previous-property-change pos &optional object limit
>> This is like ‘next-property-change’, but scans back from POS
>> instead of forward. If the value is non-‘nil’, it is a position
>> ^^^^^^^^^
>> less than or equal to POS; it equals POS only if LIMIT equals POS.
>> ^^
>>
>> I don't understand the second sentence. What "the value" stands for?
>
> When we say "value" in the context of describing a function, we mean
> the value the function returns. In this case, the value returned by
> previous-property-change.
I see. I notice the term "the return value" is also used in some place
in the manual.
>> If it stands for LIMIT, what "it" stands for?
>
> "It" stands for the value returned by the function. the text says
> that the function returns the position of the previous change of the
> property, and that position could only be the same as the starting
> position POS if LIMIT is equal to POS, i.e. if LIMIT forces the
> function to stop at its starting position.
>
> I hope this clarifies the issue.
Thanks for your explanation. Feel free to close the issue.
next prev parent reply other threads:[~2018-03-14 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 9:58 bug#30816: 27.0.50; Info documentation of previous-property-change is not very clear Xu Chunyang
2018-03-14 16:26 ` Eli Zaretskii
2018-03-14 19:04 ` Xu Chunyang [this message]
2018-03-14 19:35 ` 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
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=m2h8pieawx.fsf@xuchunyang.me \
--to=mail@xuchunyang.me \
--cc=30816@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).