From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: propagating a coding setting across source files
Date: Mon, 16 Jan 2012 10:07:36 +0100 [thread overview]
Message-ID: <87y5t8hv6v.fsf@pobox.com> (raw)
In-Reply-To: <87hazwhbxw.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 15 Jan 2012 22:51:07 +0100")
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/
next prev parent reply other threads:[~2012-01-16 9:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 8:06 propagating a coding setting across source files Sven Hartrumpf
2011-12-02 10:41 ` rixed
2011-12-02 12:41 ` Paul Smith
2011-12-02 12:46 ` rixed
2011-12-02 12:55 ` Mike Gran
2011-12-02 13:41 ` Sven Hartrumpf
2011-12-02 14:23 ` Mike Gran
2011-12-05 17:25 ` Ludovic Courtès
2012-01-09 22:51 ` Andy Wingo
2012-01-10 8:51 ` Sven Hartrumpf
2012-01-11 18:00 ` Andy Wingo
2012-01-11 18:13 ` Mike Gran
2012-01-15 21:51 ` Ludovic Courtès
2012-01-16 9:07 ` Andy Wingo [this message]
2012-01-16 23:41 ` Ludovic Courtès
2013-01-07 21:28 ` 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=87y5t8hv6v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).