I have a file that looks like this:

$ head newsrc-news.eternal-september.org-test
nl.newsgroups.announce: 1-1329
free.uk.amateur-radio: 1-15497
uk.media.radio.misc: 1-456
uk.radio.amateur: 1-377688,377690,377692,377694-377697,377699,377701-377704
uk.radio.amateur.moderated: 1-6432
uk.legal.moderated: 1-378428
comp.security.ssh: 1-3221
alt.comp.software.newsreaders: 1-481
uk.net.news.moderation: 1-64428
free.uk.legal: 1-275

I want to convert all the last part of the lines from 1-whatever to 1-1

I have tried:

$ sed -i 's/"1-*"/'1-1'/g' newsrc-news.eternal-september.org-test

and

$ sed -i 's/"1-*"/"1-1"/g' newsrc-news.eternal-september.org-test

$ sed -i 's/"1-*"/1-1/g' newsrc-news.eternal-september.org-test

but none of them does the job.

If I do:

$ sed -i 's/1-*/"1-1"/g' newsrc-news.eternal-september.org-test

then:

$ head newsrc-news.eternal-september.org-test
nl.newsgroups.announce: "1-1""1-1""1-1""1-1"329
free.uk.amateur-radio: "1-1""1-1""1-1""1-1"5497
uk.media.radio.misc: "1-1""1-1"456
uk.radio.amateur:
"1-1""1-1"377688,377690,377692,377694-377697,377699,37770"1-1""1-1"377704
uk.radio.amateur.moderated: "1-1""1-1"6432
uk.legal.moderated: "1-1""1-1"378428
comp.security.ssh: "1-1""1-1"322"1-1""1-1"
alt.comp.software.newsreaders: "1-1""1-1"48"1-1""1-1"
uk.net.news.moderation: "1-1""1-1"64428
free.uk.legal: "1-1""1-1"275

which is not what I want.

Any help will be appreciated.

--
Ottavio Caruso

Am 06/03/2024 um 14:46 schrieb Ottavio Caruso:
> I have a file that looks like this:
>
> $ head newsrc-news.eternal-september.org-test
> nl.newsgroups.announce: 1-1329
> free.uk.amateur-radio: 1-15497
> uk.media.radio.misc: 1-456
> uk.radio.amateur: 1-377688,377690,377692,377694-377697,377699,377701-377704
> uk.radio.amateur.moderated: 1-6432
> uk.legal.moderated: 1-378428
> comp.security.ssh: 1-3221
> alt.comp.software.newsreaders: 1-481
> uk.net.news.moderation: 1-64428
> free.uk.legal: 1-275
>
> I want to convert all the last part of the lines from 1-whatever to 1-1
>
> I have tried:
>
> $ sed -i 's/"1-*"/'1-1'/g'  newsrc-news.eternal-september.org-test
>
> and
>
> $ sed -i 's/"1-*"/"1-1"/g'  newsrc-news.eternal-september.org-test
>
> $ sed -i 's/"1-*"/1-1/g'  newsrc-news.eternal-september.org-test
>
> but none of them does the job.
>
> If I do:
>
> $ sed -i 's/1-*/"1-1"/g'  newsrc-news.eternal-september.org-test
>
> then:
>
> $ head  newsrc-news.eternal-september.org-test
> nl.newsgroups.announce: "1-1""1-1""1-1""1-1"329
> free.uk.amateur-radio: "1-1""1-1""1-1""1-1"5497
> uk.media.radio.misc: "1-1""1-1"456
> uk.radio.amateur:
> "1-1""1-1"377688,377690,377692,377694-377697,377699,37770"1-1""1-1"377704
> uk.radio.amateur.moderated: "1-1""1-1"6432
> uk.legal.moderated: "1-1""1-1"378428
> comp.security.ssh: "1-1""1-1"322"1-1""1-1"
> alt.comp.software.newsreaders: "1-1""1-1"48"1-1""1-1"
> uk.net.news.moderation: "1-1""1-1"64428
> free.uk.legal: "1-1""1-1"275
>
>
> which is not what I want.
>
> Any help will be appreciated.
>

For posterity, Grant Taylor on alt.comp.software.thunderbird suggested
this and worked:

