all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joaotavora@gmail.com (João Távora)
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org,
	Noam Postavsky <npostavs@gmail.com>,
	tino.calancha@gmail.com
Subject: Re: Finding macro-generated ert test definitions
Date: Thu, 24 May 2018 17:50:26 +0100	[thread overview]
Message-ID: <87lgc9ov59.fsf@gmail.com> (raw)
In-Reply-To: <83efi1atw5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 May 2018 19:41:14 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> +@code{ert-find-test-other-window}) if the test was loaded from a file.
>> +Since this relies on a textual search of the source, it will likely
>> +fail if you use a macro which expands into the @code{ert-deftest}
>> +form, especially if the test name itself is absent from the source.
>
> Looks like a good addition, thanks.

Nothing against this, but can anyone comment on the possiblity of
recording actual position information in bytecomp.el, so we wouldn't
have this limitation in the first place (and hence wouldn't need to
document it)?

João



  reply	other threads:[~2018-05-24 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 22:55 Finding macro-generated ert test definitions (WAS: [Emacs-diffs] master bb591f139f: Enhance CC Mode's fontification, etc., of unterminated strings.) Noam Postavsky
2018-05-23  0:52 ` Finding macro-generated ert test definitions João Távora
2018-05-23 14:54 ` Finding macro-generated ert test definitions (WAS: [Emacs-diffs] master bb591f139f: Enhance CC Mode's fontification, etc., of unterminated strings.) Eli Zaretskii
2018-05-23 22:40   ` Noam Postavsky
2018-05-24 16:41     ` Eli Zaretskii
2018-05-24 16:50       ` João Távora [this message]
2018-05-24 22:34         ` Finding macro-generated ert test definitions Noam Postavsky
2018-05-24 23:00           ` João Távora

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=87lgc9ov59.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@gmail.com \
    --cc=tino.calancha@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.