From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8693@debbugs.gnu.org
Subject: bug#8693: 24.0.50; doc strings in syntax.el
Date: Thu, 28 Apr 2016 12:59:47 +0200 [thread overview]
Message-ID: <87eg9qov6k.fsf@gnus.org> (raw)
In-Reply-To: <m38vrz8xbi.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 15 Jul 2011 15:53:21 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> 2. In doc strings of `syntax-propertize-function' and
>> `syntax-propertize-extend-region-functions': Please describe
>> START and END: their meanings and possible values (type).
>> Likewise NEW-START and NEW-END.
This seems like it has been fixed...
>> 3. IN doc string of `syntax-propertize-rules':
>> "if SYNTAX has the form (prog1 EXP . EXPS) then the value
>> returned by EXP will be applied to the buffer before running
>> EXPS and if EXP is a string it is also converted with
>> `string-to-syntax'."
>> Need descriptions of what EXP and EXPs are: meanings and possible values
>> (types).
I think the natural interpretation here is that EXP is of the same type
as SYNTAX otherwise described. (And EXPS is a list of whatever that is.)
>> 4. Doc string of `syntax-propertize-via-font-lock':
>> "Propertize for syntax in START..END using font-lock syntax..."
>> There are no parameters START, END. Please describe them and
>> relate them to the function.
Fixed.
>> 5. Doc string of `syntax-propertize': It would be clearer if POS were
>> described (e.g. as a buffer position). Same thing elsewhere that the meaning
>> might not be obvious. (Calling it POSITION would pretty much obviate the need
>> for a description.)
I've clarified.
>> 6. Doc string of `syntax-ppss-cache': Describe POS and PPSS.
>>
>> 7. Doc string of `syntax-ppss-last': Describe LAST-POS and LAST-PPSS.
Seems unnecessary for these internal things.
>> 8. Doc string of `syntax-ppss-flush-cache': Describe parameter
>> IGNORED.
It's... ignored.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-28 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 16:14 bug#8693: 24.0.50; doc strings in syntax.el Drew Adams
2011-05-18 16:28 ` Drew Adams
2011-05-18 22:10 ` Stefan Monnier
2011-05-18 22:46 ` Drew Adams
2011-07-15 13:53 ` Lars Magne Ingebrigtsen
2011-07-15 15:09 ` Drew Adams
2016-04-28 10:59 ` Lars Ingebrigtsen [this message]
2016-04-28 13:55 ` Drew Adams
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=87eg9qov6k.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=8693@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.