unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nathan Trapuzzano <nbtrap@nbtrap.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15778@debbugs.gnu.org
Subject: bug#15778: 24.3; cperl-mode causes emacs to lock up
Date: Fri, 01 Nov 2013 13:21:33 -0400	[thread overview]
Message-ID: <87sivg81pp.fsf@nbtrap.com> (raw)
In-Reply-To: <871u30cqtq.fsf@nbtrap.com>

Eli Zaretskii <eliz@gnu.org> writes:

> Is it safe to assume that a 'syntax-type' property will never cover
> exactly one buffer position?

I think the question is actually whether it's safe to assume that
font-lock-mode will never pass cperl's font-lock function a point (BEG)
on a line whose first position is the beginning of a `multiline'
`syntax-type' property.  (That's a mouth full.)

I can see why such an assumption might be made.  So far as I can tell,
the multiline property always begins at the position immediately
following certain operators.  Obviously, this can't ever be a position
satisfying (bolp), since newline is no such operator.

However, in this case, we're killing the line where the multiline
property begins, and so as cperl goes about refontifying, it appears
that the multiline property does in fact begin a line.

So in the end, no, I don't think it's a safe assumption, at least not
until _after_ fontification.

> (I have no idea why the defalias is needed to trigger the bug.)

Indeed.





  reply	other threads:[~2013-11-01 17:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 11:19 bug#15778: 24.3; cperl-mode causes emacs to lock up Nathan Trapuzzano
2013-11-01 11:46 ` Eli Zaretskii
2013-11-01 12:16   ` Nathan Trapuzzano
2013-11-01 14:41     ` Eli Zaretskii
2013-11-01 14:59       ` Nathan Trapuzzano
2013-11-01 16:26         ` Eli Zaretskii
2013-11-01 17:21           ` Nathan Trapuzzano [this message]
2013-11-01 20:23             ` Stephen Berman
2013-11-03  0:00               ` Stephen Berman
2013-11-03 12:00                 ` Nathan Trapuzzano
2013-11-03 13:41                   ` Stephen Berman
2013-11-03 13:59                     ` Nathan Trapuzzano
2013-11-03 19:39                       ` Stephen Berman
2013-11-03 19:48                         ` Nathan Trapuzzano
2013-11-03 22:22                           ` Stephen Berman
2013-11-03 22:50                             ` Nathan Trapuzzano
2013-11-04  1:48                               ` Stefan Monnier
2013-11-04  2:29                                 ` Nathan Trapuzzano
2013-11-04  3:52                                   ` Stefan Monnier
2013-11-03 14:15                   ` Stefan Monnier
2013-11-03 14:23                     ` Nathan Trapuzzano

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=87sivg81pp.fsf@nbtrap.com \
    --to=nbtrap@nbtrap.com \
    --cc=15778@debbugs.gnu.org \
    --cc=eliz@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).