From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Scanning for coding declarations in all files (not just source)
Date: Tue, 22 Jan 2013 12:38:40 +0100 [thread overview]
Message-ID: <87zk01v45b.fsf@pobox.com> (raw)
In-Reply-To: <8738y2x04e.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 15 Jan 2013 10:32:17 +0100")
On Tue 15 Jan 2013 10:32, ludo@gnu.org (Ludovic Courtès) writes:
> Mike Gran <spk121@yahoo.com> skribis:
>
>> Opening a file that contains a coding declaration using an encoding other
>> than binary or the coding declared in the file seems like it would be
>> something of a corner case. So, IMHO it makes sense that opening a file
>> using its self-declared encoding should be the simple case, and that
>> opening a text file in a different (non-binary) text encoding should
>> be the more complicated case, in a API sense.
I am sympathetic to this, but also to Mike's "it's a tough problem;
whatever makes people happy" sentiment.
> As usual, backward-compatibility gives us an incentive not to change
> anything in 2.0. But perhaps we should change that in 2.2.
>
> Thoughts?
IMO we should update the docs and leave it as it is, though I don't care
much.
Mark?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-22 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 18:25 Scanning for coding declarations in all files (not just source) Mark H Weaver
2013-01-13 19:51 ` Mike Gran
2013-01-15 9:32 ` Ludovic Courtès
2013-01-22 11:38 ` Andy Wingo [this message]
2013-01-31 5:06 ` [PATCH] Do not scan for coding declarations in open-file Mark H Weaver
2013-01-31 10:00 ` Andy Wingo
2013-01-31 18:58 ` Mark H Weaver
2013-01-31 20:04 ` Andy Wingo
2013-01-31 22:00 ` Ludovic Courtès
2013-01-31 22:19 ` Noah Lavine
2013-01-31 21:51 ` Ludovic Courtès
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=87zk01v45b.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@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).