unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Peter Milliken" <PeterM@resmed.com.au>
Cc: <bug-gnu-emacs@gnu.org>
Subject: RE: Apparent problem with looking-at?
Date: Wed, 19 Jun 2002 15:17:58 +1000	[thread overview]
Message-ID: <9E217BAD4019CE4095869023168429A9CCF91B@vulture.corp.resmed.org> (raw)

Richard,

I believe the problem was that when I originally coded this defun (some
years ago now) I had an incomplete and faulty understanding of some of the
elisp defuns I was using - in this case, it was looking-at :-).

The code should have been (As Kim Storm kindly pointed out in
gnu.emacs.bugs):

(looking-at (regexp-quote comment-start))

using this works perfectly well (and was what I originally intended :-)). I
suspect that the "bug" has existed in my code all of this time because I
rarely code in C and thus the particular fact that a C comment-start is
actually a regular expression meant that I never noticed the problem i.e. I
normally use this code snippet with other languages and thus other
comment-start definitions and was thusly (falsely) under the impression that
this code had only failed with Emacs 21.2.1 - my apologies :-).

Thankyou for your help, I fixed "my" problem :-)

Regards,
Peter

-----Original Message-----
From: Richard Stallman [mailto:rms@gnu.org]
Sent: Wednesday, June 19, 2002 12:24 PM
To: Peter Milliken
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Apparent problem with looking-at?


Would you please provide a complete self-contained test case
so that we can reproduce the problem and debug it?

    nil and never has in previous versions of Emacs. If I alter the code
snippet
    to (looking-at "/*") then it works (note the absence of the space after
the
    '*'). Also, if I place a space character at the start of the line i.e.

Note that "/*" is a regexp that matches zero or more slashes.


Warning:  Copyright ResMed.  Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient.

This communication is confidential and may contain legally privileged information. By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal privilege in,the content of the email and of any attachments.
If the recipient of this message is not the intended addressee, please call ResMed immediately on (02) 9886 5000 Sydney, Australia.

             reply	other threads:[~2002-06-19  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19  5:17 Peter Milliken [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17 23:39 Apparent problem with looking-at? Peter Milliken
2002-06-18  9:42 ` Kim F. Storm
2002-06-19  2:24 ` 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=9E217BAD4019CE4095869023168429A9CCF91B@vulture.corp.resmed.org \
    --to=peterm@resmed.com.au \
    --cc=bug-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 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).