unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Peter Milliken <peter.milliken@gmail.com>
Cc: 33441@debbugs.gnu.org
Subject: bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1?
Date: Thu, 22 Nov 2018 23:12:41 -0800	[thread overview]
Message-ID: <8fbb79e5-e852-73d8-9b2c-15ac14a9c5b8@cs.ucla.edu> (raw)
In-Reply-To: <CAA0nDNswo6wLn9SU6JVRYXtbv3N-s+fwuYfpAAoqBjcJ3iED3A@mail.gmail.com>

Peter Milliken wrote:
> Faking up a code snippet is not necessarily that easy - and, again, the
> problem described in 29220 sounds exactly like the issue I am having.

If it's a pain to reproduce the bug and if you have a different workaround which 
means the bug is low priority for you, then perhaps the best we can do for now 
is to merge bugs 29220 and 33441. I'll do that next.





  reply	other threads:[~2018-11-23  7:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  7:21 bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1? Peter Milliken
2018-11-20 20:56 ` Paul Eggert
2018-11-20 21:02   ` Noam Postavsky
2018-11-20 21:09     ` Peter Milliken
2018-11-20 21:17       ` Paul Eggert
2018-11-20 21:19       ` Noam Postavsky
2018-11-21  1:52         ` Peter Milliken
2018-11-21  3:27           ` Basil L. Contovounesios
2018-11-21  3:46           ` Eli Zaretskii
2018-11-21  4:21             ` Peter Milliken
2018-11-23  7:12               ` Paul Eggert [this message]
2019-04-01 23:55               ` Noam Postavsky
2019-04-02  2:51                 ` Peter Milliken
2019-04-02 13:29                   ` Noam Postavsky

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=8fbb79e5-e852-73d8-9b2c-15ac14a9c5b8@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=33441@debbugs.gnu.org \
    --cc=peter.milliken@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).