unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Tury <tury.peter@gmail.com>
Subject: Re: identifiing strings and comments in program source files (to skip them over)
Date: Wed, 26 Apr 2006 08:04:06 GMT	[thread overview]
Message-ID: <1rr66a7a2k4a8.n59erpn8woet.dlg@40tude.net> (raw)
In-Reply-To: 7epsj5vvqa.fsf@ada2.unipv.it

On Wed, 26 Apr 2006 05:53:01 +0200, Thien-Thi Nguyen wrote:

> Peter Tury <tury.peter@gmail.com> writes:
> 
>> What do you think: can a robust solution be built using this approach?
> 
> yes, if you now how (and how much) to wait for font lock to do its job:

Yes, I had a feeling this could be a problem.
When I eval (text-properties-at (point)) I see e.g. (face
font-lock-comment-face fontified t). Can I use this "fontified" for
checking if font lock is done? Or this remains always t if fontified once?
What is this "fontified" exactly? How can I get more info? Please point me
some place in the manual.

Anyway, I would like to get some hideshow ;-)) (I couldn't use hideshow.el
until now for this major mode; now I plan to reuse it somehow, with
modifications.) So I hope fontification will be ready when I search (for
hide/show.)

Thanks!
P

  reply	other threads:[~2006-04-26  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 21:14 identifiing strings and comments in program source files (to skip them over) Peter Tury
2006-04-26  3:53 ` Thien-Thi Nguyen
2006-04-26  8:04   ` Peter Tury [this message]
2006-04-26  6:01 ` Stefan Monnier
2006-04-26  8:06   ` Peter Tury
  -- strict thread matches above, loose matches on Subject: below --
2006-04-26  6:38 martin rudalics
     [not found] <mailman.964.1146057880.9609.help-gnu-emacs@gnu.org>
2006-04-26 19:05 ` Peter Tury

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=1rr66a7a2k4a8.n59erpn8woet.dlg@40tude.net \
    --to=tury.peter@gmail.com \
    /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.
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).