unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T. V. Raman" <raman@users.sf.net>
Cc: raman@users.sf.net, emacs-devel@gnu.org
Subject: Re: font-lock and shell scripts: Raises redisplay errors in highlight pattern:
Date: Thu, 6 Jul 2006 21:01:29 -0700	[thread overview]
Message-ID: <17581.56473.552614.576371@localhost.localdomain> (raw)
In-Reply-To: <m33bdfqcgi.fsf@kfs-l.imdomain.dk>


I'll try to reproduce a backtrace --- wil need to first disable
the advice I threw around it to get rid of the annoyance.

Note that I've not changed or modified font-lock-keywords for
shell-script mode as far as I can tell.

One possibility is that I'm noticing these errors when others
dont because I advice 'error in emacspeak to get auditory alerts
for errors.
Since 'error does not return, this has to be a before advice.
A side-consequence of this is that errors that are later by  an
error-handler further up the call stack end up still getting
signaled auditorally. 




>>>>> "Kim" == Kim F Storm <storm@cua.dk> writes:
    Kim> "T. V. Raman" <raman@users.sf.net> writes:
    >> Hi,
    >> 
    >> This has been around for some months now and I've been too
    >> lazy to track down its exact source until now.
    >> 
    >> Symptom:
    >> 
    >> When editting shell scripts with font-lock turned on,
    >> emacs raises errors during redisplay -- specifically in
    >> functions
    >> 
    >> font-lock-apply-syntactic-highlight
    >> font-lock-apply-highlight
    >> 
    >> Once these errors hit, highlighting doesn't appear to
    >> happen correctly.
    Kim> 
    Kim> What kind of errors are raised "during redisplay".
    Kim> 
    Kim> Does turning on Options > Debug on Error provide more
    Kim> information?
    Kim> 
    Kim> -- Kim F. Storm <storm@cua.dk> http://www.cua.dk

-- 
Best Regards,
--raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

  reply	other threads:[~2006-07-07  4:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  3:38 font-lock and shell scripts: Raises redisplay errors in highlight pattern: T. V. Raman
2006-07-06  8:29 ` Romain Francoise
2006-07-06 10:01 ` Kim F. Storm
2006-07-07  4:01   ` T. V. Raman [this message]
2006-07-07 14:18     ` Stefan Monnier
2006-07-13  4:08       ` T. V. Raman
2006-07-13 15:30         ` Stefan Monnier
2006-07-14  1:28           ` T. V. Raman
2006-07-14  4:06         ` Richard Stallman
2006-07-14 13:00           ` T. V. Raman
2006-07-14 13:04             ` David Kastrup
2006-07-14 13:09             ` Chong Yidong
2006-07-15  1:43               ` T. V. Raman
2006-07-15 13:37             ` Richard Stallman
2006-07-15 14:27               ` T. V. Raman
2006-07-16  6:25                 ` Richard Stallman
2006-07-16 17:18                   ` T. V. Raman

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=17581.56473.552614.576371@localhost.localdomain \
    --to=raman@users.sf.net \
    --cc=emacs-devel@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).