Closed SirWumpus closed 2 months ago
Updating manifest now (.entry.json
stage) for 1991, 1992, 1993 and 2015. However there still is the question of what to do about 2004 and 2005: as they have a configure
script and Makefile templates. How do you want to deal with this, Landon? I can't add these files to finish this issue until this is decided.
.. and I'll be afk soon: I think. But if I do not finish the manifest before then I will do so when I'm back. That will solve the problem from the other day. Hopefully today I can review the changes you made several hours back too: though I think that's probably pretty good. If I get that done then I can finally (!! - unless we decide upon 2004 and 2005: seems good to finish an issue first) get back to formatting fixes up through 1995 I think it was. After that I can then go beyond that and move towards 2020.
Just about done .. then will sync to server and take a quick look. Don't expect any problems. A couple other entries had an entry_text changed: changed deobfuscated to unobfuscated and now they're all the same text. Seemed a better word: if only slightly.
Question for you @SirWumpus.
In 2015/howe you wrote a summary for support files. You left out a summary for avgtime.sh though. Do you wish to provide one? The entry_text in the manifest has: support script
.. but that could be improved too. I could come up with something, maybe, but I want to offer you the opportunity first.
Commit https://github.com/ioccc-src/temp-test-ioccc/pull/2548/commits/92139c55d75dd60e7ddc2e6cf76e446d561285f3 updates the 1991-1993 and 2015 entries plus the manifest for a couple other entries (as the entry_text was made the same wording - unobfuscated).
What remains for this issue is 2004 and 2005 entries but I don't know how we want to have those organised. Please advise, Landon, when you can, so that we can hopefully get this issue resolved soon.
You left out a summary for avgtime.sh
Was only intended to help test basic performance of npdif
(mine) verses the system diff(1)
(typically GNU). So feel free to apply your wit "in a timely manner".
You left out a summary for avgtime.sh
Was only intended to help test basic performance of
npdif
(mine) verses the systemdiff(1)
(typically GNU). So feel free to apply your wit "in a timely manner".
Thanks .. and great pun! I put in the manifest report average time running a command N times
and in the README.md file Run time(1) N times on a command to determine average runtime.
I think that works well enough. Unless you think something better can be contrived?
Oh .. I just remembered the ideas you had about text to have about for a challenge etc. I did not add that to the entries I moved the alt code in. I will be finishing the four up today (except for the one with the pending question/concern) - perhaps you'd like to do this? Otherwise I can look at it tomorrow. I just feel like that issue is taking time away from this issue and it's taking longer than I was hoping :(
the ideas you had about text to have about for a challenge etc
Say woot?
the ideas you had about text to have about for a challenge etc
Say woot?
What Landon committed. But it I wasn't clear it's because I am very tired. Can try again tomorrow.
I got hibachi done .. well minus the manifest. That will be fun!
I'll also have to do the other one too. Might as well finish that before doing the manifest.
An odd problem though with hibachi: it seems only the unobfuscated version is working. But perhaps that's due to socket options that were not used (just a guess based on my experience with sockets). Will have to try it in a bit.
Working on manifest for both .. if all good then this issue can be closed (I think) - once something is decided in another issue (which is a simple fix once it's decided).
The configure
script for hibachi was quite annoying but I got it. The mynx one has a configure for both but they're not used: I only added them because they originally were submitted. (Not my doing of not using the script .. if I had my way the other one wouldn't either though once this is resolved that will likely change: a unique thing is very much a good thing).
Commit https://github.com/ioccc-src/temp-test-ioccc/pull/2551/commits/0d65af1b2bfd66ecc9120125dbb4dc1accd8d0e1 added 2004/hibachi and 2005/mynx. I have not looked at the manifest results as I haven't got to those years yet but I suspect that there won't have to be any real changes if any at all (unless it is decided that the order of files should be changed).
This means that this issue is almost resolved - just the one thing we've been discussing. But I am off for the day. Back tomorrow!
Looking at commit 2e2ae5f132f2e4f7f60ad8c275038c8db506c7ec now but also made a change in the heading name used (added a ':'). When those files are rebuilt (quick_readme2index is taking longer as I used sgit and should have done on all rather than just .md files) I'll sync to server and then look at those entries - or at least those of the years I have already checked. After that I'll see if I can figure out the problematic file and entry_text for the one entry here. If I can then I think this issue can be closed as complete. Otherwise we will have to work that out.
It would be nice if this can be marked complete as I could then move forward on the other issue in important ways.
I also have to update the FAQ today but that shouldn't take much time I think.
What else I'll do today I really don't know. I'm pretty worn out but it's also early enough where it's quite possible I'll be doing more.
Thank you @SirWumpus and @xexyl
Thank you @SirWumpus and @xexyl
You are most welcome .. though it's not completely resolved yet. Nonetheless it's about to be. I'll make a commit very soon: within minutes at most.
Commit 88d8a302b4eec834bee4272d5f28b374ee65c6bf should be it!
Now (or next time I look at the repo .. not sure how much more I'll do here today) I can look at the 'look and feel' issue again.
I was reviewing how my past entries currently appear in the updated site.
All my winning entries are on GitHub, have spoilers, some have been cleaned up to C89 versions (ae, ag). All of them should work. Much of the documentation has been converted to Markdown (not the .hint files). Not sure if you want to reference these repositories, copy the formatted documentation, etc.
Anyway I provide these links to the material: