zsh-users
 help / color / mirror / code / Atom feed
From: Michele Venturi <dardo82@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Bart Schaefer <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: Substitute the last match of a pattern during parameters expansion.
Date: Thu, 15 Sep 2022 03:45:04 +0200	[thread overview]
Message-ID: <CA+Ds4Nu=w0hb_Rn2Hsf66ATRS5PrpLqrGzFBQAU4LkHWCa0v8A@mail.gmail.com> (raw)
In-Reply-To: <dbe3ef1a-90c2-4b7b-a53e-69b466933dcb@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

On Thu, Sep 15, 2022, 02:29, Lawrence Velázquez, <larryv@zsh.org> wrote:

> On Wed, Sep 14, 2022, at 5:59 PM, Michele Venturi, <dardo82@gmail.com>
> wrote:
> > It seems that nobody here is able to do it now,
> > so this is the wrong place to ask for such things.
>
> Don't conflate "can't do it" with "won't do it".
>

If you can't do it (and you don't want to learn) you are useless, if you
don't want to do it (and it's a good idea)
you are guilty; anyway is it not MY problem. I will repeat
it because sadly you need it: I'm not here to ask for help,
but to help you improve YOUR project and how to do it...
So it seems like you are the one confused here, that is
refusing free suggestions and support for his activities.


> > Are there other mailing lists with more

> capable people on this specific subject?
>
> Bart has been involved with zsh for at least 27 years.  You need one hand
> to count the number of people in the world more knowledgeable about zsh
> internals.
>

These are probably too few people to work on it, right?

[-- Attachment #2: Type: text/html, Size: 2212 bytes --]

  reply	other threads:[~2022-09-15  1:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  4:20 Michele Venturi
2022-09-12  6:01 ` Lawrence Velázquez
2022-09-13  4:19   ` Michele Venturi
2022-09-13  6:06     ` Lawrence Velázquez
2022-09-13 23:11       ` Bart Schaefer
2022-09-14  3:20         ` Michele Venturi
2022-09-14 18:56           ` Bart Schaefer
2022-09-14 20:06             ` Ray Andrews
2022-09-14 21:59             ` Michele Venturi
2022-09-14 22:04               ` Bart Schaefer
2022-09-14 22:20                 ` Michele Venturi
2022-09-15  0:00                   ` Alex Satrapa
2022-09-15  0:29               ` Lawrence Velázquez
2022-09-15  1:45                 ` Michele Venturi [this message]
2022-09-15 12:01                   ` Roman Perepelitsa
2022-09-15 23:29                     ` Michele Venturi
2022-09-16  6:37                       ` Roman Perepelitsa
2022-09-16  7:52                         ` Michele Venturi
2022-09-16  7:57                           ` Roman Perepelitsa
2022-09-16  8:19                             ` Michele Venturi
2022-09-16  8:22                               ` Roman Perepelitsa
2022-09-16  8:33                                 ` Michele Venturi
2022-09-16  8:36                                   ` Roman Perepelitsa
2022-09-16  9:08                                     ` Michele Venturi

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='CA+Ds4Nu=w0hb_Rn2Hsf66ATRS5PrpLqrGzFBQAU4LkHWCa0v8A@mail.gmail.com' \
    --to=dardo82@gmail.com \
    --cc=larryv@zsh.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).