From: JD Smith <jdsmith@as.arizona.edu>
Subject: Re: Font-lock in COMINT modes
Date: Thu, 07 Dec 2006 09:38:23 -0700 [thread overview]
Message-ID: <pan.2006.12.07.16.38.22.999820@as.arizona.edu> (raw)
In-Reply-To: pan.2006.12.07.00.57.36.274572@as.arizona.edu
On Wed, 06 Dec 2006 17:57:36 -0700, JD Smith wrote:
>
> In Emacs 22, my idlwave-shell mode font-lock fontifies
> comments/strings/etc. without having been asked to. This can be
> problematic if you miss a closing quote, and all subsequent text gets
> string fontification. In Emacs 21, the only fontification was comint
> coloring the prompt blue.
>
> I don't mind the fontification so much (in fact I like it), it's just
> that missing string quotes allow it to run away, latching onto parts
> of the subsequent input and output in a way that's hard to cancel.
> Perhaps there is an easy way to inhibit scanning through the prompt?
A strange side note. In attempting to find out why strings and
comments are being fontified in my comint shell, despite the fact
that:
font-lock-defaults is a variable defined in `font-core.el'.
Its value is (nil)
Local in buffer *idl*; global value is nil
I attempted to instrument `font-lock-default-fontify-region'. Edebug
couldn't do so, giving this error:
Debugger entered--Lisp error: (invalid-read-syntax "Expected lambda
expression")
next prev parent reply other threads:[~2006-12-07 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 0:57 Font-lock in COMINT modes JD Smith
2006-12-07 16:38 ` JD Smith [this message]
2006-12-07 18:00 ` JD Smith
2006-12-09 1:26 ` Richard Stallman
2006-12-09 2:15 ` JD Smith
2006-12-09 4:02 ` Stefan Monnier
2006-12-11 16:22 ` JD Smith
2006-12-12 14:29 ` Richard Stallman
[not found] ` <87vekaf780.fsf@stupidchicken.com>
2006-12-18 16:00 ` Richard Stallman
2006-12-18 16:36 ` Chong Yidong
2006-12-18 20:38 ` Stefan Monnier
2006-12-20 13:00 ` Richard Stallman
2006-12-20 22:06 ` Stefan Monnier
2006-12-09 18:25 ` Richard Stallman
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=pan.2006.12.07.16.38.22.999820@as.arizona.edu \
--to=jdsmith@as.arizona.edu \
/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).