From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: mike yao <yaoweizhen@gmail.com>,
Seraphees <shaowei.dai@gmail.com>,
Emacs Devel <emacs-devel@gnu.org>
Subject: utf-8 elisp problem
Date: Mon, 28 Apr 2008 19:05:22 +0200 [thread overview]
Message-ID: <481603D2.2090100@gmail.com> (raw)
In-Reply-To: <424e2e1c0804280931n5df0caecm253774b81038c523@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Thanks mike, that made it clear that this problem is over my head. I am
not sure if this is a bug or not. I am sending this on Emacs devel where
I am sure there a people who understand this better than me.
So the problem is this:
- When mike or Shaowei loads the attached file they get the error below.
- When I do it I get no error.
Can someone please explain what is happening? I think mike has some more
information about utf-8 environment, see below.
----------------
Subject: Re: error on nxhtml version higher than 1.03
mike yao wrote:
> I have ran your code, there is same message:
> Debugger entered--Lisp error: (invalid-read-syntax "] in a list")
> eval-buffer() ; Reading at buffer position 103
> call-interactively(eval-buffer nil nil)
>
> I also found that ran with emacs -Q, can't read the '«' character in
> utf8-problem.el file, but in utf-8 enviroment, it can
>
> On Tue, Apr 29, 2008 at 12:14 AM, Lennart Borgman (gmail)
> <lennart.borgman@gmail.com <mailto:lennart.borgman@gmail.com>> wrote:
>
> Thanks Shaowei, this helped me (though it was not exactly what I meant).
>
> Can you try to load the attached file with
>
> M-x load-file
>
> Before loading it please do
>
> M-: (setq debug-on-error t)
>
> If you get an error trace back please send it to me.
[-- Attachment #2: utf8-problem.el --]
[-- Type: text/plain, Size: 115 bytes --]
(defvar utf8-problem
"\\(?:^\\|[[:space:]]\\)\\(?:href\\|src\\)[[:space:]]*=[[:space:]]*\"\\([^<«\"]*\\)\"")
next parent reply other threads:[~2008-04-28 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cda1dc92-1fb4-4eb9-8d7b-f3dd1f2ec7e5@24g2000hsh.googlegroups.com>
[not found] ` <4811a586-7b25-405b-8970-5aeff5ee0774@q1g2000prf.googlegroups.com>
[not found] ` <481183C3.70102@gmail.com>
[not found] ` <ba2332470804250040v79e2bc41n911c8b3ebb71c860@mail.gmail.com>
[not found] ` <4811FE4B.7010802@gmail.com>
[not found] ` <424e2e1c0804270151s39158899t4659d4a9a53e24c4@mail.gmail.com>
[not found] ` <ba2332470804271829g6df65ce7od302da493894c1b7@mail.gmail.com>
[not found] ` <48156EA6.1020806@gmail.com>
[not found] ` <ba2332470804272352k27546a87g23d59a70b5ffa25f@mail.gmail.com>
[not found] ` <4815F7E1.1080307@gmail.com>
[not found] ` <424e2e1c0804280931n5df0caecm253774b81038c523@mail.gmail.com>
2008-04-28 17:05 ` Lennart Borgman (gmail) [this message]
2008-04-28 18:09 ` utf-8 elisp problem Stefan Monnier
2008-04-28 18:53 ` Lennart Borgman (gmail)
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=481603D2.2090100@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=shaowei.dai@gmail.com \
--cc=yaoweizhen@gmail.com \
/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).