Re: Modify buffering of standard streams via environment variables (not LD_PRELOAD)?

2024-04-20 Thread wrotycz
 Sat, Apr 20, 2024 at 16:45 Carl Edquist wrote:However, stdout 
and stderr are still separate streams even if they refer to the same output 
file/pipe/device, so partial lines are not interleaved in the order that they 
were printed. will output abc\n123\n instead of 
a1b2c3\n\n, even if you run it as   $ ./abc123 21 | cat  
 It seems that its interleaved when buffer is written to a file 
or pipe, and because stdout is buffered it waits until buffer is full or 
flushed, while stderr is not and it doesnt wait and write immediately.


Re: Re: GNU Coding Standards, automake, and the recent xz-utils backdoor

2024-04-04 Thread wrotycz
 lz4 and zstd are quite a bit less resource-hungry than xz   Is it?  By 
default, and up to -19 level, zstd uses 8 MiB (sliding) window, when xz uses 8 
MiB at level 6, which is default, default and doubles is every next level. More 
over that, xz compression with 8 MiB window uses 96 MiB of memory, when zstd 
needs 272 MiB at level 19, 224 MiB at lv. 16 and 232 MiB at lv. 12.  Similarily 
with decompression - xz needs 11 MiB to decompress archive with 8 MiB window, 
zstd needs 30 MiB to decompress it.   I dont see where zstd is less 
resource-hungry than xz. With these options, the zst tarball came 
withing a hares breath of the xz compressed file size.   Here are some 
samples of about 8 MB files compressed with bzip2, gzip, xz and zstd with 
different levels of compression:   paste.ee paste.ee/p/tVIWG  paste.ee 
paste.ee/p/PsNrxI did not find any drawbacks.   Except higher memory 
requirements, lower compression, similar issues with long term archiving 
usefulness, there are no drawbacks.


Re: Re: Date setting examples in manual

2024-03-29 Thread wrotycz
 I think one example (the first) would be enough in the manualBetter 
than nothing, but helps.  Thanks Note we do give more details in the 
full documentationAnd who reads that? If its not in `prog --help`, nor 
in `man prog`, then everyone is going to go to search engine rather than GNU 
html documentation.  And its basic operation, and me, add a user, expect 
basic help. Not super advanced help.Regards


Correction to pl po translation

2024-03-24 Thread wrotycz
I noticed some minor mistakes or inconsistences in translation so I send 
correction.   Regards  Wrotycz
--- pl.po~  2023-08-29 14:00:27.0 +
+++ pl.po   2024-03-24 18:59:24.0 +
@@ -355,7 +355,7 @@ msgstr "Błędne wyrażenie regularne"
 # ? - rzm
 #: lib/regcomp.c:131
 msgid "Invalid collation character"
-msgstr "Znak błędny dla bieżącego uporządkowania"
+msgstr "Błędny znak bieżącego uporządkowania"
 
 #: lib/regcomp.c:134
 msgid "Invalid character class name"
@@ -395,11 +395,11 @@ msgstr "Brak pamięci"
 
 #: lib/regcomp.c:161
 msgid "Invalid preceding regular expression"
-msgstr "Błędne wyrażenie regularne"
+msgstr "Błędne poprzednie wyrażenie regularne"
 
 #: lib/regcomp.c:164
 msgid "Premature end of regular expression"
-msgstr "Przedwczesny koniec szukania wyrażenia regularnego"
+msgstr "Przedwczesny koniec wyrażenia regularnego"
 
 #: lib/regcomp.c:167
 msgid "Regular expression too big"


Date setting examples in manual

2024-03-24 Thread wrotycz
I noticed there are no examples of how to set date using date, in the manual. 
Therefore I propose to add these to examples section to make it clear and easy 
to do so. I used simple formats, more like machine formats to make it 
even simpler, as no one wants to use elaborate formats like Thu Mar  3 
23:05:25 2005 only to make wrong. And one of the reasons for it is 
American habit to make things complicated, to put month before day, and stuff 
like that.   Thats what I propose:   Set new data and time:   date 
--set 2001-02-03 11:12:13Set new date:   date +%Y%m%d -s 
20010203Set time:   date +%T -s 11:12:13Regards  
Wrotycz