From: Michael Albinus <michael.albinus@gmx.de>
To: 27371@debbugs.gnu.org
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#27371: 26.0.50; Unexpected element (define-type . tramp-file-name) in load-history
Date: Mon, 17 Jul 2017 14:36:56 +0200 [thread overview]
Message-ID: <87o9sjme8n.fsf@detlef> (raw)
In-Reply-To: <87mv99n0ac.fsf@detlef> (Michael Albinus's message of "Thu, 15 Jun 2017 10:05:31 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> 1. emacs -Q -l tramp
> 2. M-x unload-feature <RET> tramp
>
> => Unexpected element (define-type . tramp-file-name) in load-history
The following patch fixes this for me:
--8<---------------cut here---------------start------------->8---
diff --git a/lisp/loadhist.el b/lisp/loadhist.el
index 28d0b18c81..34200ab40e 100644
--- a/lisp/loadhist.el
+++ b/lisp/loadhist.el
@@ -269,7 +269,7 @@ unload-feature
;; and says we should restore SYMBOL's autoload
;; when we undefine it.
(`t (setq restore-autoload (cdr x)))
- ((or `require `defface) nil)
+ ((or `require `defface `define-type) nil)
(_ (message "Unexpected element %s in load-history" x)))
;; Kill local values as much as possible.
(dolist (buf (buffer-list))
--8<---------------cut here---------------end--------------->8---
However, it just skips the entry. Wouldn't it be better to remove the
defstruct itself, and all inherited symbols? And where could I find
information how to destroy a defstruct?
Stefan?
Beswt regards, Michael.
next prev parent reply other threads:[~2017-07-17 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 8:05 bug#27371: 26.0.50; Unexpected element (define-type . tramp-file-name) in load-history Michael Albinus
2017-07-17 12:36 ` Michael Albinus [this message]
2017-07-17 19:43 ` Stefan Monnier
2017-07-18 7:09 ` Michael Albinus
2017-07-18 14:25 ` Stefan Monnier
2017-07-18 15:19 ` Michael Albinus
2017-07-18 15:56 ` Stefan Monnier
2017-07-24 15:01 ` Michael Albinus
2017-07-24 15:33 ` Stefan Monnier
2017-07-24 16:13 ` Michael Albinus
2017-07-24 16:31 ` Stefan Monnier
2017-07-24 17:39 ` Michael Albinus
2017-07-18 16:08 ` Michael Albinus
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=87o9sjme8n.fsf@detlef \
--to=michael.albinus@gmx.de \
--cc=27371@debbugs.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).