From: John Wiegley <jwiegley@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Permission requested to merge branch comment-cache into master.
Date: Sat, 12 Mar 2016 16:02:28 -0800 [thread overview]
Message-ID: <m2a8m3s0rv.fsf@newartisans.com> (raw)
In-Reply-To: <20160312231713.GD10781@acm.fritz.box> (Alan Mackenzie's message of "Sat, 12 Mar 2016 23:17:13 +0000")
>>>>> Alan Mackenzie <acm@muc.de> writes:
> This is not possible, and the suggestion that it is is mischievous.
I try to reserve my mischief for things are much more fun, I assure you. :)
> The two approaches are fundamentally different. They aim to do different
> things, and they do them in very different ways.
What I don't want to happen is that a disagreement between contributors
results in the maintenance of two separate solutions to similar problems, just
because of a difference in design and a lack of agreement.
Stefan had the prerogative to include his solution before, so I understand why
it's in emacs-25 now. But your concerns lead me to believe that his code
should be revisited. If `syntax-ppss' is not doing the job we need it to do --
to the extent that you have to implement new code to work around it -- that
indicate a potential problem.
I also want to make sure it's not just a documentation failure, or lack of
communication, before either ditching syntax-ppss, or introducing a new
mechanism to live alongside it.
Is it possible to summarize why syntax-ppss is not fulfilling your needs,
other than it being buggy? Because if that's the only issue, we can fix the
code.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-03-13 0:02 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 [this message]
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
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=m2a8m3s0rv.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@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).