$ awk '{print $1, "1-1"}' newsrc-news.eternal-september.org-test >
newsrc-news.eternal-september.org

Sorry for the noise. I never got to learn awk properly.

--
Ottavio Caruso

In article <us9vka$fepq$1@dont-email.me>,
Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> wrote:
>I have a file that looks like this:
>
>$ head newsrc-news.eternal-september.org-test
>nl.newsgroups.announce: 1-1329
>free.uk.amateur-radio: 1-15497
>uk.media.radio.misc: 1-456
>uk.radio.amateur: 1-377688,377690,377692,377694-377697,377699,377701-377704
>uk.radio.amateur.moderated: 1-6432
>uk.legal.moderated: 1-378428
>comp.security.ssh: 1-3221
>alt.comp.software.newsreaders: 1-481
>uk.net.news.moderation: 1-64428
>free.uk.legal: 1-275
>
>I want to convert all the last part of the lines from 1-whatever to 1-1

Two comments:
1) "sed" is almost never the right answer, regardless of what the
question is. AWK can do everything (with maybe one or two obscure
exceptions) that sed can do, and is a lot easier to use.

2) Why not just:

awk 'sub(/1-[0-9]+$/,"1-1");{ print "Line:",$0,"does not fit the expected pattern." > "/dev/stderr" }' yourfile

--
Many (most?) Trump voters voted for him because they thought if they
supported Trump enough, they'd get to *be* Trump.

Similarly, Trump believes that if *he* praises Putin enough, he'll get to *be* Putin.

Am 06/03/2024 um 14:59 schrieb Kenny McCormack:
> In article <us9vka$fepq$1@dont-email.me>,
> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> wrote:
>> I have a file that looks like this:
>>
>> $ head newsrc-news.eternal-september.org-test
>> nl.newsgroups.announce: 1-1329
>> free.uk.amateur-radio: 1-15497
>> uk.media.radio.misc: 1-456
>> uk.radio.amateur: 1-377688,377690,377692,377694-377697,377699,377701-377704
>> uk.radio.amateur.moderated: 1-6432
>> uk.legal.moderated: 1-378428
>> comp.security.ssh: 1-3221
>> alt.comp.software.newsreaders: 1-481
>> uk.net.news.moderation: 1-64428
>> free.uk.legal: 1-275
>>
>> I want to convert all the last part of the lines from 1-whatever to 1-1
>
> Two comments:
> 1) "sed" is almost never the right answer, regardless of what the
> question is. AWK can do everything (with maybe one or two obscure
> exceptions) that sed can do, and is a lot easier to use.
>
> 2) Why not just:
>
> awk 'sub(/1-[0-9]+$/,"1-1");{ print "Line:",$0,"does not fit the expected pattern." > "/dev/stderr" }' yourfile
>

I actually got myself in trouble because I realised this is not what I
really wanted, so I just made a lot of noise for nuffink.

--
Ottavio Caruso

On 3/6/24 08:46, Ottavio Caruso wrote:
> Any help will be appreciated.

Copying my sed version reply from alt.comp.software.thunderbird here for
completeness:

mv newsrc newsrc.backup
sed 's/:.*/: 1-1/' newsrc.backup > newsrc

--
Grant. . . .

In article <usa1ei$hr$3@tncsrv09.home.tnetconsulting.net>,
Grant Taylor <gtaylor@tnetconsulting.net> wrote:
>On 3/6/24 08:46, Ottavio Caruso wrote:
>> Any help will be appreciated.
>
>Copying my sed version reply from alt.comp.software.thunderbird here for
>completeness:
>
>mv newsrc newsrc.backup
>sed 's/:.*/: 1-1/' newsrc.backup > newsrc

sed -i 's/:.*/: 1-1/' newsrc

--
Most Southerners interest in, knowledge of, and participation in politics begins with
and ends with: Screw the blacks. If a guy is onboard with that, he's our guy!

Get them back in chains where they belong!

