all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Heime <heimeborgia@protonmail.com>
Cc: "'Help-Gnu-Emacs (help-gnu-emacs@gnu.org)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Regexp for matching (defun lines
Date: Wed, 31 Jul 2024 21:02:32 +0000	[thread overview]
Message-ID: <DS7PR10MB5232D7F72F5FF0DF3CB3F938F3B12@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <5kzhsBHCj8GW4rjzi0sutBSutYlMHmDBIV7PD1V_v0CGB-KH5pSJPw0jrwHErO5ivHjsPTAcmmaAHXNJH4u6VON3xL6q7Hdwnf2SNxOw_G8=@protonmail.com>

> > (concat
> >  "^\\s-("
> >  (regexp-opt...)
> >  t)
> >  "\\s-+\\(\\(\\sw\\|\\s_\\)+\\)")
> 
> I see that you use "\\sw".  What is the advantage verses "[[:alnum:]-_]"

No special advantage. You can include any other
chars you want, so you can pick up, e.g.,

(defun foo!@$%^&*+={}/:42<>? ()
  (message "Hello"))

Perfectly legitimate, and none of those chars
even require escaping.

A function name can include ANY chars, including
whitespace and chars that normally have special
meaning for Lisp, but some need to be escaped
in the defun.  If you want to handle such cases,
go for it.

My point was really to point out that there are
many ways to define a function, other than just
`defun'.

> Why do you use the OR "\\|" with "\\s_" ?

Word-syntax chars plus symbol-syntax chars.
But use whatever you like.

  reply	other threads:[~2024-07-31 21:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 19:23 Regexp for matching (defun lines Heime
2024-07-31 19:59 ` [External] : " Drew Adams
2024-07-31 20:14   ` Heime
2024-07-31 21:02     ` Drew Adams [this message]
2024-07-31 21:15       ` Heime
2024-08-01  2:11         ` Drew Adams
2024-07-31 21:29       ` Heime
2024-08-01  2:08         ` Drew Adams
2024-08-01  2:24           ` Heime
2024-08-01  3:34             ` Drew Adams
2024-08-01  4:15               ` Heime

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=DS7PR10MB5232D7F72F5FF0DF3CB3F938F3B12@DS7PR10MB5232.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=heimeborgia@protonmail.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.