From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, Kenichi Handa <handa@m17n.org>
Cc: bug-gnu-emacs@gnu.org, 1187@emacsbugs.donarmstrong.com
Subject: bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax
Date: Fri, 17 Oct 2008 20:24:36 +0200 [thread overview]
Message-ID: <uwsg7krkr.fsf@gnu.org> (raw)
In-Reply-To: <001401c93074$62481300$0200a8c0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <lennart.borgman@gmail.com>, <1187@emacsbugs.donarmstrong.com>,
> <wence@gmx.li>
> Date: Fri, 17 Oct 2008 09:21:16 -0700
>
> > Anyway, does the problem go away if you visit the file with
> >
> > "C-x RET c utf-8 RET C-x C-f vline.el RET"
> >
> > before evaluating it?
>
> Yes and no. I did `C-x RET c utf-8 RET C-x C-f vline.el RET'. If I then do `M-x
> load-file RET', then I get the same error. However, if instead of `M-x load-file
> RET' I use `M-x eval-buffer RET', then I don't get the error.
I meant the latter, sorry for another vague request.
> > If this does the trick, then please talk to the author and ask him to
> > include an explicit coding: cookie in the file.
>
> I can do that, if you tell me exactly what to tell him needs to be done.
Add a "coding: utf-8" cookie on the first line of the file. See the
beginning of calendar/icalendar.el for an example.
> However, is it normal that Emacs 23 raises an error if the encoding is wrong?
> Emacs 22 does not raise any error here.
I don't know. Perhaps Handa-san can tell if there's a better way of
handling this particular case, without a need for a coding cookie.
next prev parent reply other threads:[~2008-10-17 18:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwv3aivjkhw.fsf-monnier+emacsbugreports@gnu.org>
2008-10-16 21:22 ` bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax Drew Adams
2008-10-16 23:41 ` Lennart Borgman (gmail)
2008-10-17 0:00 ` Drew Adams
2008-10-17 8:18 ` Eli Zaretskii
2008-10-17 8:36 ` Lennart Borgman (gmail)
2008-10-17 9:57 ` Eli Zaretskii
2008-10-17 8:15 ` Eli Zaretskii
2008-10-17 14:26 ` Drew Adams
2008-10-17 12:30 ` Lawrence Mitchell
2008-10-17 13:07 ` Eli Zaretskii
2008-10-17 14:40 ` Drew Adams
2008-10-17 15:53 ` Drew Adams
2008-10-17 16:04 ` Eli Zaretskii
2008-10-17 14:58 ` Lennart Borgman (gmail)
2008-10-17 15:18 ` Drew Adams
2008-10-17 15:58 ` Lawrence Mitchell
2008-10-17 16:09 ` Drew Adams
2008-10-17 16:00 ` Eli Zaretskii
2008-10-17 16:21 ` Drew Adams
2008-10-17 18:24 ` Eli Zaretskii [this message]
2008-10-20 10:28 ` Kenichi Handa
2008-10-20 10:58 ` Eli Zaretskii
2008-10-21 2:40 ` Kenichi Handa
2008-10-21 4:46 ` Drew Adams
2008-10-17 15:55 ` bug#1187: marked as done (23.0.60; Cannot read vline.el - invalid read syntax) Emacs bug Tracking System
[not found] ` <handler.1187.D1187.122425837312105.notifdone@emacsbugs.donarmstrong.com>
2008-10-17 16:48 ` bug#1187: closed by Stefan Monnier <monnier@iro.umontreal.ca> (Re: bug#1187: 23.0.60; " Drew Adams
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=uwsg7krkr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1187@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=drew.adams@oracle.com \
--cc=handa@m17n.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).