|
From: | Andy Wingo |
Subject: | Re: [Guile-commits] GNU Guile branch, string_abstraction2, updated. 823e444052817ee120d87a3575acb4f767f17475 |
Date: | Thu, 28 May 2009 20:21:22 +0200 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (gnu/linux) |
Hi, On Thu 28 May 2009 16:37, address@hidden (Ludovic Courtès) writes: > Andy Wingo <address@hidden> writes: > >> This is complicated in Guile by #!. A reasonable thing would be to have >> the reader have a bit on whether it actually saw an expression yet or >> not. If not, "^;+ [^\n]*coding: ..." would set the file's encoding. > > I think it would make sense to follow Emacs' specification of file-local > variables as closely as possible (info "(emacs) Specifying File > Variables"), as well as its naming scheme for encodings as shown by > `M-x list-coding-systems'. Good points. Although, I wonder how emacs does the right thing regarding coding: if the variable list is at the end of a file. But certainly recognizing it in the first two lines of the file would be robust and follow emacs. Andy -- http://wingolog.org/
[Prev in Thread] | Current Thread | [Next in Thread] |