Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15771
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Unicode range and enumeration support. |
| Date | 2019-12-23 15:58 -0500 |
| Message-ID | <mailman.1337.1577134711.1979.bug-bash@gnu.org> (permalink) |
| References | (6 earlier) <20191218194651.GH851@eeg.ccf.org> <5DFD68B9.3050202@tlinx.org> <2334eff4-8a88-18ee-b086-4ba4e80af01b@archlinux.org> <5E0128F0.5000901@tlinx.org> <20191223205826.GY851@eeg.ccf.org> |
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
character, and the resulting output. Explain why a bash user who
uses your implementation to echo {ñ..💩} (N WITH TILDE to PILE OF
POO) or whatever will feel that your answer is correct and sensible.
> It is in unicode code point order. Which is what you would use
> for unicode. If you want to sort via unicode, use the -u switch.
That isn't what the sort -u option does, and you know it. I hope.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Unicode range and enumeration support. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-12-23 15:58 -0500
csiph-web