all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [Emacs-diffs] master 75336a2: Merge branch 'feature/standard-test-location'
Date: Thu, 03 Dec 2015 17:31:12 +0000	[thread overview]
Message-ID: <87wpsvo2vz.fsf@russet.org.uk> (raw)
In-Reply-To: <86k2oysknp.fsf@stephe-leake.org> (Stephen Leake's message of "Tue, 1 Dec 2015 01:16:58 -0600")

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>>> The .el extension points to emacs-lisp-mode already, doesn't it?
>>
>> Then you are testing two things: auto-mode-alist *and* indentation.
>
> Yes. But that's a Good Thing.
>
> And it will significantly reduce perceived "noise" in the test sources,
> which is also a Good Thing.
>
> The need to set the mode via a local variable documents that you are not
> expecting auto-mode-alist to handle it.

I think that you are partly right about this, although, of course, you
are assuming that indentation tests WILL be in files. As is stands
sisyphus does not make this assumption -- it's possible to drop code
inline into tests also. There are advantages to this for short pieces of
code.

Still, you are correct -- auto-mode-alist should be usable if wanted.


>>> Have you considered just adding a few functions to ert-x? As a first step, I
>>> mean.
>>
>> Not yet, no. I wanted to get something working and useful first. The
>> problem with adding it to ert-x is that it's core, and I think I'd
>> rather have it in ELPA in the short term.
>
> I think "it" here is your new test macros, that make it easier to write
> indentation tests?
>
> They are useful for testing core code, so they should be in core. At
> least until we get "core ELPA" packages working; then this would be a
> candidate for moving to Gnu ELPA.
>
> Putting them in a separate package for now probably makes sense; once
> they are fully polished we can decide if they should be in ert or ert-x.


I'd agree with all this also. I think that my packages will be good for
testing core. I'm not making any decisions till I find out how long it
takes me write. Maybe "core ELPA" will be working by then. Who knows!

Phil



  reply	other threads:[~2015-12-03 17:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151126211432.7647.1395@vcs.savannah.gnu.org>
     [not found] ` <E1a23s9-00020K-OH@vcs.savannah.gnu.org>
2015-11-28 18:56   ` [Emacs-diffs] master 75336a2: Merge branch 'feature/standard-test-location' Dmitry Gutov
2015-11-28 18:59     ` Eli Zaretskii
2015-11-28 19:20     ` Phillip Lord
2015-11-28 20:06       ` Dmitry Gutov
2015-11-28 21:20         ` Phillip Lord
2015-11-29  4:16           ` Dmitry Gutov
2015-11-29 17:50             ` automated indent tests Stephen Leake
2015-11-29 18:00               ` Dmitry Gutov
2015-11-29 21:15             ` [Emacs-diffs] master 75336a2: Merge branch 'feature/standard-test-location' Phillip Lord
2015-12-01  7:16               ` Stephen Leake
2015-12-03 17:31                 ` Phillip Lord [this message]
2015-11-28 20:15     ` Ken Brown
2015-11-28 20:52       ` Dmitry Gutov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wpsvo2vz.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.