From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/accurate-warning-pos: next steps.
Date: Tue, 11 Dec 2018 21:35:29 +0000 [thread overview]
Message-ID: <20181211213529.GE4911@ACM> (raw)
In-Reply-To: <jwvimzz93jf.fsf-monnier+gmane.emacs.devel@gnu.org>
Hello, Stefan.
On Tue, Dec 11, 2018 at 16:11:21 -0500, Stefan Monnier wrote:
> > As for amending the reader and byte compiler to work with "Stefan's
> > format",
> BTW, I have suggested various approaches, not just one.
Apologies, this is true. And you also expressed a desire not to work on
the problem. This is accepted and respected.
> And all of them have been just rough sketches.
One of them was what I've implemented as scratch/accurate-warning-pos. :-)
> Whether and how they'd work is an open question.
The one Paul and I have been referring to was the one where the reader
would return extended lists containing location info alongside the
actual Lisp Object.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-12-11 21:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 18:00 scratch/accurate-warning-pos: next steps Alan Mackenzie
2018-12-10 18:15 ` Eli Zaretskii
2018-12-10 18:28 ` Alan Mackenzie
2018-12-10 18:39 ` Eli Zaretskii
2018-12-10 19:35 ` Alan Mackenzie
2018-12-10 20:06 ` Eli Zaretskii
2018-12-10 21:03 ` Alan Mackenzie
2018-12-11 6:41 ` Eli Zaretskii
2018-12-11 19:21 ` Stefan Monnier
2018-12-11 19:07 ` Stefan Monnier
2018-12-10 23:54 ` Paul Eggert
2018-12-11 11:34 ` Alan Mackenzie
2018-12-11 18:05 ` Paul Eggert
2018-12-11 19:20 ` Alan Mackenzie
2018-12-11 19:59 ` Paul Eggert
2018-12-11 20:51 ` Alan Mackenzie
2018-12-11 21:11 ` Stefan Monnier
2018-12-11 21:35 ` Alan Mackenzie [this message]
2018-12-11 22:58 ` Stefan Monnier
2018-12-11 21:43 ` Paul Eggert
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=20181211213529.GE4911@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).