On 06.03.2024 15:53, Ottavio Caruso wrote:
> Am 06/03/2024 um 14:46 schrieb Ottavio Caruso:
>> I have a file that looks like this:
>>
>> $ head newsrc-news.eternal-september.org-test
>> nl.newsgroups.announce: 1-1329
>> free.uk.amateur-radio: 1-15497
>> uk.media.radio.misc: 1-456
>> uk.radio.amateur:
>> 1-377688,377690,377692,377694-377697,377699,377701-377704
>> uk.radio.amateur.moderated: 1-6432
>> uk.legal.moderated: 1-378428
>> comp.security.ssh: 1-3221
>> alt.comp.software.newsreaders: 1-481
>> uk.net.news.moderation: 1-64428
>> free.uk.legal: 1-275
>>
>> [...]
>>
>> Any help will be appreciated.
>>
>
> For posterity, Grant Taylor on alt.comp.software.thunderbird suggested
> this and worked:
>
>
> $ awk '{print $1, "1-1"}' newsrc-news.eternal-september.org-test >
> newsrc-news.eternal-september.org

In this specific case of regular data you can simplify that to

awk '$2="1-1"' sourcefile > targetfile

Janis

Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:

[...]

> Sorry for the noise. I never got to learn awk properly.

The book

The AWK Programming Language
Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
Addison-Wesley Publishing Company, 1988
ISBN 0-201-07981-X

is one of the most interesting books on programming ever written.
(Along with SICP, HtDP and others.)

Julieta Shem <jshem@yaxenu.org> writes:
> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>
> [...]
>
>> Sorry for the noise. I never got to learn awk properly.
>
> The book
>
> The AWK Programming Language
> Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
> Addison-Wesley Publishing Company, 1988
> ISBN 0-201-07981-X
>
> is one of the most interesting books on programming ever written.
> (Along with SICP, HtDP and others.)

The second edition was published in 2024.

SICP is "Structure and Interpretation of Computer Programs" by Harold
Abelson and Gerald Jay Sussman with Julie Sussman.

HtDP is "How to Design Programs" by Matthias Felleisen, Robert Bruce
Findler, Matthew Flatt, and Shriram Krishnamurthi.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
> I have a file that looks like this:
>
> $ head newsrc-news.eternal-september.org-test
> nl.newsgroups.announce: 1-1329
> free.uk.amateur-radio: 1-15497
> uk.media.radio.misc: 1-456
> uk.radio.amateur: 1-377688,377690,377692,377694-377697,377699,377701-377704
> uk.radio.amateur.moderated: 1-6432
> uk.legal.moderated: 1-378428
> comp.security.ssh: 1-3221
> alt.comp.software.newsreaders: 1-481
> uk.net.news.moderation: 1-64428
> free.uk.legal: 1-275
>
> I want to convert all the last part of the lines from 1-whatever to 1-1
[...]

