all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: regex.c simplification
Date: Fri, 20 Jul 2018 09:58:12 +0300	[thread overview]
Message-ID: <83wotq1ji3.fsf@gnu.org> (raw)
In-Reply-To: <7cc7d274-ee6a-ab14-c78a-4fdba963578b@cs.ucla.edu> (message from Paul Eggert on Thu, 19 Jul 2018 17:59:12 -0700)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 19 Jul 2018 17:59:12 -0700
> 
> No, etags uses the regexp code only for --regex arguments. It would of course be 
> simpler to disable --regex on platforms lacking the glibc regex API. However, my 
> impression is that etags --regex gets some use. For example:
> 
> https://stackoverflow.com/questions/21283687/what-do-you-put-in-your-standard-etags-regex-calls
> http://xahlee.info/comp/ctags_etags_gtags.html

We actually use the --regex switch in our own Makefile, for the TAGS
target, see src/Makefile.in.



  parent reply	other threads:[~2018-07-20  6:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16 15:35 regex.c simplification Daniel Colascione
2018-06-16 15:53 ` Eli Zaretskii
2018-06-16 16:11   ` Paul Eggert
2018-06-16 16:17     ` Daniel Colascione
2018-06-16 18:06     ` Andreas Schwab
2018-06-16 19:27       ` Perry E. Metzger
2018-06-17 16:50         ` Clément Pit-Claudel
2018-06-18 14:08     ` Stefan Monnier
2018-07-17 23:58       ` Paul Eggert
2018-07-20  0:33         ` Stefan Monnier
2018-07-20  0:59           ` Paul Eggert
2018-07-20  1:42             ` Stefan Monnier
2018-07-20  6:59               ` Eli Zaretskii
2018-07-20 21:49                 ` Paul Eggert
2018-07-21  6:43                   ` Eli Zaretskii
2018-07-21  7:17                     ` Paul Eggert
2018-08-01  0:17                       ` Paul Eggert
2018-08-01  2:38                         ` Brett Gilio
2018-07-20  6:58             ` Eli Zaretskii [this message]
2018-06-16 16:12   ` Daniel Colascione
2018-06-16 16:43     ` Perry E. Metzger
2018-06-16 16:09 ` Noam Postavsky
2018-06-16 16:35 ` Perry E. Metzger
2018-06-16 16:42   ` Daniel Colascione
2018-06-16 16:55     ` Eli Zaretskii
2018-06-16 18:24       ` Perry E. Metzger
2018-06-16 18:29         ` Eli Zaretskii
2018-06-16 18:58           ` Perry E. Metzger
2018-06-16 19:27             ` Eli Zaretskii
2018-06-18  9:36               ` Robert Pluim

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=83wotq1ji3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --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 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.