From: Juanma Barranquero <lekktu@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: 4440@emacsbugs.donarmstrong.com
Subject: bug#4440: 23.1.50; Add .dx32fsl to completion-ignored-extensions
Date: Fri, 25 Sep 2009 13:42:47 +0200 [thread overview]
Message-ID: <f7ccd24b0909250442y6b124971qff748d975bdb55d3@mail.gmail.com> (raw)
In-Reply-To: <m0my4we0mf.fsf@cam.ac.uk>
On Tue, Sep 15, 2009 at 16:36, Leo <sdl.web@gmail.com> wrote:
> I am surprised to see that .dx64fsl is on completion-ignored-extensions
> while .dx32fsl is not.
>
> '.dx32fsl' is produced by 32 bit clozure-cl¹. So I'd propose to add it
> to the list.
Apparently, OpenMCL / Clozure uses different extensions for fasl
according to target architecture:
http://ccl.clozure.com/ccl-documentation.html#building-definitions
The attached patch adds them all, though I think they're a bit too
much. Any way to know which of these are commonly used?
Juanma
Index: lisp/bindings.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/bindings.el,v
retrieving revision 1.225
diff -u -2 -r1.225 bindings.el
--- lisp/bindings.el 14 Sep 2009 23:28:43 -0000 1.225
+++ lisp/bindings.el 22 Sep 2009 13:43:44 -0000
@@ -602,7 +602,10 @@
;; CMUCL
".x86f" ".sparcf"
- ;; Other CL implementations (Allegro, LispWorks, OpenMCL)
- ".fasl" ".ufsl" ".fsl" ".dxl" ".pfsl" ".dfsl"
- ".p64fsl" ".d64fsl" ".dx64fsl"
+ ;; OpenMCL / Clozure CL
+ ".dfsl" ".pfsl" ".d64fsl" ".p64fsl" ".lx64fsl" ".lx32fsl"
+ ".dx64fsl" ".dx32fsl" ".fx64fsl" ".fx32fsl" ".sx64fsl"
+ ".sx32fsl" ".wx64fsl" ".wx32fsl"
+ ;; Other CL implementations (Allegro, LispWorks)
+ ".fasl" ".ufsl" ".fsl" ".dxl"
;; Libtool
".lo" ".la"
next prev parent reply other threads:[~2009-09-25 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 14:36 bug#4440: 23.1.50; Add .dx32fsl to completion-ignored-extensions Leo
2009-09-15 15:14 ` Juanma Barranquero
2009-09-15 18:51 ` Leo
2009-09-25 11:42 ` Juanma Barranquero [this message]
2009-09-30 10:00 ` Leo
2011-07-13 13:39 ` Lars Magne Ingebrigtsen
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=f7ccd24b0909250442y6b124971qff748d975bdb55d3@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=4440@emacsbugs.donarmstrong.com \
--cc=sdl.web@gmail.com \
/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).