unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Add ".guile.sls" and ".sls" to the default %load-extensions
Date: Sun, 4 Nov 2012 11:10:22 -0500	[thread overview]
Message-ID: <CA+U71=PmTNvcheYJxHk6GKXJKk9vHJo2gkb-7pRJsxOwSGXSJw@mail.gmail.com> (raw)
In-Reply-To: <87fw4qgi1i.fsf@tines.lan>

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

If it's semi-standard, we should probably support it too.

However, a Google search reveals the following other uses of .sls:
  - A list of images for a slideshow ("sls" stands for "slideshow script")
  - The backup files for some program callled Litespeed
  - ScriptLab Scripts (seems to be an image generation program)
  - Configuration files for the Salt infrastructure management tool

So we probably shouldn't use it ourselves. (Plus, I personally think it's
uglier than .scm, but that's not a strong argument.)

Noah



On Sat, Nov 3, 2012 at 11:31 PM, Mark H Weaver <mhw@netris.org> wrote:

> Hello all,
>
> Any objections to adding ".guile.sls" and ".sls" to Guile's default
> %load-extensions?  Ian Price tells me that this naming convention is
> commonly followed for R6RS libraries and implementations, e.g. Racket,
> Mosh, Ikarus, and Ypsilon.  It would facilitate easy use of R6RS
> libraries without having to rename the files.  I'm inclined to go along.
>
> What do you think?
>
>     Mark
>
>
>

[-- Attachment #2: Type: text/html, Size: 1579 bytes --]

  reply	other threads:[~2012-11-04 16:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04  3:31 [PATCH] Add ".guile.sls" and ".sls" to the default %load-extensions Mark H Weaver
2012-11-04 16:10 ` Noah Lavine [this message]
2012-11-04 20:34 ` Ludovic Courtès
2012-11-04 22:27   ` Andreas Rottmann
2012-11-04 23:32     ` Ludovic Courtès
2012-11-05  0:17       ` Andreas Rottmann
2012-11-05 15:16         ` Ludovic Courtès
2012-11-05 20:48           ` Mark H Weaver
2012-11-05 21:15             ` Ludovic Courtès
2012-11-06  2:19               ` nalaginrut
2012-11-06  2:36                 ` Ian Price
2012-11-06  2:56               ` Ian Price
2012-11-06  5:18               ` Mark H Weaver
2012-11-07 20:28                 ` Ludovic Courtès
2012-11-08  2:37                   ` Alex Shinn
2012-11-08 22:41                   ` Andreas Rottmann

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/guile/

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

  git send-email \
    --in-reply-to='CA+U71=PmTNvcheYJxHk6GKXJKk9vHJo2gkb-7pRJsxOwSGXSJw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).