From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] configure check for crypt()
Date: Sun, 22 Feb 2004 07:41:35 +1000 [thread overview]
Message-ID: <87oerskt4g.fsf@zip.com.au> (raw)
In-Reply-To: <87ad3czy6q.fsf@ID-28718.user.uni-berlin.de> (Andreas Voegele's message of "Sat, 21 Feb 2004 08:30:53 +0100")
Andreas Voegele <voegelas@gmx.net> writes:
>
> (passwd:dir (getpwuid (cuserid)))
Incidentally, I see the glibc manual and the gnu/linux man page advise
against cuserid, suggesting either LOGNAME or geteuid. Looks like
glib g_get_home_dir uses the latter. Maybe a little define (just for
internal use) for guile to collect up this nonsense in one place.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-02-21 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 19:48 [PATCH] configure check for crypt() Andreas Voegele
2004-02-19 10:27 ` Andreas Voegele
2004-02-20 23:17 ` Kevin Ryde
2004-02-21 0:52 ` Rob Browning
2004-02-21 7:30 ` Andreas Voegele
2004-02-21 21:00 ` Kevin Ryde
2004-02-21 21:41 ` Kevin Ryde [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=87oerskt4g.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).