unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Two questions about thumbs.el
Date: 26 Apr 2004 18:39:21 +0200	[thread overview]
Message-ID: <m3y8oin16u.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040426104147.5042.JMBARRANQUERO@wke.es>

Juanma Barranquero <jmbarranquero@wke.es> writes:

> Third question (yeah, I lied on the subject): There are at least eight
> versions of the time-less-p code:
> 
> calendar/time-date: time-less-p
> calendar/timeclock: timeclock-time-less-p
> pcomplete:          pcomplete-time-less-p
> speedbar:           speedbar-check-obj-this-line (fragment)
> thumbs:             time-less-p
> autoload:           autoload-before-p
> eshell/esh-util:    eshell-time-less-p
> net/tramp-smb:      tramp-smb-time-less-p (fragment)
> 
> speedbar, eshell and tramp have a life outside of Emacs, so they need
> their own definitions for compatibility, but the others could be
> "reunified" by using calendar/time-date's version (time-date.elc is
> quite small, about 4K).

This functionality is obviously generally useful.
Maybe time-less-p should be defined in subr.el?

> Note: I'm not sure about autoload, because without testing it I don't
> know if there'll be a problem for autoload to use an autoloaded function.

I don't this that's a problem, but in any case defining it in subr.el
would fix that nevertheless.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-04-26 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 13:31 Two questions about thumbs.el Juanma Barranquero
2004-04-26 16:39 ` Kim F. Storm [this message]
2004-04-26 16:58   ` Juanma Barranquero
2004-04-27 16:29     ` Richard Stallman
2004-04-27 18:09       ` Juanma Barranquero
2004-05-24 14:08 ` Richard Stallman
2004-05-24 14:32   ` Juanma Barranquero

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3y8oin16u.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).