From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: ERT indentation testing
Date: Thu, 19 May 2011 08:56:07 -0300 [thread overview]
Message-ID: <jwvmxiizz24.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87fwobasiy.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 19 May 2011 05:33:57 -0500")
>>> This can be done with ERT, right? A bunch of .cc files with file-local
>>> variables could be indented "properly" for those variables. Then the
>>> test logic for each file is
SM> [...]
>>> Plus, of course, it's not limited to .cc files. It would work just as
>>> well for .c, .pl, .el, whatever.
SM> Yup, we already have such files in test/indent.
> Yes, I see that now (I didn't see the commit for those, cool!)
> We should have .c and .cc files with the major indentation styles
> specified as file-local variables, plus .ini, Perl, Java, Python, and of
> course Lisp (CL and ELisp). Should I add those?
Feel free. I only added the ones I actually worked on. BTW, the
octave.m testcase is too long for that kind of test (although the length
was instrumental in fixing some performance bugs).
Stefan
next prev parent reply other threads:[~2011-05-19 11:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 23:21 [RFC PATCH] setting indentation styles via `c-file-style' fails to actually change indentation Nix
2011-05-18 0:17 ` Stefan Monnier
2011-05-18 20:28 ` Nix
2011-05-18 21:08 ` ERT indentation testing (was: [RFC PATCH] setting indentation styles via `c-file-style' fails to actually change indentation) Ted Zlatanov
2011-05-18 22:19 ` ERT indentation testing Stefan Monnier
2011-05-19 10:33 ` Ted Zlatanov
2011-05-19 11:56 ` Stefan Monnier [this message]
2011-06-01 21:30 ` Ted Zlatanov
2011-06-02 18:43 ` Ted Zlatanov
2011-06-03 0:04 ` Stefan Monnier
2011-06-03 11:33 ` Ted Zlatanov
2011-06-03 12:12 ` martin rudalics
2011-06-03 15:06 ` extra-interactive functions (was: ERT indentation testing) Ted Zlatanov
2011-06-03 15:27 ` extra-interactive functions martin rudalics
2011-06-03 16:11 ` Ted Zlatanov
2011-06-03 18:59 ` martin rudalics
2011-06-03 19:10 ` Ted Zlatanov
2011-06-03 20:54 ` martin rudalics
2011-06-08 10:44 ` ERT indentation testing Ted Zlatanov
2011-06-08 15:24 ` Stefan Monnier
2011-06-09 16:05 ` Ted Zlatanov
2011-06-10 20:41 ` Stefan Monnier
2011-06-01 14:31 ` [RFC PATCH] setting indentation styles via `c-file-style' fails to actually change indentation Nix
2011-06-02 12:24 ` Alan Mackenzie
2011-06-02 13:35 ` Stefan Monnier
2011-06-02 16:47 ` Nix
2011-06-02 21:15 ` Alan Mackenzie
2011-06-02 21:43 ` Nix
2011-06-05 15:06 ` Alan Mackenzie
2011-07-24 10:07 ` Kan-Ru Chen
2011-08-05 14:14 ` Nix
2011-05-18 3:27 ` Glenn Morris
2011-05-18 11:02 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2011-06-02 12:37 ERT indentation testing Alan Mackenzie
2011-06-02 14:23 ` Ted Zlatanov
2011-06-03 11:48 ` Ted Zlatanov
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=jwvmxiizz24.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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).