From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Glenn Morris <rgm@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Problems with `require' in recent changes
Date: Wed, 12 Dec 2007 14:39:56 +0900 [thread overview]
Message-ID: <b4m8x401nf7.fsf@jpl.org> (raw)
In-Reply-To: <t6zlwga9j2.fsf@fencepost.gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]
>>>>> Glenn Morris wrote:
> Katsumi Yamaoka wrote:
>> I don't know what (require 'password) is for, too.
> Because I didn't know if password will get renamed in Gnus too, or if
> Gnus needs to support systems where password-cache is still called
> password.
Now only password-cache.el exists in the Gnus trunk. However,
password.el is still in ecrypto that is an official XEmacs Lisp
package. So, it will override password-cache.el if some program
requires the feature `password'. I'm not sure what it brings,
but it seems that password-cache.el had better provide also the
feature `password'. Though it might cause a trouble in programs
that use password functions, I guess it is easy to be solved.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-12-12 5:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 12:04 Dave Goldberg
2007-12-12 3:12 ` Katsumi Yamaoka
2007-12-12 3:15 ` Glenn Morris
2007-12-12 5:39 ` Katsumi Yamaoka [this message]
2007-12-12 15:09 ` Stefan Monnier
2007-12-12 20:45 ` Reiner Steib
2007-12-14 0:07 ` Katsumi Yamaoka
2007-12-16 18:32 ` Reiner Steib
2007-12-16 20:22 ` Miles Bader
2007-12-16 20:51 ` Reiner Steib
2007-12-17 2:25 ` Glenn Morris
2007-12-17 18:44 ` Glenn Morris
2007-12-18 0:29 ` Katsumi Yamaoka
2007-12-28 19:34 ` Reiner Steib
2007-12-17 21:45 ` Dave Goldberg
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=b4m8x401nf7.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.
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).