napshot/hstbm-0.13.tar.gz
Git users probably want to clone the repository instead; the
latest sources (which may include changes after the 0.13 release)
can be retrieved via "git clone":
git clone git://git.savannah.nongnu.org/hst
cheers,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
ently to the development (Git head) set of sources?
Apologies in advance if there's some documentation that I overlooked.
thanks,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
[1] http://savannah.nongnu.org/projects/hstbm
[2] http://icl.cs.utk.edu/papi/
versions on a different machine, as
suggested by Paul yesterday.
cheers,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
On 03/04/15 17:48, Paul Eggert wrote:
sur-behoffski wrote:
Looking at Grep's "configure --help" output, I see that
"--enable-gcc-warnings" is an option, and, with some experimentation with
invoking compilation in different environments, it seems that a slew of
warning
22/lib'
Makefile:1684: target '.deps/alloca.Po' given more than once in the
same rule
CC argmatch.o
CC binary-io.o
[...]
Looking at the sources, Line 308 of lib/Makefile.in may provide a
hint:
lib/Makefile.in:308:am__depfiles_remade = $(DEPDIR)/alloca.Po
./$(DEPDIR)/alloca.Po
cheers,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
IL: 0
# XPASS: 0
# ERROR: 0
========
cheers,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
ocessing is done when the modules are first
initialised (e.g. setting up some tables), and mbrtowc itself is not
thread-safe, as it assumes a "current" locale.
So, I'm not sure if a thread-safe (i.e. locale-safe) version of mbrtowc
exists; if not, this needs to be addressed befor
this is a duplicate. -- sur-behoffski]
Forwarded Message
Subject: Re: bug#23269: Multi-threaded operation, mbrtowc, and "untangle"
script [was Re: bug#23269...]
Date: Thu, 21 Apr 2016 21:32:15 +0930
From: sur-behoffski
To: arn...@skeeve.com
On 04/21/16 19:25, ar
ittedly somewhat dated, and/or for smaller architectures)
is that preserving the distinction is valuable.
Are there documentation standards, especially GNU ones, that cover this
distinction? If not, is it worth striving to gradually introduce this
in a systematic manner, e.g. "NUL (the zero c
tation
policy in the long run.
cheers,
sur-behoffski [etc...]
e bytes
skipped per test), but, for some pathological data cases, the skip
size might always be small, whereas choosing one of the shorter
strings might lead to larger skips per test, and so run faster.
cheers,
sur-behoffski (Brenton Hoff)
Programmer, Grouse Software
is at:
https://dwheeler.com/essays/filenames-in-shell.html
Hope this helps,
sur-behoffski (Brenton Hoff)
programmer, Grouse Software
On 2/28/22 06:01, Marja Koivunen wrote:
> Ok. I understand it is not possible to make “-V “ instead of “-Vfilename”
> because so many existing scripts rely on thatgrept works a certain way.
>
> Maybe there is a way to add space after “-V “ and possibly also other options
> that could be used as
This can reduce runtimes for large haystack input from seconds to
milliseconds.
While this is not a terribly common case, it's an easy item to
check for; it's possible that, in the future, patterns may become
less hand-crafted and more machine-crafted, and so this case may
become more relevant
On 2025-01-16 08:05, Paul Eggert wrote:
> On 2025-01-15 02:51, Anton Samokat wrote:
>> Please, make it more simple and straightforward, remove possible ambiguity
>
> Unfortunately these are competing goals.
>
> Perhaps this would be better:
>
> If no FILE is given read standard input, but if -r
On 2025-01-16 15:32, Jim Meyering wrote:
> On Wed, Jan 15, 2025 at 8:16 PM sur-behoffski
> wrote:
> [...]>
> Thanks for the suggestions. I went with Paul's (keeping it concise is
> important), so --help now prints this:
>
> When FILE is '-', read sta
16 matches
Mail list logo
