From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: using guile scripts from hack/scripts
Date: 01 Apr 2002 16:03:51 +0100 [thread overview]
Message-ID: <m3ofh3wje0.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <E16rmfS-0005uz-00@giblet>
>>>>> "Thien-Thi" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
Thien-Thi> more divided mind healing here...
Thien-Thi> thi
Thien-Thi> ________________________
Thien-Thi> cd hack/scripts
Thien-Thi> cvs upd
Thien-Thi> cat Makefile # note var `gscripts'
Thien-Thi> make gscripts-symlink # use gscripts=DIR to customize
gscripts-symlinks
Thien-Thi> ./lint ./lint # test
I must remember to add lint to unstable sometime. (Unless someone
does it for me.)
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-01 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 21:15 using guile scripts from hack/scripts Thien-Thi Nguyen
2002-04-01 15:03 ` Neil Jerram [this message]
2002-04-03 10:52 ` Thien-Thi Nguyen
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=m3ofh3wje0.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-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.
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).