From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: special characters in file names issue
Date: Sat, 11 Nov 2023 10:19:23 -0800 [thread overview]
Message-ID: <CAH+w=7a=wjVuuAno4d40zz7he3a4O5X6aBmicY0YLmKroQrRaA@mail.gmail.com> (raw)
In-Reply-To: <fa2af3a1-ff04-44dd-890f-872fb6e5f836@eastlink.ca>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Sat, Nov 11, 2023, 9:18 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
> what would be the practicalities of Thomas just hacking the code to his
> own satisfaction? That kind of solution never seems to be suggested but it
> would seem to be a possibility.
>
It's always implicit that anyone can submit a patch, though usually that
should happen on zsh-workers rather than -users. (Everyone on -workers gets
to see -users by default, so the distinction is mostly so the consumers
don't have to see the sausage being made, so to speak.) But at least for
me the presumption on -users is that an answer that works now is preferable
to one that has to wait for the next version or use a local build.
[-- Attachment #2: Type: text/html, Size: 1083 bytes --]
next prev parent reply other threads:[~2023-11-11 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 23:16 Jim
2023-11-10 5:04 ` Mikael Magnusson
2023-11-10 9:50 ` Roman Perepelitsa
2023-11-10 14:17 ` Mikael Magnusson
2023-11-10 14:28 ` Roman Perepelitsa
2023-11-11 18:26 ` Jim
2023-11-10 16:33 ` Lawrence Velázquez
2023-11-10 17:02 ` Bart Schaefer
2023-11-10 20:37 ` Roman Perepelitsa
2023-11-11 0:13 ` Bart Schaefer
2023-11-11 17:18 ` Ray Andrews
2023-11-11 18:19 ` Bart Schaefer [this message]
2023-11-11 18:52 ` Ray Andrews
2023-11-11 18:26 ` Jim
2023-11-12 0:08 ` Bart Schaefer
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='CAH+w=7a=wjVuuAno4d40zz7he3a4O5X6aBmicY0YLmKroQrRaA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--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).