unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
Cc: 55645@debbugs.gnu.org
Subject: bug#55645: src/print.c; print_object changes make it impossible to compare elisp code across versions
Date: Mon, 18 Jul 2022 11:13:10 -0700	[thread overview]
Message-ID: <CA+G3_PO6t6fJof3tOmSB9BFtacsiF+x7enhpwziA142H7JUVew@mail.gmail.com> (raw)
In-Reply-To: <CA+G3_POkK1nOJuFAx6zVMJQYvaQBS3Vxcz3eDMmABYU9fwEM8Q@mail.gmail.com>

Ok. I went with the band non-portable symbols solution and it works.
Here's to hoping nothing changes for another 30 years! Will close.





  reply	other threads:[~2022-07-18 18:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 23:12 bug#55645: src/print.c; print_object changes make it impossible to compare elisp code across versions Tom Gillespie
2022-05-26 12:03 ` Lars Ingebrigtsen
2022-05-26 15:56   ` Tom Gillespie
2022-05-27 10:33     ` Lars Ingebrigtsen
2022-05-27 19:19       ` Tom Gillespie
2022-05-28 10:39         ` Lars Ingebrigtsen
2022-05-28 17:54           ` Tom Gillespie
2022-05-29 13:15             ` Lars Ingebrigtsen
2022-05-29 15:14               ` Eli Zaretskii
2022-05-29 21:03                 ` Tom Gillespie
2022-06-04  9:15                   ` Eli Zaretskii
2022-06-04 11:35                     ` Lars Ingebrigtsen
2022-06-04 11:53                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 12:09                         ` Lars Ingebrigtsen
2022-06-04 12:18                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 13:14                             ` Lars Ingebrigtsen
2022-06-04 13:30                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 13:35                                 ` Lars Ingebrigtsen
2022-06-04 13:47                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-06 23:30                     ` Tom Gillespie
2022-06-07 16:35                       ` Eli Zaretskii
2022-07-11 11:22                         ` Lars Ingebrigtsen
2022-07-11 18:43                           ` Tom Gillespie
2022-07-12 12:44                             ` Lars Ingebrigtsen
2022-07-13 23:26                               ` Tom Gillespie
2022-07-14 17:22                                 ` Lars Ingebrigtsen
2022-07-14 21:36                                   ` Tom Gillespie
2022-07-18 18:13                                     ` Tom Gillespie [this message]
2022-07-12  3:04                           ` Richard Stallman
2022-07-12 12:45                             ` Lars Ingebrigtsen
2022-07-13  3:16                               ` Richard Stallman
2022-05-28 23:14         ` Richard Stallman

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=CA+G3_PO6t6fJof3tOmSB9BFtacsiF+x7enhpwziA142H7JUVew@mail.gmail.com \
    --to=tgbugs@gmail.com \
    --cc=55645@debbugs.gnu.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 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).