Re: propagating a coding setting across source files

2013-01-07 Thread Andy Wingo
Hi, Forwarding this one to bug-guile to make a bug report. I guess we need a (default-source-file-encoding) parameter. Andy On Tue 17 Jan 2012 00:41, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo skribis: > >> On Sun 15 Jan 2012 22:51, l...@gnu.org (Ludovic Courtès) writes: >> >>> Mike

Re: propagating a coding setting across source files

2012-01-16 Thread Ludovic Courtès
Hi! Andy Wingo skribis: > On Sun 15 Jan 2012 22:51, l...@gnu.org (Ludovic Courtès) writes: > >> Mike Gran skribis: >> >>> I tried to dig through the logic of this the other day, and I'm not >>> sure that your suggestion can work.  If "load" ends up calling >>> "primitive-load", then any file wi

Re: propagating a coding setting across source files

2012-01-16 Thread Andy Wingo
On Sun 15 Jan 2012 22:51, l...@gnu.org (Ludovic Courtès) writes: > Mike Gran skribis: > >> I tried to dig through the logic of this the other day, and I'm not >> sure that your suggestion can work.  If "load" ends up calling >> "primitive-load", then any file without a "coding:" line is UTF-8. >>

Re: propagating a coding setting across source files

2012-01-16 Thread Ludovic Courtès
Hi, Mike Gran skribis: > I tried to dig through the logic of this the other day, and I'm not > sure that your suggestion can work.  If "load" ends up calling > "primitive-load", then any file without a "coding:" line is UTF-8. > %default-port-encoding doesn't enter in to it. Right. So what Sve

Re: propagating a coding setting across source files

2012-01-11 Thread Sven Hartrumpf
Hi Andy. Mon, 09 Jan 2012 23:51:42 +0100, wingo wrote: >> I added to the master file the following comment: >> >> ; coding: iso-8859-1 >> >> which works as documented. >> How can I avoid to add this comment line to all the other files >> which are currently included by the master file using "load"

Re: propagating a coding setting across source files

2012-01-11 Thread Mike Gran
I added to the master file the following comment: ; coding: iso-8859-1 which works as documented. How can I avoid to add this comment line to all the other files which are currently included by the master file using > "load"? >>> >>> You can (fluid-set!

Re: propagating a coding setting across source files

2012-01-11 Thread Andy Wingo
On Tue 10 Jan 2012 09:51, Sven Hartrumpf writes: > Hi Andy. > > Mon, 09 Jan 2012 23:51:42 +0100, wingo wrote: >>> I added to the master file the following comment: >>> >>> ; coding: iso-8859-1 >>> >>> which works as documented. >>> How can I avoid to add this comment line to all the other files >

Re: propagating a coding setting across source files

2012-01-09 Thread Andy Wingo
Hi Sven, On Fri 02 Dec 2011 09:06, Sven Hartrumpf writes: > After a long period of working with other Schemes, > I am returning to guile for some tests to see what > Guile has achieved in recent years. Cool! Let us know if you find something that smells bad. > My test program is made up of ar

Re: propagating a coding setting across source files

2011-12-05 Thread Ludovic Courtès
Hi! Mike Gran skribis: > I'm pretty sure that, for 2.0.x at least, if you don't > specify an encoding, it presumes iso-8859-1 as the default. No, UTF-8 is the default (info "(guile) Compilation"). Thanks, Ludo’.

Re: propagating a coding setting across source files

2011-12-02 Thread Mike Gran
>Not when loading a file with Latin-1 characters: > >> cat aa.scm >(define c #\ä) > >> guile >GNU Guile 2.0.3 >... >scheme@(guile-user)> (load "aa.scm") >;;; compiling /home/s/aa.scm >;;; WARNING: compilation of /home/s/aa.scm failed: >;;; ERROR: In procedure scm_lreadr: /home/s/aa.scm:1:13: unkno

Re: propagating a coding setting across source files

2011-12-02 Thread Sven Hartrumpf
Fri, 2 Dec 2011 04:55:39 -0800 (PST), spk121 wrote: > I'm pretty sure that, for 2.0.x at least, if you don't > specify an encoding, it presumes iso-8859-1 as the default. Not when loading a file with Latin-1 characters: > cat aa.scm (define c #\ä) > guile GNU Guile 2.0.3 ... scheme@(guile-user)>

Re: propagating a coding setting across source files

2011-12-02 Thread Mike Gran
> From: Sven Hartrumpf >My test program is made up of around 100 scheme files, all >encoded in latin-1. >I added to the master file the following comment: > >; coding: iso-8859-1 > >which works as documented. >How can I avoid to add this comment line to all the other files >which are currently inc

Re: propagating a coding setting across source files

2011-12-02 Thread rixed
-[ Fri, Dec 02, 2011 at 07:41:40AM -0500, Paul Smith ] > On Fri, 2011-12-02 at 11:41 +0100, ri...@happyleptic.org wrote: > > $ find where-your-files-are -type f -name '*.scm' | > > while read f; do echo '; coding: iso-8859-1' > $f ; done > > Boy I _really_ don't think you want to do th

Re: propagating a coding setting across source files

2011-12-02 Thread Paul Smith
On Fri, 2011-12-02 at 11:41 +0100, ri...@happyleptic.org wrote: > $ find where-your-files-are -type f -name '*.scm' | > while read f; do echo '; coding: iso-8859-1' > $f ; done Boy I _really_ don't think you want to do that. --

Re: propagating a coding setting across source files

2011-12-02 Thread rixed
-[ Fri, Dec 02, 2011 at 09:06:07AM +0100, Sven Hartrumpf ] > How can I avoid to add this comment line to all the other files > which are currently included by the master file using "load"? You very possibly have better reasons to refuse to add this line to your files than the mere trouble of t