propagating a coding setting across source files

propagating a coding setting across source files

[Sven Hartrumpf]

Hi all.

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.

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 included by the master file using "load"?

Ciao
Sven

Re: propagating a coding setting across source files

[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 the trouble doing it by
hand, but anyway just in case you need a command to do this
operation here it is:

$ find where-your-files-are -type f -name '*.scm' |
	while read f; do echo '; coding: iso-8859-1' > $f ; done

Although it may be shorter in scheme...

Re: propagating a coding setting across source files

[Paul Smith]

On Fri, 2011-12-02 at 11:41 +0100, rixed@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.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@gnu.org>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.mad-scientist.net
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

Re: propagating a coding setting across source files

[rixed]

-[ Fri, Dec 02, 2011 at 07:41:40AM -0500, Paul Smith ]----
> On Fri, 2011-12-02 at 11:41 +0100, rixed@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.

Sure!
That's ">>" not ">" : echo '; coding...' >> $f
                                         ^^
                                         !!

I _really_ hope every one is using a versionning system these days :)

Re: propagating a coding setting across source files

[Mike Gran]

> From: Sven Hartrumpf <hartrumpf@gmx.net>
>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 included by the master file using "load"?

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.
 
-Mike

Re: propagating a coding setting across source files

[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)> (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: unknown character name 
ERROR: In procedure primitive-load:
ERROR: In procedure scm_lreadr: /home/s/aa.scm:1:13: unknown character name 

Sven

Re: propagating a coding setting across source files

[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: unknown character name 
>ERROR: In procedure primitive-load:
>ERROR: In procedure scm_lreadr: /home/s/aa.scm:1:13: unknown character name 


I guess you're right.  Looks like, at some point, the default for files with
no 'coding:' line got hard set to UTF-8 in 'scm_primitive_load' and 'compile-file'
and friends.


At first, I thought you could do something with %load-hook, or by setting
the %default-port-encoding, but that isn't going to work either.

No workaround is obvious to me.  Hrm.  Unfortunate.

-Mike

Re: propagating a coding setting across source files

[Ludovic Courtès]

Hi!

Mike Gran <spk121@yahoo.com> 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

[Andy Wingo]

Hi Sven,

On Fri 02 Dec 2011 09:06, Sven Hartrumpf <hartrumpf@gmx.net> 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 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 included by the master file using "load"?

You can (fluid-set! %default-port-encoding "iso-8859-1").

Let us know if this doesn't work.

Andy
-- 
http://wingolog.org/

Re: propagating a coding setting across source files

[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"?
> 
> You can (fluid-set! %default-port-encoding "iso-8859-1").
> 
> Let us know if this doesn't work.

If I add this to my master file it does not help.
Where should I put your command?

Sven

Re: propagating a coding setting across source files

[Andy Wingo]

On Tue 10 Jan 2012 09:51, Sven Hartrumpf <hartrumpf@gmx.net> 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
>>> which are currently included by the master file using "load"?
>> 
>> You can (fluid-set! %default-port-encoding "iso-8859-1").
>> 
>> Let us know if this doesn't work.
>
> If I add this to my master file it does not help.
> Where should I put your command?

It could be that there is an issue regarding compile-time versus
run-time;

  http://www.gnu.org/software/guile/manual/html_node/Eval-When.html

If you put this at the top of your file, before any use-modules or
anything like that, does it work?

  (eval-when (eval load compile)
    (fluid-set!  %default-port-encoding "iso-8859-1"))

You might need to run with --auto-compile=fresh to invalidate the
caches.

Regards,

Andy
-- 
http://wingolog.org/

Re: propagating a coding setting across source files

[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! %default-port-encoding "iso-8859-1").
>>> 
>>>  Let us know if this doesn't work.
>> 
>>  If I add this to my master file it does not help.
>>  Where should I put your command?
> 
> It could be that there is an issue regarding compile-time versus
> run-time;
> 
>   http://www.gnu.org/software/guile/manual/html_node/Eval-When.html
> 
> If you put this at the top of your file, before any use-modules or
> anything like that, does it work?
> 
>   (eval-when (eval load compile)
>     (fluid-set!  %default-port-encoding "iso-8859-1"))
> 
> You might need to run with --auto-compile=fresh to invalidate the
> caches.
 
Hey Andy, 
 
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.
 
But there is a lot between "load" and "primitive-load" that I didn't
try to trace through.  I'm not sure under what conditions "load" calls
"primitive load".
 
Thanks,
 
Mike

Re: propagating a coding setting across source files

[Ludovic Courtès]

Hi,

Mike Gran <spk121@yahoo.com> 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 Sven is asking for, propagating source file encoding
programmatically, is not possible AFAIK.  Sven: you really need to add
the “coding:” cookie to each and every file.

Thanks,
Ludo’.

Re: propagating a coding setting across source files

[Andy Wingo]

On Sun 15 Jan 2012 22:51, ludo@gnu.org (Ludovic Courtès) writes:

> Mike Gran <spk121@yahoo.com> 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 Sven is asking for, propagating source file encoding
> programmatically, is not possible AFAIK.  Sven: you really need to add
> the “coding:” cookie to each and every file.

Is possible to provide such an interface?

I agree that coding: is the right thing, but there's a lot of legacy
code out there.  If it's possible to support without much effort, we
probably should do so.

Andy
-- 
http://wingolog.org/

Re: propagating a coding setting across source files

[Ludovic Courtès]

Hi!

Andy Wingo <wingo@pobox.com> skribis:

> On Sun 15 Jan 2012 22:51, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mike Gran <spk121@yahoo.com> 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 Sven is asking for, propagating source file encoding
>> programmatically, is not possible AFAIK.  Sven: you really need to add
>> the “coding:” cookie to each and every file.
>
> Is possible to provide such an interface?

Maybe a ‘guild compile’ option?

Ludo’.

Re: propagating a coding setting across source files

[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, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> skribis:
>
>> On Sun 15 Jan 2012 22:51, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Mike Gran <spk121@yahoo.com> 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 Sven is asking for, propagating source file encoding
>>> programmatically, is not possible AFAIK.  Sven: you really need to add
>>> the “coding:” cookie to each and every file.
>>
>> Is possible to provide such an interface?
>
> Maybe a ‘guild compile’ option?
>
> Ludo’.

-- 
http://wingolog.org/