From: "João Távora" <joaotavora@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>,
Tino Calancha <tino.calancha@gmail.com>
Subject: Re: Finding macro-generated ert test definitions
Date: Fri, 25 May 2018 00:00:38 +0100 [thread overview]
Message-ID: <CALDnm53okDDrdf0OdayvThrirgG09qT-iDDqLv37Ex_kB0oRfg@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-8ZYsS85es4vjTXGNRykMkMz3V71-vAopZ0CE98nSqVzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Thu, May 24, 2018, 23:34 Noam Postavsky <npostavs@gmail.com> wrote:
> On 24 May 2018 at 12:50, João Távora <joaotavora@gmail.com> wrote:
>
> > 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)?
>
> Considering Bug#24592, it seems a bit optimistic to expect useful
> position information from the byte compiler
Doesn't seem like a huge showstopper though. That bug is about errors and
warnings, whereas we want the position of the containing top-level form
that originated the named function being compiled. That would be a
considerable improvement already.
I think Michael's suggesting about `definition-name' could help. That
> seems like something that should be mentioned in the elisp manual too,
> somewhere.
>
I didn't fully understand it yet, but I will try that too.
Thanks
[-- Attachment #2: Type: text/html, Size: 2133 bytes --]
prev parent reply other threads:[~2018-05-24 23:00 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 ` Finding macro-generated ert test definitions João Távora
2018-05-24 22:34 ` Noam Postavsky
2018-05-24 23:00 ` João Távora [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=CALDnm53okDDrdf0OdayvThrirgG09qT-iDDqLv37Ex_kB0oRfg@mail.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 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).