The numbers are a list of which articles in a newsgroup are marked as
already read (either because you've actually read them, or because you
don't want to see them again).

Changing the list to "1-1", which is equivalent to just "1", means that
you've read article number 1. Depending on the server and the newsgroup,
there may or may not be an article number 1, but marking it as read is
harmless. With "nl.newsgroups.announce: 1-1", your newsreader will show
you all articles in that newsgroup other than article number 1.

But I wonder if what you really want to do is mark *all* articles as
unread, so you can see everything. You can do that by deleting the list
of article numbers.

Of course if you really want to mark article 1 in each newsgroup as read
and all others as unread, that's fine. But marking all articles as
unread is easier and perhaps more likely to be what you want.

sed 's/:.*/:/' is likely to do what you want. In my experience it
doesn't matter whether there's a space after the ':'. I'm presume the
format is documented somewhere.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

On 06.03.2024 22:50, Keith Thompson wrote:
> Julieta Shem <jshem@yaxenu.org> writes:
>>
>> The book
>>
>> The AWK Programming Language
>> Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
>> Addison-Wesley Publishing Company, 1988
>> ISBN 0-201-07981-X
>>
>> is one of the most interesting books on programming ever written.
>
> The second edition was published in 2024.

This is a very notable fact given that the first edition was from 1988!

Janis

On 3/6/24 09:20, Kenny McCormack wrote:
> sed -i 's/:.*/: 1-1/' newsrc

Agreed /if/ the sed that the OP is using supports `-i`.

My day job has me working across multiple platforms and try to do things
more consistently across the platforms.

--
Grant. . . .

On 3/6/24 13:40, Janis Papanagnou wrote:
> In this specific case of regular data you can simplify that to
>
> awk '$2="1-1"' sourcefile > targetfile

Interesting.

I don't know that I've ever seen (re)defining a field value as part of
the script.

I'll have to file that one away.

Today I learned.

Thank you.

--
Grant. . . .

On 07.03.2024 02:34, Grant Taylor wrote:
> On 3/6/24 13:40, Janis Papanagnou wrote:
>> In this specific case of regular data you can simplify that to
>>
>> awk '$2="1-1"' sourcefile > targetfile
>
> Interesting.
>
> I don't know that I've ever seen (re)defining a field value as part of
> the script.

Assigning to a field is possible but you should be aware that the
fields in $0 will become reorganized then... (mind the blank spaces)

awk '$2="NEW"' <<EOT
abc defg ghi
jk lm no pq
EOT

Output:
abc NEW ghi
jk NEW no pq

You see that there's then (per default) only single delimiting
spaces left. You can change that by delimiter OFS, e.g. OFS="\t"
would place TABs in between (but would not preserve the original
spacing).

If you'd want to retain the previous spaces it would require some
other (not so trivial) handling.

Janis

> [...]

Am 06/03/2024 um 21:26 schrieb Julieta Shem:
> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>
> [...]
>
>> Sorry for the noise. I never got to learn awk properly.
>
> The book
>
> The AWK Programming Language
> Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
> Addison-Wesley Publishing Company, 1988
> ISBN 0-201-07981-X
>
> is one of the most interesting books on programming ever written.
> (Along with SICP, HtDP and others.)

Smartass.

--
Ottavio Caruso

Am 06/03/2024 um 21:50 schrieb Keith Thompson:
> Julieta Shem <jshem@yaxenu.org> writes:
>> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>>
>> [...]
>>
>>> Sorry for the noise. I never got to learn awk properly.
>>
>> The book
>>
>> The AWK Programming Language
>> Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
>> Addison-Wesley Publishing Company, 1988
>> ISBN 0-201-07981-X
>>
>> is one of the most interesting books on programming ever written.
>> (Along with SICP, HtDP and others.)
>
> The second edition was published in 2024.
>
> SICP is "Structure and Interpretation of Computer Programs" by Harold
> Abelson and Gerald Jay Sussman with Julie Sussman.
>
> HtDP is "How to Design Programs" by Matthias Felleisen, Robert Bruce
> Findler, Matthew Flatt, and Shriram Krishnamurthi.
>

For fucks sake, I know what awk is. I just never bothered learning it.

Just because you see a foreign name, you all expect we live in a cave.

--
Ottavio Caruso

Am 07/03/2024 um 01:32 schrieb Grant Taylor:
> On 3/6/24 09:20, Kenny McCormack wrote:
>> sed -i 's/:.*/: 1-1/' newsrc
>
> Agreed /if/ the sed that the OP is using supports `-i`.
>
> My day job has me working across multiple platforms and try to do things
> more consistently across the platforms.
>
>
>

Thanks Grant. I am unsubscribing from this NG, so you won't catch me here.

--
Ottavio Caruso

In article <usc2je$vsku$2@dont-email.me>,
Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> wrote:
....
>For fucks sake, I know what awk is. I just never bothered learning it.

You were responding to Leader Keith. Yes, Keith is an asshole, but he's
our asshole and we love him for it.

>Just because you see a foreign name, you all expect we live in a cave.

Do you even have electricity where you live?

--
Just like Donald Trump today, Jesus Christ had a Messiah complex.

And, in fact, the similarities between the two figures are quite striking.
For example, both have a ragtag band of followers, whose faith cannot be shaken.

Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
> Am 06/03/2024 um 21:50 schrieb Keith Thompson:
>> Julieta Shem <jshem@yaxenu.org> writes:
>>> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>>>
>>> [...]
>>>
>>>> Sorry for the noise. I never got to learn awk properly.
>>>
>>> The book
>>>
>>> The AWK Programming Language
>>> Alfred V. Aho, Brian W. Kernighan, Peter J. Weinberger
>>> Addison-Wesley Publishing Company, 1988
>>> ISBN 0-201-07981-X
>>>
>>> is one of the most interesting books on programming ever written.
>>> (Along with SICP, HtDP and others.)
>> The second edition was published in 2024.
>> SICP is "Structure and Interpretation of Computer Programs" by
>> Harold
>> Abelson and Gerald Jay Sussman with Julie Sussman.
>> HtDP is "How to Design Programs" by Matthias Felleisen, Robert Bruce
>> Findler, Matthew Flatt, and Shriram Krishnamurthi.
>
> For fucks sake, I know what awk is. I just never bothered learning it.
>
> Just because you see a foreign name, you all expect we live in a cave.

What on Earth are you talking about? I didn't even notice your name.
I just expanded on what Julieta Shem wrote, and you somehow managed
to take offense. (I didn't know what HtDP means; I had to look it
up, and then I shared that information with the group.)

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

On 3/6/24 19:54, Janis Papanagnou wrote:
> You see that there's then (per default) only single delimiting spaces
> left.

I think I see what you're saying. I also feel like I must be missing
something obvious, because what you're describing is what I would expect
awk to do.

> You can change that by delimiter OFS, e.g. OFS="\t" would place TABs
> in between (but would not preserve the original spacing).

I've dabbled with OFS, and IFS, a few times as needed. But most of the
time I don't need to.

> If you'd want to retain the previous spaces it would require some other
> (not so trivial) handling.

I can't think of a use case where I would want that and choose to use
awk. -- I'm sure such use cases exist, I'm just ignorant of them.

--
Grant. . . .

Grant Taylor <gtaylor@tnetconsulting.net> writes:
> On 3/6/24 19:54, Janis Papanagnou wrote:
>> You see that there's then (per default) only single delimiting
>> spaces left.
>
> I think I see what you're saying. I also feel like I must be missing
> something obvious, because what you're describing is what I would
> expect awk to do.

I know that's what awk does, but I don't think I would have expected it
if I didn't know about it.

For example:

$ echo 'one two three' | awk '{print}'
one two three
$ echo 'one two three' | awk '{$0 = $0 " four" ; print}'
one two three four
$ echoʜ'one two three' | awk '{$2 = "TWO" ; print}'
one TWO three
$

$0 is the current input line. If you don't change anything, or if you
modify $0 itself, whitespace betweeen fields is preserved. If you
modify any of the fields, $0 is recomputed and whitespace between tokens
is collapsed.

awk *could* have been defined to preserve inter-field whitespace even
when you modify individual fields, and I think I would have found that
more intuitive. (And ideally there would be a way to refer to that
inter-field whitespace.) The fact that modifying a field has the side
effect of messing up $0 seems counterintuitive.

Perhaps the behavior matches your intuition better than it matches mine.

(And perhaps this should be moved to comp.lang.awk if it doesn't die out
soon. Though both sed and awk are both languages in their own right and
tools that can be used from the shell, so I'd argue there's a topicality
overlap.)

[...]

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
[...]
> $ echo 'one two three' | awk '{print}'
> one two three
> $ echo 'one two three' | awk '{$0 = $0 " four" ; print}'
> one two three four
> $ echoʜ'one two three' | awk '{$2 = "TWO" ; print}'
> one TWO three
> $

Please ignore the stray ʜ character. It was supposed to be a space.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

On 3/7/24 18:09, Keith Thompson wrote:
> I know that's what awk does, but I don't think I would have expected
> it if I didn't know about it.

Okay. I think that's a fair observation.

> $0 is the current input line.

Or $0 is the current /record/ in awk parlance.

> If you don't change anything, or if you modify $0 itself, whitespace
> betweeen fields is preserved.

> If you modify any of the fields, $0 is recomputed and whitespace
> between tokens is collapsed.

I don't agree with that.

% echo 'one two three' | awk '{print $0; print $1,$2,$3}'
one two three
one two three

I didn't /modify/ anything and awk does print the fields with different
white space.

> awk *could* have been defined to preserve inter-field whitespace even
> when you modify individual fields,

I question the veracity of that. Specifically when lengthening or
shortening the value of a field. E.g. replacing "two" with "fifteen".
This is particularly germane when you look at $0 as a fixed width
formatted output.

> and I think I would have found that more intuitive.

I don't agree.

> (And ideally there would be a way to refer to that inter-field
> whitespace.)

Remember, awk is meant for working on fields of data in a record. By
default, the fields are delimited by white space characters. I'll say
it this way, awk is meant for working on the non-white space characters.
Or yet another way, awk is not meant for working on white space charters.

> The fact that modifying a field has the side effect of messing up $0
> seems counterintuitive.

Maybe.

But I think it's one that is acceptable for what awk is intended to do.

> Perhaps the behavior matches your intuition better than it matches
> mine.

I sort of feel like you are wanting to / trying to use awk in places
where sed might be better. sed just sees a string of text and is
ignorant of any structure without a carefully crafted RE to provide it.

Conversely awk is quite happy working with an easily identified field
based on the count with field separators of one or more white space
characters.

Consider the output of `netstat -an` wherein you have multiple columns
of IP addresses.

Please find a quick way, preferably that doesn't involve negation
(because what needs to be negated may bey highly dynamic) that lists
inbound SMTP connections on an email server but doesn't list outbound
SMTP connections.

awk makes it trivial to identify and print records that have the SMTP
port in the local IP column, thus ignoring outbound connections with
SMTP in the remote column.

Aside: Yes, I know that ss and the likes have more features for this,
but this is my example and ss is not installed everywhere.

I sort of view awk as somewhat akin to SQL wherein fields in awk are
like columns in SQL.

I'd be more than a little bit surprised to find an SQL interface that
preserved white space /between/ columns. -- Many will do it /within/
columns.

awk makes it trivial to take field oriented output from commands and
apply some logic / parsing / action on specific fields in records.

> (And perhaps this should be moved to comp.lang.awk if it doesn't die
> out soon.

comp.lang.awk added and followup pointed there.

> Though both sed and awk are both languages in their own right
> and tools that can be used from the shell, so I'd argue there's a
> topicality overlap.)

;-)

