unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Permission requested to merge branch comment-cache into master.
Date: Sun, 13 Mar 2016 19:38:08 -0400	[thread overview]
Message-ID: <56E5F9E0.4030501@gmail.com> (raw)
In-Reply-To: <20160313225247.GJ1871@acm.fritz.box>


[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]

On 03/13/2016 06:52 PM, Alan Mackenzie wrote:
> They're not broken, not of themselves.  Would you agree that because
> syntax-ppss doesn't always return the defined value according to its
> spec, we should move away from using it?

Hi Alan,

Before I read this thread, I never really paid attention to the fact that syntax-ppss needed widening; I would guess (but of course I can't be sure) that many did the same thing. In fact, I've only ever used syntax-ppss to decide whether I was in a comment, or in a string, and possibly where it sarted, so if syntax-ppss was changed my code would benefit.
On the other hand, if a better behaved alternative is introduced, my code will have to be manually updated; thus I would very much like it if syntax-ppss was changed :)

Just offering an opinion of course. Thanks for your efforts on this!
Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-03-13 23:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12  0:28 Permission requested to merge branch comment-cache into master Alan Mackenzie
2016-03-12  7:32 ` Eli Zaretskii
2016-03-12 10:08   ` Alan Mackenzie
2016-03-12 11:14     ` Eli Zaretskii
2016-03-12 11:50       ` Alan Mackenzie
2016-03-12 12:31         ` Eli Zaretskii
2016-03-12 13:11           ` Alan Mackenzie
2016-03-12 21:38           ` John Wiegley
2016-03-12 23:17             ` Alan Mackenzie
2016-03-13  0:02               ` John Wiegley
2016-03-13 15:20                 ` Alan Mackenzie
2016-03-13 16:04                   ` Clément Pit--Claudel
2016-03-13 16:12                     ` Dmitry Gutov
2016-03-13 19:12                     ` Alan Mackenzie
2016-03-13 22:27                       ` Stefan Monnier
2016-03-13 22:52                         ` Alan Mackenzie
2016-03-13 23:38                           ` Clément Pit--Claudel [this message]
2016-03-14  0:20                           ` Stefan Monnier
2016-03-14  6:32                           ` Andreas Röhler
2016-03-14 11:27                             ` Alan Mackenzie
2016-03-13 17:07                   ` John Wiegley
2016-03-13 19:04                     ` Alan Mackenzie
2016-03-14  0:25                   ` Dmitry Gutov
2016-03-14  1:11                   ` Stefan Monnier
2016-03-14 13:28                     ` Alan Mackenzie
2016-03-14 15:58                       ` Stefan Monnier
2016-03-13 18:03               ` Eli Zaretskii
2016-03-12 13:23 ` Dmitry Gutov
2016-03-12 14:06   ` Alan Mackenzie
2016-03-12 21:39   ` John Wiegley
2016-03-13 17:22 ` Stefan Monnier

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=56E5F9E0.4030501@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=emacs-devel@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).