unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: 22229@debbugs.gnu.org
Subject: bug#22229: Error when running script from directory with non-ASCII characters
Date: Sun, 07 Aug 2016 13:07:47 +0200	[thread overview]
Message-ID: <8760rcrg58.fsf@pobox.com> (raw)
In-Reply-To: <CAMfbzvDb+wRPVc5FWnstfUe_GFumHYXYO9KF--G=9SytREd8=g@mail.gmail.com> (Vicente Vera's message of "Wed, 23 Dec 2015 22:46:21 -0300")

On Thu 24 Dec 2015 02:46, Vicente Vera <vicentemvp@gmail.com> writes:

> Guile chokes when running a .scm script from a directory with
> non-ASCII characters.
>
> A simple test script:
>
> -------------------
> #!/usr/bin/guile -s
> !#
> ;; coding: utf-8
> (display "hey")
> (newline)
> -------------------
>
> $ cd ~/código/
> $ ./test.scm
> ;;; Stat of /home/me/c??digo/./test.scm failed:
> ;;; ERROR: In procedure stat: No such file or directory:

Weird :)

It's fixed in Guile 2.2 because Guile 2.2 installs the locale
automatically; see GUILE_INSTALL_LOCALE here:

  https://www.gnu.org/software/guile/manual/html_node/Environment-Variables.html

I don't know what to do about Guile 2.0 though.  And of course it's
possible even with Guile 2.2 to be in a directory whose name is not
valid in the current encoding.

Though I would like to fix it nicely, I suspect that given the proximity
of 2.2.0, we'll just punt on 2.0 :(  A bit frustrating though.

Andy





  parent reply	other threads:[~2016-08-07 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24  1:46 bug#22229: Error when running script from directory with non-ASCII characters Vicente Vera
2016-03-28  3:57 ` Alex Vong
2016-08-07 11:07 ` Andy Wingo [this message]
2016-08-11 17:53   ` Vicente Vera
2017-02-28 14:38     ` Andy Wingo

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=8760rcrg58.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=22229@debbugs.gnu.org \
    --cc=vicentemvp@gmail.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).