|
From: | carmen |
Subject: | [bug-enscript] [bug #57965] the wildcard * for input files daes not work properly? |
Date: | Mon, 31 May 2021 07:02:15 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Follow-up Comment #2, bug #57965 (project enscript): [comment #1 comentario nº1:] > I wasn't able to reproduce this with GNU Enscript 1.6.5.90: > > > horizon:~/tmp/enscript/57965$ rm -f *.f; for n in P0_1 P0_2 P0_3 P0_4 P0_5 P1_1 P1_2 P1_3 P1_4 P1_5; do printf ' PROGRAM %s\n' "$n" >| ${n}.f; done; enscript -v -pfoo.ps *.f > AFM: scanning path... > AFM: reading font map "/usr/share/enscript/afm/font.map" > processing file "P0_1.f"... > processing file "P0_2.f"... > processing file "P0_3.f"... > processing file "P0_4.f"... > processing file "P0_5.f"... > processing file "P1_1.f"... > processing file "P1_2.f"... > processing file "P1_3.f"... > processing file "P1_4.f"... > processing file "P1_5.f"... > [ 10 pages * 1 copy ] left in foo.ps > > > Could you provide more specific instructions on how to reproduce this problem with a specific version of enscript? > > The thing that looks most strange about the symptoms you show is that you specified *.f and yet the files are not being processed in lexicographic order, either. > > Can you reproduce your problem with the shell configured with (for example) the "C" locale? > > > $ LC_ALL=C > $ export LC_ALL > $ exec bash > > > _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57965> _______________________________________________ Mensaje enviado vía Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |