unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.homelinux.net>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>,
	guile-devel@gnu.org
Subject: Re: Trouble using (current-filename)
Date: Thu, 15 Mar 2012 08:34:59 +0000	[thread overview]
Message-ID: <87ehsu45zg.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <CA+U71=P-WwGffokEMg_T1d1Vi+4qdfb1a_L27A+B9yTOCjrtzg@mail.gmail.com> (Noah Lavine's message of "Wed, 14 Mar 2012 22:00:49 -0400")

Noah Lavine <noah.b.lavine@gmail.com> writes:

> Hello,
>
> What ever happened to this issue? Is it considered resolved now, or is
> there more to do?

For my use case it's resolved, in the sense that I really needed a
runtime directory that may not be the same as the source compilation
location; and hence 'current-filename' wasn't the right solution after
all.

For other use cases, I guess it depends what those are.

     Neil



  reply	other threads:[~2012-03-15  8:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 18:57 Trouble using (current-filename) Mark H Weaver
2012-02-15 22:23 ` Andy Wingo
2012-02-16 21:34   ` Ludovic Courtès
2012-02-16 22:25     ` Andy Wingo
2012-02-17 22:49       ` Ludovic Courtès
2012-02-18 20:58         ` Andy Wingo
2012-02-19 14:10           ` Ludovic Courtès
2012-02-19 20:44             ` Andy Wingo
2012-02-19 21:02               ` Ludovic Courtès
2012-02-19 21:23                 ` Andy Wingo
2012-02-19 21:30                   ` Noah Lavine
2012-02-20 13:12                     ` Ludovic Courtès
2012-02-21 20:48             ` Neil Jerram
2012-02-21 20:52               ` Ludovic Courtès
2012-02-21 21:00                 ` Neil Jerram
2012-03-15  2:00                   ` Noah Lavine
2012-03-15  8:34                     ` Neil Jerram [this message]
2012-03-15 16:41                       ` Ludovic Courtès
2012-03-15 21:31                         ` Andy Wingo
2012-03-21 21:11                           ` Ludovic Courtès
2012-02-21 17:38   ` Mark H Weaver

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=87ehsu45zg.fsf@neil-laptop.ossau.uklinux.net \
    --to=neil@ossau.homelinux.net \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    --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).