all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: leim/quail and mule doble names of pkg
Date: Mon, 28 Nov 2011 12:53:14 -0500	[thread overview]
Message-ID: <jwvzkfgb0v0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874nxogw0p.fsf@gilgamesch.quim.ucm.es> (Uwe Brauer's message of "Mon, 28 Nov 2011 15:29:58 +0100")

> For example
> hebrew.el
> Is in
> leim/quail/hebrew.el for the input method
> But also in
> lisp/language/hebrew.el for the coding
> Is this wise?

I'm not sure if "wise" is the right question, but yes, there are some
problems in this area.  With the CEDET integration we have many more
such cases.  IIRC XEmacs has other cases with its packages's
"autoload" files.

The way those "same name files" are distinguished depends on the
particular case, and the potential problems are mostly avoided in
ad-hoc ways.

For CEDET, we basically consider the file's name to be
(file-relative-name buffer-file-name load-path), which does make those
file names unique again.  The same has been used for term/*.el files in
the past.  But this is not supported consistently (e.g. eval-after-load
does not understand this convention, IIRC).

For other files, we just try to treat those files specially (they don't
`provide' their name and aren't loaded via load-path), which comes with
its own set of problems and limitations.

I'd be happy to see someone tackle this issue and try to come up with
a set of solutions which we can then try to support consistently.


        Stefan



      parent reply	other threads:[~2011-11-28 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 14:29 leim/quail and mule doble names of pkg Uwe Brauer
2011-11-28 15:06 ` Andreas Schwab
2011-11-28 17:53 ` Stefan Monnier [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=jwvzkfgb0v0.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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.