From: Andy Wingo <wingo@pobox.com>
To: guile-user@gnu.org, bug-guile <bug-guile@gnu.org>
Subject: Re: propagating a coding setting across source files
Date: Mon, 07 Jan 2013 22:28:45 +0100 [thread overview]
Message-ID: <87ip78ptrm.fsf@pobox.com> (raw)
In-Reply-To: <874nvv1ahb.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 17 Jan 2012 00:41:36 +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@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/
parent reply other threads:[~2013-01-07 21:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <874nvv1ahb.fsf@gnu.org>]
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=87ip78ptrm.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=guile-user@gnu.org \
/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).