all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: 23869@debbugs.gnu.org
Cc: sdl.web@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#23869: 25.0.95; replace-match can crash emacs
Date: Wed, 06 Jul 2016 16:32:03 +0200	[thread overview]
Message-ID: <87oa6altwc.fsf@gmail.com> (raw)
In-Reply-To: <83a8hxpg97.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Jul 2016 18:36:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> I didn't have anything specific in mind, but indeed it's typically the
>> approach I've taken so far in similar circumstances (e.g. detecting
>> when syntax-propertize modified the buffer and cry foul if so).
>
> Thanks, I installed on emacs-25 changes to do that, and I'm closing
> this bug.

This change is causing org-capture to error out for me.  How should I
go about determining what needs to be modified in org to fix this?

This is with Org-mode version 8.3.4 (8.3.4-99-ga8e4a3-elpa @
/home/rpluim/.emacs.d/elpa/org-20160704/), based on a quick test the
Org shipped with emacs-25 does not have this problem.

Regards

Robert





      reply	other threads:[~2016-07-06 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:17 bug#23869: 25.0.95; replace-match can crash emacs Leo Liu
2016-06-29 15:37 ` Eli Zaretskii
2016-06-29 16:00   ` Leo Liu
2016-06-29 16:07     ` Eli Zaretskii
2016-06-30  3:27       ` Leo Liu
2016-06-30 15:04         ` Eli Zaretskii
2016-07-03 18:53           ` Leo Liu
2016-07-03 19:32             ` Eli Zaretskii
2016-07-03 20:08           ` Stefan Monnier
2016-07-03 20:33             ` Eli Zaretskii
2016-07-03 21:06               ` Stefan Monnier
2016-07-04 15:36                 ` Eli Zaretskii
2016-07-06 14:32                   ` Robert Pluim [this message]

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=87oa6altwc.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=23869@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sdl.web@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.