unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: zhang cc <ccsmile2008@outlook.com>
Cc: Alan Mackenzie <acm@muc.de>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: c-forward-sws: Is the code right?
Date: Tue, 27 Mar 2018 21:56:39 -0400	[thread overview]
Message-ID: <CAM-tV-9UXsuRDuvuFQEYEGK=72ivnxLMQS6jkMck6OMi9hnNVA@mail.gmail.com> (raw)
In-Reply-To: <SG2PR0601MB1405EBDAEFBF9E300386C9A0A8A30@SG2PR0601MB1405.apcprd06.prod.outlook.com>

On 27 March 2018 at 21:35, zhang cc <ccsmile2008@outlook.com> wrote:
>
>> Is the bug reproducible?
>
> Yes. See
> https://github.com/joaotavora/yasnippet/issues/923#issuecomment-376569337

A simpler reproduction:

    emacs -Q -f c-mode -f toggle-debug-on-error --eval '(insert "\u963Fa")'
    DEL

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  c-forward-sws()
  c-unfind-coalesced-tokens(147 148)
  c-before-change(147 148)
  delete-char(-1 nil)
  delete-backward-char(1 nil)
  backward-delete-char-untabify(1)
  c-electric-backspace(nil)
  funcall-interactively(c-electric-backspace nil)
  call-interactively(c-electric-backspace nil nil)
  command-execute(c-electric-backspace)

>> If so, could you possibly patch that bit of
>> code to add (not (equal c-opt-cpp-prefix "\\<\\>")) before the
>> (looking-at ...) form, and see if that stops the error.
>
>
> No. the value of c-opt-cpp-prefix printed as "\s *#\s *”.

I believe you mean: "\\s *#\\s *"



  reply	other threads:[~2018-03-28  1:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 14:44 c-forward-sws: Is the code right? zhang cc
2018-03-27 16:41 ` Alan Mackenzie
2018-03-27 17:15   ` Stefan Monnier
2018-03-28  1:35   ` zhang cc
2018-03-28  1:56     ` Noam Postavsky [this message]
2018-03-28 19:05     ` Alan Mackenzie
2018-03-29  3:06       ` net june
2018-03-29 10:38       ` Eli Zaretskii
2018-04-02 19:58         ` Alan Mackenzie
2018-04-02 23:58           ` Stefan Monnier
2018-04-03 17:13             ` Andy Moreton
2018-04-03 21:03               ` Stefan Monnier

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='CAM-tV-9UXsuRDuvuFQEYEGK=72ivnxLMQS6jkMck6OMi9hnNVA@mail.gmail.com' \
    --to=npostavs@gmail.com \
    --cc=acm@muc.de \
    --cc=ccsmile2008@outlook.com \
    --cc=emacs-devel@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. 
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).