From: Tassilo Horn <tsdh@gnu.org>
To: Erik Colson <eco@ecocode.net>
Cc: ding@gnus.org
Subject: Re: error since upgraded to 24.3 and gnus from git
Date: Thu, 14 Mar 2013 08:05:58 +0100 [thread overview]
Message-ID: <87mwu6ea09.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m01ubjt200.fsf@ecocode.net> (Erik Colson's message of "Wed, 13 Mar 2013 22:37:35 +0100")
Erik Colson <eco@ecocode.net> writes:
Hi Erik,
>> So gnus-util has actually been successfully loaded before the error
>> is triggered, but it must be an old version of gnus-util.el which
>> hasn't gnus-get-text-property-excluding-characters-with-faces, or
>> perhaps gnus-util.elc is stale. At least, I can't think of any other
>> reason...
>
> yep, that was it :)
> had another gnus-util.elc which got loaded !
Good that it's solved now.
For the future, there's this nice command that helps to find those
problems.
,----[ C-h f list-load-path-shadows RET ]
| list-load-path-shadows is an interactive autoloaded Lisp function in
| `shadow.el'.
|
| (list-load-path-shadows &optional STRINGP)
|
| Display a list of Emacs Lisp files that shadow other files.
|
| If STRINGP is non-nil, returns any shadows as a string.
| Otherwise, if interactive shows any shadows in a `*Shadows*' buffer;
| else prints messages listing any shadows.
|
| This function lists potential load path problems. Directories in
| the `load-path' variable are searched, in order, for Emacs Lisp
| files. When a previously encountered file name is found again, a
| message is displayed indicating that the later file is "hidden" by
| the earlier.
|
| For example, suppose `load-path' is set to
|
| ("/usr/gnu/emacs/site-lisp" "/usr/gnu/emacs/share/emacs/19.30/lisp")
|
| and that each of these directories contains a file called XXX.el. Then
| XXX.el in the site-lisp directory is referred to by all of:
| (require 'XXX), (autoload .... "XXX"), (load-library "XXX") etc.
|
| The first XXX.el file prevents Emacs from seeing the second (unless
| the second is loaded explicitly via `load-file').
|
| When not intended, such shadowings can be the source of subtle
| problems. For example, the above situation may have arisen because the
| XXX package was not distributed with versions of Emacs prior to
| 19.30. An Emacs maintainer downloaded XXX from elsewhere and installed
| it. Later, XXX was updated and included in the Emacs distribution.
| Unless the Emacs maintainer checks for this, the new version of XXX
| will be hidden behind the old (which may no longer work with the new
| Emacs version).
|
| This function performs these checks and flags all possible
| shadowings. Because a .el file may exist without a corresponding .elc
| (or vice-versa), these suffixes are essentially ignored. A file
| XXX.elc in an early directory (that does not contain XXX.el) is
| considered to shadow a later file XXX.el, and vice-versa.
|
| Shadowings are located by calling the (non-interactive) companion
| function, `load-path-shadows-find'.
`----
Bye,
Tassilo
next prev parent reply other threads:[~2013-03-14 7:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:08 Erik Colson
2013-03-13 11:29 ` Erik Colson
2013-03-13 12:29 ` Tassilo Horn
2013-03-13 13:16 ` Erik Colson
2013-03-13 16:35 ` Tassilo Horn
2013-03-13 19:17 ` Erik Colson
2017-03-25 0:23 ` dovecot X-MAILBOX and X-REAL-UID support in nnimap ? Erik Colson
2013-03-13 16:30 ` error since upgraded to 24.3 and gnus from git Wolfgang Jenkner
2013-03-13 19:19 ` Erik Colson
2013-03-13 19:41 ` Wolfgang Jenkner
2013-03-13 21:37 ` Erik Colson
2013-03-14 7:05 ` Tassilo Horn [this message]
2013-03-14 7:43 ` Erik Colson
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=87mwu6ea09.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=eco@ecocode.net \
/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.
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 NNTP newsgroup(s).