From: Paul R <paul.r.ml@gmail.com>
To: Nobuyoshi Nakada <nobu@ruby-lang.org>
Cc: emacs-devel@gnu.org
Subject: Re: ruby-mode : ruby-mode-set-encoding
Date: Wed, 04 Mar 2009 09:25:24 +0100 [thread overview]
Message-ID: <87wsb5heyz.fsf@gmail.com> (raw)
In-Reply-To: <49adca00.14098e0a.2c79.ffff83d1@mx.google.com> (Nobuyoshi Nakada's message of "Wed, 04 Mar 2009 09:23:23 +0900")
Hello Nobuyoshi,
Nobuyoshi> It's mandatory for Ruby 1.9 or later. Ruby 1.9 needs that
Nobuyoshi> "magic comment" to know in what encoding a script is written.
Nobuyoshi> Otherwise, the script is assumed as written with ASCII 7bit
Nobuyoshi> characters only, and non-ASCII character causes an exception
Nobuyoshi> if exists.
Fine, I did not relate it to 1.9 (that was recently released) because
I have seen this behaviour for monthes. I think the reason is that I was
using the svn version of ruby-mode.el. After reading the doc, it is
clear and I see indeed why now ruby wants to know file encoding before
parsing it.
Nobuyoshi> Could you elaborate the problem?
The problem simply was that I did not expect this behaviour, and did not
understand the motivation behind it.
Somebody mentionned some similarities with python. Should emacs provide
a standard mechanism to insert this tag for script language modes that
need it ?
Thanks,
--
Paul
next prev parent reply other threads:[~2009-03-04 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 13:46 ruby-mode : ruby-mode-set-encoding Paul R
2009-03-03 13:55 ` Leo
2009-03-03 16:30 ` Stefan Monnier
2009-03-04 0:23 ` Nobuyoshi Nakada
2009-03-04 1:14 ` Stefan Monnier
2009-03-04 2:05 ` Stephen J. Turnbull
2009-03-04 4:07 ` Stefan Monnier
2009-03-04 6:10 ` Stephen J. Turnbull
2009-03-04 14:10 ` Stefan Monnier
2009-03-04 15:07 ` Stephen J. Turnbull
2009-03-04 16:40 ` Stefan Monnier
2009-03-04 8:25 ` Paul R [this message]
2009-03-04 14:13 ` Stefan Monnier
2009-03-04 14:56 ` Nobuyoshi Nakada
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wsb5heyz.fsf@gmail.com \
--to=paul.r.ml@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=nobu@ruby-lang.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).