Re: one-character expansion in shell

Hi Philipp, Philipp Buehler wrote on Wed, May 06, 2020 at 04:03:41PM +0200: > Am 06.05.2020 15:54 schrieb Ingo Schwarze: >> Your misunderstandiing is that file names consist of characters. >> They do not. They consist of bytes, and to match two bytes, >> you need two question marks. > One can h

Re: one-character expansion in shell

On Wed, 6 May 2020 at 14:25, Rudolf Sykora wrote: > > Hello list, > > > is this an expected behaviour? > > odin$ ls v?k* > ls: v?k*: No such file or directory > odin$ ls v??k* > výkres.1.pdfvýkres.2.pdfvýkres.5.pdfvýkres.8.pdf > výkres.10.pdf výkres.3.pdfvýkres.6.pdfvýkres.9.

Re: one-character expansion in shell

Am 06.05.2020 15:54 schrieb Ingo Schwarze: Your misunderstandiing is that file names consist of characters. They do not. They consist of bytes, and to match two bytes, you need two question marks. One can hold for the OP; the ksh(1) manpage talks about "characters" in 'File name patterns' thro

Re: one-character expansion in shell

Hi Rudolf, Rudolf Sykora wrote on Wed, May 06, 2020 at 03:25:09PM +0200: > is this an expected behaviour? Yes, that is expected behaviour. > odin$ ls v?k* > ls: v?k*: No such file or directory > odin$ ls v??k* [ some file names containing two-byte UTF-8 sequences ] > odin$ locale The locale

one-character expansion in shell

Hello list, is this an expected behaviour? odin$ ls v?k* ls: v?k*: No such file or directory odin$ ls v??k* výkres.1.pdfvýkres.2.pdfvýkres.5.pdfvýkres.8.pdf výkres.10.pdf výkres.3.pdfvýkres.6.pdfvýkres.9.pdf výkres.11.pdf výkres.4.pdfvýkres.7.pdf odin$ locale LANG= LC