all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Different behaviour while debugging?
Date: Wed, 20 Feb 2013 17:31:40 +0100	[thread overview]
Message-ID: <87ehgbkkur.fsf@gmail.com> (raw)
In-Reply-To: jwv621n2d78.fsf-monnier+gmane.emacs.help@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> but inside the 'cond function in the while loop, the out-commented lines
>> ("comline") are not recognized when run normally
>
> My crystal ball is very cloudy but it seems like it's trying to tell me
> that single-stepping via edebug causes the file's content to be
> displayed before you run the code, and displaying this content causes it
> to be font-locked, which ends up adding some syntax-table properties
> which make those comments recognized as such.

that sounds quite reasonable to me, thank you, might 'comment-start',
'comment-end' and 'comment-padding' be among such syntax-table
properties? 

it works as expected with emacs lisp, picolisp and latex, but not in
html-mode (only mode among these that uses 'comment-start' *and*
'comment-end'), so maybe 'comment-end' is involved in the problem.

Is this a mistake of my program not to display the content before
running the code? With which elisp-trickery could I always enforce to
display the content first?

Or is this a problem with Emacs, and my program should not care about
these things? 

-- 
cheers,
Thorsten




  reply	other threads:[~2013-02-20 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 14:57 Different behaviour while debugging? Thorsten Jolitz
2013-02-20 15:08 ` Drew Adams
2013-02-20 15:45   ` Thorsten Jolitz
2013-02-20 16:25     ` Drew Adams
2013-02-20 16:50       ` Thorsten Jolitz
2013-02-20 15:56 ` Stefan Monnier
2013-02-20 16:31   ` Thorsten Jolitz [this message]
2013-02-22 14:06     ` Stefan Monnier
2013-02-22 17:44       ` Thorsten Jolitz
2013-02-22 18:56 ` Andreas Röhler
2013-02-23  9:07   ` Thorsten Jolitz
2013-02-23 11:35     ` Andreas Röhler

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehgbkkur.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.