--
Grant. . . .

On Thu, 07 Mar 2024 14:32:58 -0800, Keith Thompson
<Keith.S.Thompson+u@gmail.com> wrote in
<87jzmdoep1.fsf@nosuchdomain.example.com>:

> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>> Am 06/03/2024 um 21:50 schrieb Keith Thompson:
>>> Julieta Shem <jshem@yaxenu.org> writes:
>>>> Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> writes:
>>>>
>>>> [...]
>>>>
>>>>> Sorry for the noise. I never got to learn awk properly.
>>>>
>>>> The book
>>>>
>>>> The AWK Programming Language Alfred V. Aho, Brian W. Kernighan,
>>>> Peter J. Weinberger Addison-Wesley Publishing Company, 1988 ISBN
>>>> 0-201-07981-X
>>>>
>>>> is one of the most interesting books on programming ever written.
>>>> (Along with SICP, HtDP and others.)
>>> The second edition was published in 2024.
>>> SICP is "Structure and Interpretation of Computer Programs" by Harold
>>> Abelson and Gerald Jay Sussman with Julie Sussman.
>>> HtDP is "How to Design Programs" by Matthias Felleisen, Robert Bruce
>>> Findler, Matthew Flatt, and Shriram Krishnamurthi.
>>
>> For fucks sake, I know what awk is. I just never bothered learning it.
>>
>> Just because you see a foreign name, you all expect we live in a cave.
>
> What on Earth are you talking about? I didn't even notice your name.
> I just expanded on what Julieta Shem wrote, and you somehow managed to
> take offense. (I didn't know what HtDP means; I had to look it up, and
> then I shared that information with the group.)

Someone having a bad day?

Anyway, thank you for the heads-up that a new edition
of the AWK book was out. I bought it on Kindle -- would
have bought hardcopy, but Amazon seems to only have it
in paperback (and Kindle).

(Coincidentally, I have a question about shell providers,
but will post that separately.)

--
-v

In article <usdufk$19m29$1@dont-email.me>, vallor <vallor@cultnix.org> wrote:
....
>Someone having a bad day?

Yes, but with Keith, every day is a bad day.

You get used to it.

--
'Islamaphobia' is a term created by fascists and used by cowards to manipulate morons.

- Author unknown, quoted by Sam Harris -