Question: Issues that aren’t really major issues but are still issues

[xexyl]

Due to the fact that we have another issue that has had a number of OT comments I think it might be good to have a new mostly OT thread here rather than clutter the one in the other repo more or the issue for jprint.

I had the thought of suggesting you reopen the other one but there's a comment there I don't want to get lost that I hope you can finish replying to (you were doing it in parts) when things are less busy here. I also wanted to see if anything in particular occurs if one uses the same name (I rather doubt it will but it popped into my head anyway).

Feel free to assign this to me even though it's not technically an issue that has to be resolved.

[xexyl]

As I don't feel up to working on the tool (too tired or something along those lines though I hope to a bit later on today[0]) I do have some OT things to bring up which I'll do in additional comments.

[0] I do have a zoom meeting today and I'll be done working on the repo for the day prior to this, whatever I got done, whether anything beyond the two open pull requests or not.

[xexyl]

Tolkien books

I know I told you about the book that Christopher blessed before his tragic death that you got and started to read (I still haven't had a chance to ... :( ) but I have also brought up some others that I wonder if you've got, books that are delightful.

• The Adventures of Tom Bombadil. Did you know that the first writing of Tom he was captured by Old Man Willow? He was actually invented in Oxford Magazine I think in 1933 - totally unrelated to the Legendarium (that didn't exist as we know it at the time if at all). But there are other stories and etymologies of things too.
• The Letters of JRR Tolkien (this one is brilliant: has a lot of insight from him and answering questions about Silmarillion, Hobbit and The Lord of the Rings - amongst many other things totally unrelated to the Legendarium)
• The Art Of The Lord Of The Rings (by Tolkien). BTW: if you didn't know in the 50th anniversary of LR the leaves of the Book of Mazarbul that he wanted published initially but could not be due to costs and other things was put in the book. It's a one book volume of the three parts (one volume which is what he wanted in the first place as it's not technically a trilogy - he wrote about that in the Letters actually).
• The Art Of The Hobbit (by Tolkien also)
• The History of the Hobbit (this is one I did not finish yet ... I always go back to other books by him but I will get to it eventually I hope)
• You can read the first edition of Hobbit (you know from The Return of the Shadow, HoMe VI, what the significant difference is - which is also talked about in the Letters quite a bit - but you can read it in full): The Hobbit facsimile first edition.
• JRR Tolkien Artist & Illustrator
• The Letters of Father Christmas

There are others I know about that are great but that's a nice list if you didn't know about them. I have a book with pull outs of the maps but I can't access it .. they or it (might be one for Hobbit too - don't recall) are behind other books as I have limited space :( (not the only kinds of books that are inaccessible).

Enjoy!

[xexyl]

Here's a fun one I just wrote ...

/* programmer's party simulator */
#include <stdio.h>
#include <unistd.h>
void drink() { drink(); }
void party()
{
    /*
     * get pissed as a fart and do something
     * exciting, I'm sure... (where exciting
     * means stupid)
     */
    drink();
}
/* programmer's social function */
void code() { printf("Go away! I'm programming!\n"); sleep(1); code(); }
int main()
{
    /* skip the party: just go home and write code! */
    goto home;
    party();

    home: code();
}

Not that coding is the same as programming as such ...

[xexyl]

So... I discovered an interesting problem with make test but not running the test script in question directly.

Check this:

make test
...
If you are curious, you may examine the newly created compressed tarball
by running the following command:

    /opt/local/libexec/gnubin/tar -Jtvf test_ioccc/test_work/entry.test-1.1689530054.txz

As you entered an IOCCC contest ID of 'test', the compressed tarball
that was just formed CANNOT be used as an IOCCC entry. Please
do NOT email the Judges your entry!

yes: standard output: Broken pipe

It only happens when running make test: from the top level directory but also the test directory. I'm not sure why this is.

The question is do you want me to open an issue with this problem? Of course low priority right now probably but it's kind of annoying and I feel like it shouldn't be there. I'd guess you agree.

UPDATE 0

One way to fix it would be to add a -y option that says 'yes' to everything. That might be useful to some people anyway. Want me to add such a feature ?

[xexyl]

.. and I see another problem with it - display - but probably insignificant given where it is:

Is the above list a correct list of files in your entry? [yn]: 
drwxr-xr-x  0 501    20          0 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/
-rw-r--r--  0 501    20       1856 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/Makefile
-rw-r--r--  0 501    20          4 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/extra2
-rw-r--r--  0 501    20       3085 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/.auth.json
-rw-r--r--  0 501    20       2815 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/foo
-rw-r--r--  0 501    20         61 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/prog.c
-rw-r--r--  0 501    20       7623 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/remarks.md
-rw-r--r--  0 501    20       5235 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/bar
-rw-r--r--  0 501    20       1590 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/.info.json
-rw-r--r--  0 501    20          4 Jul 16 17:54 12345678-1234-4321-abcd-1234567890ab-2/extra1
    https://www.ioccc.org/index.html#news


... the output above is the listing of the compressed tarball.

Notice where the URL is.

I guess that that's just the way the script is and it's not a problem - since it ends up having to not prompt (exactly why we need the yes).

[lcn2]

So... I discovered an interesting problem with make test but not running the test script in question directly.

Check this:

make test
...
If you are curious, you may examine the newly created compressed tarball
by running the following command:

    /opt/local/libexec/gnubin/tar -Jtvf test_ioccc/test_work/entry.test-1.1689530054.txz

As you entered an IOCCC contest ID of 'test', the compressed tarball
that was just formed CANNOT be used as an IOCCC entry. Please
do NOT email the Judges your entry!

yes: standard output: Broken pipe

It only happens when running make test: from the top level directory but also the test directory. I'm not sure why this is.

The question is do you want me to open an issue with this problem? Of course low priority right now probably but it's kind of annoying and I feel like it shouldn't be there. I'd guess you agree.

Yes, we agree.

UPDATE 0

One way to fix it would be to add a -y option that says 'yes' to everything. That might be useful to some people anyway. Want me to add such a feature ?

Yes, please.

[xexyl]

So... I discovered an interesting problem with make test but not running the test script in question directly.
Check this:

make test
...
If you are curious, you may examine the newly created compressed tarball
by running the following command:

    /opt/local/libexec/gnubin/tar -Jtvf test_ioccc/test_work/entry.test-1.1689530054.txz

As you entered an IOCCC contest ID of 'test', the compressed tarball
that was just formed CANNOT be used as an IOCCC entry. Please
do NOT email the Judges your entry!

yes: standard output: Broken pipe

It only happens when running make test: from the top level directory but also the test directory. I'm not sure why this is.
The question is do you want me to open an issue with this problem? Of course low priority right now probably but it's kind of annoying and I feel like it shouldn't be there. I'd guess you agree.

Yes, we agree.

UPDATE 0

One way to fix it would be to add a -y option that says 'yes' to everything. That might be useful to some people anyway. Want me to add such a feature ?

Yes, please.

It might as I think solve the problem in the script in which case there might not be a need for an issue being opened. I opened this directly so that I'll see the email - tomorrow. Too tired to do it today I'm afraid and I'm hoping to be leaving (laptop) for the day soon.

... of course it brings up a question of is there a problem with the script that should be isolated? It might or might not have a problem. Not sure. Is it worth trying to determine the cause? I think probably not unless the -y option doesn't solve it.

[xexyl]

So... I discovered an interesting problem with make test but not running the test script in question directly.
Check this:

make test
...
If you are curious, you may examine the newly created compressed tarball
by running the following command:

    /opt/local/libexec/gnubin/tar -Jtvf test_ioccc/test_work/entry.test-1.1689530054.txz

As you entered an IOCCC contest ID of 'test', the compressed tarball
that was just formed CANNOT be used as an IOCCC entry. Please
do NOT email the Judges your entry!

yes: standard output: Broken pipe

It only happens when running make test: from the top level directory but also the test directory. I'm not sure why this is.
The question is do you want me to open an issue with this problem? Of course low priority right now probably but it's kind of annoying and I feel like it shouldn't be there. I'd guess you agree.

Yes, we agree.

UPDATE 0

One way to fix it would be to add a -y option that says 'yes' to everything. That might be useful to some people anyway. Want me to add such a feature ?

Yes, please.

It might as I think solve the problem in the script in which case there might not be a need for an issue being opened. I opened this directly so that I'll see the email - tomorrow. Too tired to do it today I'm afraid and I'm hoping to be leaving (laptop) for the day soon.

... of course it brings up a question of is there a problem with the script that should be isolated? It might or might not have a problem. Not sure. Is it worth trying to determine the cause? I think probably not unless the -y option doesn't solve it.

I am thinking it might be a good idea to make an issue out of this and make it so that it's assigned to me. I am sure this will solve the problem but the other things are higher priority, right? If so do you think I should open an issue so I remember to do it later ?

[lcn2]

I am thinking it might be a good idea to make an issue out of this and make it so that it's assigned to me. I am sure this will solve the problem but the other things are higher priority, right? If so do you think I should open an issue so I remember to do it later ?

Go ahead and open an new issue for this. That was it can be noted while other matters are prioritized.

[xexyl]

I am thinking it might be a good idea to make an issue out of this and make it so that it's assigned to me. I am sure this will solve the problem but the other things are higher priority, right? If so do you think I should open an issue so I remember to do it later ?

Go ahead and open an new issue for this. That was it can be noted while other matters are prioritized.

I will do that tomorrow.

I am about to have brownies that were pulled out of the oven about ten minutes ago.

I just needed to take it easy today. I hope that tomorrow is a more productive day.

Have a great night!

[xexyl]

I am thinking it might be a good idea to make an issue out of this and make it so that it's assigned to me. I am sure this will solve the problem but the other things are higher priority, right? If so do you think I should open an issue so I remember to do it later ?

Go ahead and open an new issue for this. That was it can be noted while other matters are prioritized.

I will do that tomorrow.

I am about to have brownies that were pulled out of the oven about ten minutes ago.

I just needed to take it easy today. I hope that tomorrow is a more productive day.

Have a great night!

Fixed it instead. See commit c776f09.

Going to try and rest now though my body is telling me that won't last for long .. but possibly won't work on the other issues for a bit if not a while later. I do hope to work on it a bit today though but we'll see if I'm up to it. Hope you're sleeping well!