On Fri, Mar 29, 2013 at 07:08:21PM +0100, Christoph Lohmann wrote:
> Greetings.
>
>
> Please retry with current from git, if this persists.
>
>
> Sincerely,
>
> Christoph Lohmann
Just tried again with st git version and openbsd -current from March
29th.
The problem persists even with the def
On 03/31/2013 06:03 PM, Charlie Kester wrote:
Why add this extra complexity when stdio is already buffering the
input stream?
I did not mean to imply double-buffering. In fact, I figured I should've
linked to documentation on input streams seconds after I sent the mail.
On 03/31/2013 10:37, Bjartur Thorlacius wrote:
On 03/31/2013 01:52 PM, Charlie Kester wrote:
I'd read the file one character at a time, counting newlines, until I
reached the desired line. [..] Doing it this way avoids the need for a
buffer altogether, along with any guessing about possible line
On 03/31/2013 01:52 PM, Charlie Kester wrote:
I'd read the file one character at a time, counting newlines, until I
reached the desired line. [..] Doing it this way avoids the need for a
buffer altogether, along with any guessing about possible line lengths.
Reading is expensive. Loop through a
On 3/31/13, Calvin Morrison wrote:
> On Mar 31, 2013 9:57 AM, "Charlie Kester" wrote:
>>
>> On 03/30/2013 23:49, Chris Down wrote:
>>>
>>> GNU coreutils packages awful versions of
>>> awk/sed.
GNU awk and GNU sed are too big to be included in coreutils. They're
both separate packages.
> Sed d
On 03/31/2013 07:19, Calvin Morrison wrote:
Sed does many things and many things well, but the unix philosophy is to do
one thing and one thing well.
Perhaps you have too narrow an understanding of "one thing"?
As others have pointed out, the people who created Unix devised numerous
language
On 2013-03-31 10:19, Calvin Morrison wrote:
> Sed does many things and many things well, but the unix philosophy is to do
> one thing and one thing well.
What? I'm not even sure if this is serious any more...
These are interfaces to *languages*. The program does only one thing: interfaces
with th
Have you even read TUPE?
On Mar 31, 2013 4:19 PM, "Calvin Morrison" wrote:
>
> On Mar 31, 2013 9:57 AM, "Charlie Kester" wrote:
> >
> > On 03/30/2013 23:49, Chris Down wrote:
> >>
> >> I really don't see the need for a tool like this. Saying sed and awk are
> >> not suckless is like saying C is
On Mar 31, 2013 9:57 AM, "Charlie Kester" wrote:
>
> On 03/30/2013 23:49, Chris Down wrote:
>>
>> I really don't see the need for a tool like this. Saying sed and awk are
>> not suckless is like saying C is not suckless -- sed and awk are
languages
>> with a very specific domain, text processing.
On 03/30/2013 23:49, Chris Down wrote:
I really don't see the need for a tool like this. Saying sed and awk are
not suckless is like saying C is not suckless -- sed and awk are languages
with a very specific domain, text processing. Perhaps you think *an
implementation* sucks. Good. GNU coreutils
2013/3/31 Calvin Morrison
> Sed and awk are not suckless, they are very anti-unix philosophy in my
> mind.
>
I disagree.
Personnally, I use very often awk on scripts, because it allows multiple
statements and it also replaces grep / cut.
I think it's one of the most powerful tool I've ever seen.
On 03/30/2013 19:27, Calvin Morrison wrote:
Is there a better way to read a whole line? fgets requires a length
argument, so I suppose it's not a very good solution
Framing the problem that way is where you went astray.
I'd read the file one character at a time, counting newlines, until I
re
Greetings.
On Sun, 31 Mar 2013 11:58:00 +0200 Nick wrote:
> Attached is a patch enabling HTTP redirection following by curl, for
> the download stuff in curl. This is useful as a bunch of websites
> rely on 302 redirects for their download sections, Project Gutenberg
> being a good example.
T
13 matches
Mail list logo
