unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: loaddefs.el filenames as seen by `update-file-autoloads'
Date: 13 May 2003 12:08:24 -0400	[thread overview]
Message-ID: <jkwuguhls7.fsf@glug.org> (raw)
In-Reply-To: "Stefan Monnier"'s message of "Tue, 13 May 2003 10:00:54 -0400"

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

   But that means that there is no way we can reliably use on Unix
   a loaddefs.el generated on VMS.  So I think the thing we should
   do is use something like `file-name-equal' rather than string=.

good point.  hmmm, the filename "datapath" is currently:

  directory-files
  system-specific munging   ;; proposed, e.g., downcase for vms
  loaddefs.el
  string=

we can make the design more reliable by explicitly specifying the
filename to be recorded in loaddefs.el (the proper comparison operation
becomes apparent w/ a well-specified data format).  that is, follow
system-specific munging w/ "filename specification override", such as
via a local variable, or by consulting the stylized top line:

   ;;; FILENAME.el --- do something

already the file needs to be scanned for local variables, so it seems to
me that approach is best.  this would mean lisp/term/AT386.el would need
to add something like:

   ;; Local variables:
   ;; autoload-recorded-file-name: "term/AT386.el"
   ;; End:

that doesn't seem too onerous.

thi

      reply	other threads:[~2003-05-13 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 22:30 loaddefs.el filenames as seen by `update-file-autoloads' Thien-Thi Nguyen
2003-05-12 23:05 ` Stefan Monnier
2003-05-13  0:41   ` Thien-Thi Nguyen
2003-05-13  1:14     ` Stefan Monnier
2003-05-13  2:05       ` Miles Bader
2003-05-13  4:06       ` Thien-Thi Nguyen
2003-05-13 14:00         ` Stefan Monnier
2003-05-13 16:08           ` Thien-Thi Nguyen [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

  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=jkwuguhls7.fsf@glug.org \
    --to=ttn@glug.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.
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).