From: Dmitry Gutov <dgutov@yandex.ru>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 305dbc7 2/4: Move description of value to syntax-ppss function.
Date: Sat, 15 Feb 2020 17:14:31 +0200 [thread overview]
Message-ID: <2ade5926-99c8-0052-b1e3-6ba4b46b972c@yandex.ru> (raw)
In-Reply-To: <CAM-tV-8C_MFDKBxErPVw+_+J3LSzqKTMQxdMXkVHsnLa=DdVvg@mail.gmail.com>
On 15.02.2020 16:55, Noam Postavsky wrote:
>>> - (comment-nesting nil :documentation "\
>>> + (comment nil :documentation "\
>>
>> Doesn't this name imply some other value? Like a string (comment opener
>> or its contents)?
>
> Hmm, you might be right about that. How about 'comment-depth': two
> characters shorter, and the other names also use "depth" rather than
> "nesting".
Sounds good.
>>> - (open-paren-positions
>>> + (open-parens
>>> nil :documentation
>>> "List of positions of currently open parens, outermost first.")
>>> - (two-character-syntax nil :documentation "\
>>> + (syntax-sequence nil :documentation "\
>>> When the last position scanned holds the first character of a
>>> (potential) two character construct, the syntax of that position,
>>> otherwise nil. That construct can be a two character comment
>>
>> These look okay to me.
>
> I'm actually feeling that the two-character-syntax one should be left
> as is, it's kind of obscure so having a longer and more explicit name
> seems better.
Agree (I also have never used it).
>> min-depth too, but, like last-complete-sexp-start, these fields in
>> values returned by syntax-ppss are unreliable/undefined, so they won't
>> be used in most Lisp programs anyway.
>
> I might be biased by having worked on the lisp indentation code which
> uses those fields quite a bit.
So... Lisp indentation code calls parse-partial-sexp directly?
Anyway, I said min-depth is okay, but if we're going to have
comment-depth, maybe min-depth starts to sound more ambiguous.
next prev parent reply other threads:[~2020-02-15 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191030121649.15369.13207@vcs0.savannah.gnu.org>
[not found] ` <20191030121651.BFCF8204DF@vcs0.savannah.gnu.org>
2019-10-30 14:59 ` master 305dbc7 2/4: Move description of value to syntax-ppss function Dmitry Gutov
2019-10-30 15:03 ` Lars Ingebrigtsen
2019-10-30 15:13 ` Dmitry Gutov
2019-10-30 15:22 ` Lars Ingebrigtsen
2019-10-30 15:26 ` Dmitry Gutov
2019-10-30 15:30 ` Lars Ingebrigtsen
2019-10-30 15:29 ` Lars Ingebrigtsen
2019-10-30 16:13 ` Dmitry Gutov
2019-10-30 16:17 ` Lars Ingebrigtsen
2019-10-30 16:47 ` Dmitry Gutov
2019-10-30 17:03 ` Lars Ingebrigtsen
2019-10-30 19:39 ` Stefan Monnier
2019-10-30 20:28 ` Lars Ingebrigtsen
2019-12-13 12:34 ` Noam Postavsky
2019-12-13 13:03 ` Dmitry Gutov
2019-12-17 16:28 ` Lars Ingebrigtsen
2020-02-15 14:55 ` Noam Postavsky
2020-02-15 15:14 ` Dmitry Gutov [this message]
2020-02-15 16:23 ` Noam Postavsky
2020-02-23 14:11 ` Noam Postavsky
2019-10-30 20:34 ` Alan Mackenzie
2019-10-30 20:41 ` Dmitry Gutov
2019-10-31 1:45 ` Stefan Monnier
2019-10-31 14:06 ` Lars Ingebrigtsen
2019-10-30 20:47 ` Alan Mackenzie
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=2ade5926-99c8-0052-b1e3-6ba4b46b972c@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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).