From: "Stéphane Glondu" <steph@glondu.net>
To: Sam Steingold <sds@gnu.org>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] new emacs tuareg mode release
Date: Wed, 26 May 2010 08:27:07 +0200 [thread overview]
Message-ID: <4BFCBF3B.1050205@glondu.net> (raw)
In-Reply-To: <AANLkTinaEKqRmatLmFxhjf9I_eu7UD1HxsUZlxtGnJVj@mail.gmail.com>
Sam Steingold a écrit :
>> I have the same problem with 22.3.1
>>
>> playing around, this construction seems to be causing some invalid modifier
>> errors:
>> (skip-syntax-backward "\s-")
>>
>> in tuareg-find-colon-typespec and other places
>
> what kind of error?
> I.e., start emacs like this:
> $ emacs -q --no-site-file
> and type in the *scratch* buffer and tell me what you type and cut and
> paste the error message from the *Messages* buffer.
On emacs 22.3.1,
(skip-syntax-backward "\s-")
gives the backtrace:
Debugger entered--Lisp error: (error "Invalid modifier in string")
read(#<buffer *scratch*>)
preceding-sexp()
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
recursive-edit()
byte-code("\306^P
@\307=\203!^@\310\311\312\"\210\313\311!\211^ZA@)\242\314=\203!^@\310\315\312\"\210\316^K!\210\317
\210\320 !\210\f\203c^@\321ed\"^MV\203W^@eb\210\322^$
debug(error (error "Invalid modifier in string"))
read(#<buffer *scratch*>)
preceding-sexp()
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
(and nothing in *Messages*)
By the way, I wasn't able to find documentation for this construct. The
"\s" is responsible, but I have no idea what is its semantics. I have
not been able to observe a behaviour different than with just
(skip-syntax-backward "-").
Cheers,
--
Stéphane
next prev parent reply other threads:[~2010-05-26 6:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 16:36 Sam Steingold
2010-05-24 16:55 ` [Caml-list] " Stéphane Glondu
2010-05-24 17:17 ` Sam Steingold
2010-05-24 18:41 ` Philip
2010-05-24 20:09 ` Sam Steingold
2010-05-24 20:36 ` Philip
2010-05-24 20:58 ` Sam Steingold
2010-05-25 1:00 ` Eliot Handelman
2010-05-25 10:17 ` Jan Rehders
2010-05-25 18:04 ` Sam Steingold
2010-05-26 6:27 ` Stéphane Glondu [this message]
2010-05-26 13:33 ` Sam Steingold
2010-05-26 14:31 ` New emacs tuareg mode Christophe TROESTLER
2010-05-26 15:36 ` [Caml-list] " Daniel Bünzli
2010-05-26 16:01 ` Christophe TROESTLER
2010-05-26 16:34 ` Stefano Zacchiroli
2010-05-27 9:46 ` David Baelde
2010-05-27 14:25 ` Eray Ozkural
2010-05-27 15:41 ` Grant Rettke
2010-05-27 16:01 ` Edgar Friendly
2010-05-29 13:16 ` David Baelde
2010-05-24 20:34 ` [Caml-list] new emacs tuareg mode release blue storm
2010-05-26 10:02 ` Tom Hutchinson
2010-05-26 13:18 ` Eliot Handelman
2010-05-26 13:32 ` Jacques Garrigue
2010-05-26 13:33 ` Mehdi Dogguy
2010-05-26 14:01 ` Christophe TROESTLER
2010-05-26 14:09 ` Mehdi Dogguy
2010-05-24 21:44 ` Sam Steingold
2010-05-25 18:08 ` [Caml-list] " Mehdi Dogguy
2010-05-25 18:25 ` Christophe TROESTLER
2010-05-24 21:50 ` Sam Steingold
2010-05-26 22:53 ` Sam Steingold
2010-06-11 12:22 ` [Caml-list] " Albert Cohen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFCBF3B.1050205@glondu.net \
--to=steph@glondu.net \
--cc=caml-list@yquem.inria.fr \
--cc=sds@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