all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: akater <nuclearspace@gmail.com>, 41814@debbugs.gnu.org
Subject: bug#41814: defmethod cl-print-object is not entirely reliable
Date: Sun, 13 Jun 2021 13:23:33 +0200	[thread overview]
Message-ID: <875yyi57pm.fsf@gnus.org> (raw)
In-Reply-To: <878sgs4m2b.fsf@web.de> (Michael Heerdegen's message of "Fri, 12 Jun 2020 12:26:20 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Yes, this doesn't use cl-print at all.  And I think that makes sense:
> when inserting a value into a buffer, readability is important (that
> doesn't make a difference in your case, though).
>
> We have different printers now in Elisp, and implementing
> cl-print-object only has an effect when cl-print is used.

Yup -- I don't think there's a bug here.  The standard Emacs
eval/printing commands aren't affected by the cl print definitions, but
instead uses a slew of different things to DWIM the printing, and we
can't change that.

> I dunno if that fact could be better documented to avoid this kind of
> confusion.

I don't think anything in our documentation (as far as I know) should
lead anybody to think that doing something in cl-print should affect
`C-u C-x C-e', so I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-06-13 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 20:05 bug#41814: defmethod cl-print-object is not entirely reliable akater
2020-06-12 10:26 ` Michael Heerdegen
2020-07-06 19:01   ` akater
2021-06-13 11:23   ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yyi57pm.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=41814@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=nuclearspace@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.