GNU bug report logs - #13382
propagating a coding setting across source files

Previous Next

Package: guile;

Reported by: Andy Wingo <wingo <at> pobox.com>

Date: Mon, 7 Jan 2013 21:30:02 UTC

Severity: wishlist

Full log


Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: guile-user <at> gnu.org, bug-guile <bug-guile <at> gnu.org>
Subject: Re: propagating a coding setting across source files
Date: Mon, 07 Jan 2013 22:28:45 +0100
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 <at> gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo <at> pobox.com> skribis:
>
>> On Sun 15 Jan 2012 22:51, ludo <at> gnu.org (Ludovic Courtès) writes:
>>
>>> Mike Gran <spk121 <at> 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/




This bug report was last modified 12 years and 62 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.