Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: assoc-string
Date: Mon, 25 Feb 2008 18:27:30 +0900	[thread overview]
Message-ID: <b4mtzjx75dp.fsf@jpl.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

Hi,

The new function `format-seconds' that time-date.el in the Gnus
CVS trunk provides now uses the `assoc-string' function, which
is not available in Emacs 21 and XEmacs.

  While compiling the end of the data in file gnus/lisp/time-date.el:
    ** The function `assoc-string' is not known to be defined.
  Wrote /tmp/.yamaoka/gnus/lisp/time-date.elc

It is not really a problem because Gnus currently does not use
`format-seconds', however someone might use it in the future
somewhere in Gnus.  What do you think we should do now?

1. Provide `time-date-assoc-string' in time-date.el in both the
   Emacs trunk and the Gnus trunk, and make `format-seconds' use
   it.  The function definition of `time-date-assoc-string' is
   attached below.

2. Similar to 1. but do it in only the Gnus trunk.

3. Replace `assoc-string' with `gnus-assoc-string' in time-date.el
   when compiling Gnus.  It does not need to modify time-date.el
   and I verified it can be done.  However it seems to be risky.
   (It is to make dgnushack.el provide the `assoc-string' macro
   which uses `gnus-assoc-string' provided in gnus-util.el .)

4. Do nothing, but don't use `format-seconds' in Gnus from now on.


[-- Attachment #2: time-date-assoc-string --]
[-- Type: application/emacs-lisp, Size: 2008 bytes --]

             reply	other threads:[~2008-02-25  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25  9:27 Katsumi Yamaoka [this message]
2008-02-25 15:51 ` assoc-string Stefan Monnier

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=b4mtzjx75dp.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).