unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Mastro <john.b.mastro@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Cc: Noam Postavsky <npostavs@users.sourceforge.net>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Odd block highlighting [master build]
Date: Tue, 20 Sep 2016 13:49:07 -0700	[thread overview]
Message-ID: <CAOj2CQQGFMXMv2qEz7ZV-BXDKnZJ4vRo_kaWB0ZxHOMB=exuCg@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1PwHFs_0z+CJj-g6pPC8_YonUFqQbPKVQB8MMA4My+mg@mail.gmail.com>

Kaushal Modi <kaushal.modi@gmail.com> wrote:
> I haven't yet been able to recreate that block highlight. But here I
> get a similar highlight on a string, with flyspell mode off. I also
> switched from the default major mode verilog-mode to fundamental mode.
> And even then I get that highlight.
>
> Here is the result of C-u C-x =:
>
> http://i.imgur.com/Nx0hPmX.png
>
> I do not understand overlays very well, but it looks like verilog-mode
> or some minor mode created 5 overlays over the same region, and they
> did not get removed even when those modes were disabled.

The overlays have a verilog-include-file property so they're most likely
coming from verilog-highlight-region (unless some other mode re-uses
that property).

        John



  parent reply	other threads:[~2016-09-20 20:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 18:44 Odd block highlighting [master build] Kaushal Modi
2016-09-20 18:47 ` Odd block highlighting [emacs-25 branch build] (Was: .. master build]) Kaushal Modi
2016-09-20 19:35 ` Odd block highlighting [master build] John Mastro
2016-09-20 19:44   ` Noam Postavsky
2016-09-20 19:50     ` Kaushal Modi
2016-09-20 20:06       ` Kaushal Modi
2016-09-20 20:10         ` Kaushal Modi
2016-09-20 20:53           ` Kaushal Modi
2016-09-20 21:48             ` Noam Postavsky
2016-09-20 20:49         ` John Mastro [this message]
2016-09-20 20:58           ` Kaushal Modi
2016-09-20 19:45   ` Kaushal Modi

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='CAOj2CQQGFMXMv2qEz7ZV-BXDKnZJ4vRo_kaWB0ZxHOMB=exuCg@mail.gmail.com' \
    --to=john.b.mastro@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /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).