From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: asking for advice for changing the cfengine.el progmode to support CFEngine 3.x
Date: Thu, 30 Jun 2011 13:28:20 -0500 [thread overview]
Message-ID: <87fwmrtbqz.fsf@lifelogs.com> (raw)
In-Reply-To: jwvr56bs3tq.fsf-monnier+emacs@gnu.org
On Thu, 30 Jun 2011 12:11:16 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> As it is, except for highlighting string interpolation, it's great for
>> everyday work. So I want to know if there's any reason to pursue
>> SMIE--what more can it do for this mode--and if there are any other
>> comments on the code. If not, I'll remove the unnecessary parts, commit
>> it, and make a note in cfengine.el about the newer version.
SM> I don't have time to look further into it. The strength of SMIE is that
SM> it structures the indentation code in a way that makes it fairly robust
SM> (in terms of indentation when the style is unusual, such as newlines
SM> placed at unexpected places) once it works and also that the most
SM> difficult part is the parsing, but that this then can be used for more
SM> than indentation (e.g. for structural navigation, for blink-matching,
SM> hopefully in the future it will also be used for alignment (in the
SM> sense of M-x align)).
Well, that's why I did the work of extracting the full cfengine 3.x
grammar, so you could see if SMIE made sense or a standard parser was
better. But it really seems like modifying the standard syntax tables
plus a little bit of indentation logic works OK without SMIE, so I was
asking what else would I get if I put the extra work into writing a SMIE
grammar.
SM> But SMIE is far from perfect and is not meant to be "the one and
SM> only way to do it", so if it doesn't work for you, don't use it.
I want to learn it and use it. It's just not easy, so please have
patience. I'm learning OPGs from scratch.
Ted
prev parent reply other threads:[~2011-06-30 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:11 asking for advice for changing the cfengine.el progmode to support CFEngine 3.x Ted Zlatanov
2011-06-17 22:02 ` Stefan Monnier
2011-06-20 20:42 ` Ted Zlatanov
2011-06-21 14:59 ` Stefan Monnier
2011-06-21 19:26 ` Ted Zlatanov
2011-06-22 17:44 ` Stefan Monnier
2011-06-22 21:24 ` Ted Zlatanov
2011-06-23 21:31 ` Ted Zlatanov
2011-06-27 15:44 ` Ted Zlatanov
2011-06-30 12:47 ` Ted Zlatanov
2011-06-30 16:03 ` Stefan Monnier
2011-06-30 18:25 ` Ted Zlatanov
2011-06-30 21:10 ` Stefan Monnier
2011-06-30 21:29 ` Ted Zlatanov
2011-07-01 8:19 ` Eli Zaretskii
2011-07-01 10:15 ` Ted Zlatanov
2011-07-01 11:22 ` Eli Zaretskii
2011-07-01 13:03 ` Ted Zlatanov
2011-06-30 16:11 ` Stefan Monnier
2011-06-30 18:28 ` Ted Zlatanov [this message]
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=87fwmrtbqz.fsf@lifelogs.com \
--to=tzz@lifelogs.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).