git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gitignore: warn about pointless syntax

From
Jeff King <peff@peff.net>
Date
Jan 9, 2012, 22:33 UTC
Message-ID
<20120109223358.GA9902@sigill.intra.peff.net>
In-Reply-To
<7vhb04ek6e.fsf@alter.siamese.dyndns.org>
On Mon, Jan 09, 2012 at 11:43:21AM -0800, Junio C Hamano wrote:
Show 18 quoted lines
> >> +static inline void check_bogus_wildcard(const char *file, const char *p)
> >> +{
> >> +	if (strstr(p, "**") == NULL)
> >> +		return;
> >> +	warning(_("Pattern \"%s\" from file \"%s\": Double asterisk does not "
> >> +		"have a special meaning and is interpreted just like a single "
> >> +		"asterisk.\n"), file, p);
> >
> > Wouldn't this also match the meaningful "foo\**"?
> 
> Yes.
> 
> But trying to catch that false positive by checking one before "**"
> against a backslash is not a way to do so as it will then turn "foo\\**"
> into a false negative, and you would end up reimplementing fnmatch if you
> really want to avoid false positives nor negatives. At that point, you may
> be better off implementing git_fnmatch() instead that understands the
> double-asterisk that works as some people may expect it to work ;-).

You only have to implement proper backslash decoding, so I think it is not as hard as reimplementing fnmatch:

  enum { NORMAL, QUOTED, WILDCARD } context = NORMAL;
  for (i = 0; p[i]; i++) {
          if (context == QUOTED)
                  context = NORMAL;
          else if (p[i] == '\\')
                  context = QUOTED;
          else if (p[i] == '*') {
                  if (context == WILDCARD) {
                        warning(...);
                        return;
                  }
                  context = WILDCARD;
          }
          else
                  context = NORMAL;
  }

That being said, if this is such a commonly-requested feature that we need to be detecting and complaining about its absence, I would be much more in favor of simply implementing it. Surely fnmatch is not that hard to write, or we could lift code from glibc or even rsync.

Which perhaps was what you are getting at, but I am happy to say it more explicitly. :)

-Peff
Previous: Junio C HamanoNext: Jan Engelhardt
Message 5 of 11 in “gitignore warn about ** submission”
  1. Jan EngelhardtJan 9, 2012
  2. gitignore: warn about pointless syntaxJan Engelhardt, Jan 9, 2012
  3. Jeff KingJan 9, 2012
  4. Junio C HamanoJan 9, 2012
  5. Jeff KingJan 9, 2012
  6. Jan EngelhardtJan 10, 2012
  7. Junio C HamanoJan 10, 2012
  8. Jan EngelhardtJan 10, 2012
  9. Jan EngelhardtJan 10, 2012
  10. Thomas RastJan 10, 2012
  11. Jeff KingJan 10, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.