From: Clinton Ebadi <clinton@unknownlamer.org>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org, Bake Timmons <b3timmons@speedymail.org>
Subject: Re: Broken link ./trunk/doc/ref/scsh.texi:@url(http://arglist.com/guile/}
Date: Tue, 17 Aug 2010 12:21:00 -0400 [thread overview]
Message-ID: <87iq391a8j.fsf@rvannith.home.unknownlamer.org> (raw)
In-Reply-To: <m3tymtw8jp.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 17 Aug 2010 08:41:46 -0700")
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Andy Wingo <wingo@pobox.com> writes:
> Hi Bake,
>
> On Fri 06 Aug 2010 06:04, Bake Timmons <b3timmons@speedymail.org> writes:
>
>> http://arglist.com/guile/ is a broken link in the scsh.texi file in
>> trunk.
>>
>> The site explains elsewhere at http://arglist.com/www :
>>
>> I've removed some material related to the Guile programming language,
>> since it's probably obsolete.
>>
>> Perhaps the link to the old guile CVS scsh-guile module should be
>> mentioned instead?
>
> Thanks for the report. Clinton (copied on this mail) once mentioned that
> he had a partial port of that old code to work with current Guile;
> Clinton, is that right? Is there somewhere else to point to, besides the
> old CVS module?
There is Guile Facade which is (more or less) scsh at:
http://unknownlamer.org/darcsweb/browse?r=guile-facade;a=summary
The interface has been changed in some ways (anything provided by Guile
itself it no longer provided), it is undocumented, and I have yet to
actually finish it (another weekend of hacking with my local changes is
all it needs in theory).
The CVS version no longer works with Guile 1.9.x unfortunately (relying
on internal behavior of macroexpanders to implement the explicit
renaming macro macro system). But... once I get my new laptop set up for
hacking (aaaalmost there) and finish up a few rather minor work tasks it
looks like I'll have time for this again (and will have a day or two
without net access to force me from distraction). I'll make an
announcement to guile-user when that happens.
FWIW the tasks I have listed remaining are:
#B _ Port scsh fname {{Tasks:2363}} ([[2010.08.16]])
#C _ Port fork/pipe et al {{Tasks:2359}} ([[2010.08.16]])
#C _ Port port->FOO {{Tasks:2360}} ([[2010.08.16]])
#C _ Port run/FOO {{Tasks:2361}} ([[2010.08.16]])
#C _ Port glob {{Tasks:2362}} ([[2010.08.16]])
I was last working on the fname module: porting it required bringing in
the entire file system code. I brought in most of the code and did a
quick make-it-compile run through, but still have to do the part wherein
I ensure it actually runs.
> For now, changing the link to point to the old CVS module.
>
> Thanks,
>
> Andy
--
Jessie: i thought your beard took the oxygen from the air and made it
breathable for you
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
prev parent reply other threads:[~2010-08-17 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 13:04 Broken link ./trunk/doc/ref/scsh.texi:@url(http://arglist.com/guile/} Bake Timmons
2010-08-17 15:41 ` Andy Wingo
2010-08-17 16:21 ` Clinton Ebadi [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iq391a8j.fsf@rvannith.home.unknownlamer.org \
--to=clinton@unknownlamer.org \
--cc=b3timmons@speedymail.org \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.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.
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).