all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: 23927@debbugs.gnu.org
Subject: bug#23927: 25.0.94; Errors when updating using package.el
Date: Wed, 13 Jul 2016 22:49:57 +0200	[thread overview]
Message-ID: <5786A975.2050703@gmail.com> (raw)
In-Reply-To: <6ea8hlmpef.fsf@fencepost.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 879 bytes --]

On 2016-07-13 19:14, Glenn Morris wrote:
> Live System User wrote:
>>> The OP has some broken info.el early in their load-path, presumably one
>>> that isn't part of Emacs.
>>
>>   There is a MELPA package I have installed called "realgud" that
>>   has the file:
>>
>>       ~/.emacs.d/elpa/realgud/common/buffer/info.el(.elc)
>>
>>   Perhaps package.el should deal with this type of issue, otherwise
>>   package authors will have to avoid naming their .el files names
>>   that are the same as (some) Emacs library names?
> 
> Emacs uses a PATH-type lookup in which first match wins. Twas ever thus.
> ("Private" namespaces are possible using the subdirectory approach used
> by eg cedet in Emacs.)

Sorry, I didn't follow this very closely. I'm one of the Realgud maintainers; is there anything we can do on our side to make things smoother?

Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-13 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  4:17 bug#23927: 25.0.94; Errors when updating using package.el Live System User
2016-07-09  7:19 ` Eli Zaretskii
2016-07-10  0:51   ` Glenn Morris
2016-07-12 21:52     ` Live System User
2016-07-13 17:14       ` Glenn Morris
2016-07-13 20:49         ` Clément Pit--Claudel [this message]
2016-07-13 20:57           ` Glenn Morris
2016-07-13 21:53             ` Clément Pit--Claudel
2016-07-12 21:21   ` Live System User

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=5786A975.2050703@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=23927@debbugs.gnu.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.