From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
Cc: 22800@debbugs.gnu.org, 22799@debbugs.gnu.org
Subject: bug#22799: bug#22800: [PATCH] Unit tests for `forward-sexp'
Date: Thu, 25 Feb 2016 16:30:59 +1030 [thread overview]
Message-ID: <878u29xrac.fsf@gnus.org> (raw)
In-Reply-To: <1456343413-64418-2-git-send-email-aaron.s.hawley@gmail.com> (Aaron S. Hawley's message of "Wed, 24 Feb 2016 14:50:13 -0500")
"Aaron S. Hawley" <aaron.s.hawley@gmail.com> writes:
> diff --git a/test/lisp/forward-sexp-tests.el b/test/lisp/forward-sexp-tests.el
If I've understood the naming methodology in the Emacs test harness, all
the -tests.el files have to be named after a file under ../lisp/
somewhere. Since there isn't a lisp/forward-sexp.el file, running the
tests fail:
larsi@mouse:~/src/emacs/trunk/test$ make lisp/forward-sexp-tests
make[1]: Entering directory '/home/larsi/src/emacs/trunk/test'
make[1]: *** No rule to make target '/home/larsi/src/emacs/trunk/test/../lisp/forward-sexp.el', needed by 'lisp/forward-sexp-tests.log'. Stop.
make[1]: Leaving directory '/home/larsi/src/emacs/trunk/test'
Makefile:142: recipe for target 'lisp/forward-sexp-tests' failed
make: *** [lisp/forward-sexp-tests] Error 2
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-25 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 19:50 bug#22799: [PATCH] Unit tests for `forward-sexp' Aaron S. Hawley
2016-02-24 19:50 ` bug#22800: " Aaron S. Hawley
2016-02-25 6:00 ` Lars Ingebrigtsen [this message]
2016-02-25 15:40 ` bug#22799: [PATCH] Unit tests for `forward-sexp' and related commands Aaron S. Hawley
2016-02-25 15:45 ` bug#22800: " Aaron S. Hawley
2016-02-25 15:45 ` Aaron S. Hawley
2016-02-26 5:49 ` Lars Ingebrigtsen
2016-02-24 20:07 ` bug#22799: [PATCH] Unit tests for `forward-sexp' Aaron S. Hawley
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=878u29xrac.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22799@debbugs.gnu.org \
--cc=22800@debbugs.gnu.org \
--cc=aaron.s.hawley@gmail.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 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.