Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <yann.morin@orange.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] editorconfig: fix wildcard expansion
Date: Wed, 20 Dec 2023 21:32:00 +0100	[thread overview]
Message-ID: <20231220213200.074ff76e@windsurf> (raw)
In-Reply-To: <01cce88291ac132ca8c881eaaaf3b02a4efa68a9.1702887543.git.yann.morin@orange.com>

On Mon, 18 Dec 2023 09:19:03 +0100
<yann.morin@orange.com> wrote:

> From: "Yann E. MORIN" <yann.morin@orange.com>
> 
> It turns out that wildcard expansion, * and ?, is not performed in
> matching lists {...}, at least in the vim plugin. The spec is not clear
> about that, but refer to "pattern matching through Unix shell-style
> wildcards" [0].
> 
> So, let's consider that this is not supported. Expand the patterns into
> one section each, rather than use a list.
> 
> [0] https://spec.editorconfig.org/
> 
> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
> ---
>  .editorconfig | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-12-20 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18  8:19 [Buildroot] [PATCH] editorconfig: fix wildcard expansion yann.morin
2023-12-20 20:32 ` Thomas Petazzoni via buildroot [this message]
2024-01-07 11:21 ` Peter Korsgaard

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=20231220213200.074ff76e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin@orange.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox