On Fri, Dec 20, 2019 at 04:35:05PM -0800, L A Walsh wrote:
> On 2019/12/18 11:46, Greg Wooledge wrote:
> > To put it another way: you can write code that determines whether
> > an input character $c matches a glob or regex like [Z-a]. (Maybe.)
> >
> > But, you CANNOT write code to generate all of
On 2019/12/21 22:38, Eli Schwartz wrote:
On 12/20/19 7:35 PM, L A Walsh wrote:
⁰⁴⁵⁶⁷⁸⁹₀₁₂₃₄₅₆₇₈₉
Q.E.D.
Is that sufficient proof?
It's sufficient proof that you're wrong, yes.
If you only knew how to use the tools you have on your machine.
Given the discussion was about collat
On 2019/12/23 05:20, Greg Wooledge wrote:
On Fri, Dec 20, 2019 at 04:35:05PM -0800, L A Walsh wrote:=
You can't simply translate $start and $end to single Unicode code point
values, enumerate the Unicode characters between those two points,
and translate those characters back to the user's lo
On Mon, Dec 23, 2019 at 12:52:00PM -0800, L A Walsh wrote:
>But it wasn't. It was about generating characters between two
> characters that were given. In unicode, that would be two code points.
> Nothing about enumeration.
Please give an example, with a starting character and an ending
char
Hi Chet,
On Fri, Nov 22, 2019 at 12:02 AM Chet Ramey wrote:
> On 11/20/19 9:27 PM, Clark Wang wrote:
> > It's quite common for people to press CTRL-C to discard the current
> command
> > line. This is harmless actually for most times except when people include
> > $? in $PS1. I also show $? in r
On 2019/12/23 12:58, Greg Wooledge wrote:
On Mon, Dec 23, 2019 at 12:52:00PM -0800, L A Walsh wrote:
But it wasn't. It was about generating characters between two
characters that were given. In unicode, that would be two code points.
Nothing about enumeration.
Please give an examp
On 12/24/19 12:34 AM, L A Walsh wrote:
> I'm not sure what you want me to say about the range you chose,
> other than it would be about 128,000 characters. It would be about the
> same argument, for or against in using
> {241..128169}. I know you are trying to make some point, but
> I'm missing it
