all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Matthew Newton <matt@knosis.org>
Cc: dpaduchikh@gmail.com, 24576@debbugs.gnu.org
Subject: bug#24576: 25.1; desktop.el does not fully preserve registers with macros
Date: Sat, 11 May 2019 08:15:50 -0400	[thread overview]
Message-ID: <87v9yhi3ux.fsf@gmail.com> (raw)
In-Reply-To: <B03E99E7-B088-456D-BBCA-E133CCC88F29@knosis.org> (Matthew Newton's message of "Fri, 10 May 2019 13:53:54 -0700")

Matthew Newton <matt@knosis.org> writes:

> Apologies for reviving a stale bug but it appears to not be resolved yet.

No apologies needed, on the contrary, thank you for looking at it.

> So there seem to be two bugs:
>
> 1. `desktop-save-mode` doesn’t serialize/deserialize keyboard macros
> properly (is it difficult to serialize a function object?)

> 2. Either :print-func and :insert-func should never be set to
> “Unprintable entity” or `register-val-describe` should handle the case
> where they are set to that value instead of a function.

The "unprintable entity" comes from desktop--v2s, looks like it doesn't
handle compiled function values, so that's why :print-func and
:insert-func get messed up like that.

> I’ve also seen “Unprintable entity” show up when a buffer position
> register points to a nonexistent buffer. Not sure how to reproduce
> that one.

I guess if you save a position in a buffer, then kill the buffer.







  reply	other threads:[~2019-05-11 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01  4:48 bug#24576: 25.1; desktop.el does not fully preserve registers with macros Dmitri Paduchikh
2019-05-10 20:53 ` Matthew Newton
2019-05-11 12:15   ` Noam Postavsky [this message]
2019-05-22 20:58     ` Matthew Newton
2019-05-23  3:43       ` Noam Postavsky
2019-05-29 17:41         ` Dmitri Paduchikh
2019-06-12 17:43         ` npostavs

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=87v9yhi3ux.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=24576@debbugs.gnu.org \
    --cc=dpaduchikh@gmail.com \
    --cc=matt@knosis.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 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.