From: Kaushal Modi <kaushal.modi@gmail.com>
To: John Mastro <john.b.mastro@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Cc: "wsnyder@wsnyder.org" <wsnyder@wsnyder.org>,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: Re: Odd block highlighting [master build]
Date: Tue, 20 Sep 2016 20:58:14 +0000 [thread overview]
Message-ID: <CAFyQvY22e1qH1LwxeDjh_qEBHj+omC5ATGBTfR61YGUQACGK7Q@mail.gmail.com> (raw)
In-Reply-To: <CAOj2CQQGFMXMv2qEz7ZV-BXDKnZJ4vRo_kaWB0ZxHOMB=exuCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Thanks. That's right.
While I still haven't been able to replicate the block highlighting issue
even since the first email in this thread, I believe this has always
happened in verilog-mode only (also I am working in verilog-mode 90% of the
time).
What's surprising is that switching to fundamental mode does not disable
that behavior. Not knowing much about overlays, here's a question to you
and whoever is reading this: Should the overlays for a major mode be
cleared when that mode is disabled? Or is that what generally is done and
recommended?
Kaushal
On Tue, Sep 20, 2016 at 4:49 PM John Mastro <john.b.mastro@gmail.com> wrote:
> 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
>
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1288 bytes --]
next prev parent reply other threads:[~2016-09-20 20:58 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
2016-09-20 20:58 ` Kaushal Modi [this message]
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=CAFyQvY22e1qH1LwxeDjh_qEBHj+omC5ATGBTfR61YGUQACGK7Q@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=wsnyder@wsnyder.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).