unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: jimb@redhat.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Implement new symbol-start and symbol-end regexp operators
Date: Thu, 15 Jul 2004 21:38:35 -0500 (CDT)	[thread overview]
Message-ID: <200407160238.i6G2cZ108348@raven.dms.auburn.edu> (raw)
In-Reply-To: <200406100032.i5A0W1A08327@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 9 Jun 2004 19:32:01 -0500 (CDT))

I asked this before, but apparently the documentation for this has not
been updated, as far as I can tell:

   Stefan Monnier wrote:

      > I find these really useful --- finally I can isearch-regexp for
      > identifiers in code and match exactly what I mean.  Synthesizing these
      > operators from the existing ones is a pain, partly because "symbol
      > constituents" are those characters whose syntax is *either* 'word' or
      > 'symbol'.

      Installed,

   You seem to have installed Jim's changes to search.c and regex.c, but
   not to searching.texi, nor, in as far as I can tell, to the NEWS.  As a
   result, the changes are, in as far as I can tell, completely undocumented.

   Is there a reason for that?

  reply	other threads:[~2004-07-16  2:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 22:57 Implement new symbol-start and symbol-end regexp operators Jim Blandy
2004-05-01  9:44 ` Richard Stallman
2004-05-04 19:17   ` Jim Blandy
2004-05-05  6:20     ` Eli Zaretskii
2004-05-05  6:14       ` Jim Blandy
2004-05-05 20:21         ` Richard Stallman
2004-05-05 21:10           ` Stefan Monnier
2004-05-12 17:36         ` Jim Blandy
2004-05-19 16:38 ` Stefan Monnier
2004-06-10  0:32   ` Luc Teirlinck
2004-07-16  2:38     ` Luc Teirlinck [this message]
2004-07-16  2:45       ` Luc Teirlinck
2004-07-16 12:43       ` Stefan
2004-07-16 17:49         ` Luc Teirlinck

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=200407160238.i6G2cZ108348@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jimb@redhat.com \
    --cc=monnier@iro.umontreal.ca \
    /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).