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

[lcn2]

Because some issues are not a real major issue, which is an issue.

• <<=== click this box
• <<=== or click this
• <<=== not an issue

[lcn2]

We worked in a family member health issue for the last 48 hours.

We hope to address questions posed in issue #13 tomorrow, assuming you need us to answer them by tomorrow (else update them accordingly).

[xexyl]

Because some issues are not a real major issue, which is an issue.

• <<=== click this box
• <<=== or click this
• <<=== not an issue

Thanks for the laugh!

[xexyl]

We worked in a family member health issue for the last 48 hours.

We hope to address questions posed in issue #13 tomorrow, assuming you need us to answer them by tomorrow (else update them accordingly).

Best wishes!

I have a kind of busy day today but I am hoping to look at the issue more soon.

I have one thought that might help but even so some of the comments if nothing else need replies (for discussion).

Thanks and no worries on my behalf! Health comes first always.

[xexyl]

I have a great idea for the Makefiles: a new control variable for the test suites.

I did it already in jparse but haven't committed yet: I have to take care of other things first.

Anyway I will also do it here and the dbg and dyn_array repos: it's VERBOSITY and default is 0 but it allows one to do something like:

make VERBOSITY=1 test

so one can more easily run the tests (and bug report for that matter if I added such an option which might not be the case as we always want it very verbose) with the Makefile and so not having to figure out the right command line to do so.

I have changes in jparse that can't be committed yet but when back at the laptop I will commit the things that can and then sync over.

Usually one will not want to change the value of the variable but during testing it might be good. What's more is that many times verbosity would have been useful for the test workflow so we can now do that too.

I have to go through photos from the past couple days, today, and I am planning on making courgette (or if you prefer zucchini) bread but otherwise until sometime early afternoon I hope to work on the repos.

[xexyl]

FYI: it is quite likely that tomorrow I won't be able to spend as much time working on these things. I've not been able to get some other things done that need to be taken care of. They could wait but I don't want to get too behind.

It might be I still get some done but I'm not sure how much. We shall see. Anyway I'm done for the day here and at the other repos too.

Hope the medical situations are going okay or will be soon!

[xexyl]

My mum is in hospital right now .. just emergency at this point. Hypertension and vertigo. She was coherent. They've taken a blood draw (no results yet) and they have her on IV for hydration.

But this has taken extra time away. I did make a few fixes in jstrdecode (minor) and I was going to sync to mkiocccentry repo along with other repos that might not be synced but the above happened and so I'm unable to do that now. I have to go take care of other things. If I don't get to this today I'll do it tomorrow. Left some comments in the thread about decoding bugs but that's possibly all I will do today. Sorry for the delays!

[lcn2]

My mum is in hospital right now .. just emergency at this point. Hypertension and vertigo. She was coherent. They've taken a blood draw (no results yet) and they have her on IV for hydration.

But this has taken extra time away. I did make a few fixes in jstrdecode (minor) and I was going to sync to mkiocccentry repo along with other repos that might not be synced but the above happened and so I'm unable to do that now. I have to go take care of other things. If I don't get to this today I'll do it tomorrow. Left some comments in the thread about decoding bugs but that's possibly all I will do today. Sorry for the delays!

Sad "turn of events", as the expression goes.

Please take care of yourself and help her as needed.

Please present my "best compliments", as the 18th century expression went, to your mom.

[xexyl]

My mum is in hospital right now .. just emergency at this point. Hypertension and vertigo. She was coherent. They've taken a blood draw (no results yet) and they have her on IV for hydration.

But this has taken extra time away. I did make a few fixes in jstrdecode (minor) and I was going to sync to mkiocccentry repo along with other repos that might not be synced but the above happened and so I'm unable to do that now. I have to go take care of other things. If I don't get to this today I'll do it tomorrow. Left some comments in the thread about decoding bugs but that's possibly all I will do today. Sorry for the delays!

Sad "turn of events", as the expression goes.

Please take care of yourself and help her as needed.

Please present my "best compliments", as the 18th century expression went, to your mom.

She says thank you!

She's doing a lot better.

Sometimes she has a problem with dehydration. This has happened before but it didn't dawn on me until she was already there.

And that's what they determined too.

[xexyl]

QUESTION - is this correct behaviour of jstrencode ?

Is this correct?

$ jstrencode -Qe '\"foo"'
\\\"foo

[lcn2]

QUESTION - is this correct behaviour of jstrencode ?

Is this correct?

$ jstrencode -Qe '\"foo"'
\\\"foo

No, it is not correct. The trailing double quote should NOT have been removed!

[xexyl]

QUESTION - is this correct behaviour of jstrencode ?

Is this correct?

$ jstrencode -Qe '"foo"'

\"foo

No, it is not correct. The trailing double quote should NOT have been removed!

So I thought.

I can look at it tomorrow unless you want to take care of it.

[lcn2]

QUESTION - is this correct behaviour of jstrencode ?

Is this correct?

$ jstrencode -Qe '"foo"'

"foo

No, it is not correct. The trailing double quote should NOT have been removed!

So I thought.

I can look at it tomorrow unless you want to take care of it.

This issue has been fixed in PR #18

The form that PR has been applied to the mkiocccentry repo via commit 4d60badafca319f126e31b72165c473348b51055

[xexyl]

QUESTION - is this correct behaviour of jstrencode ?

Is this correct?

$ jstrencode -Qe '"foo"'

"foo

No, it is not correct. The trailing double quote should NOT have been removed!

So I thought.

I can look at it tomorrow unless you want to take care of it.

This issue has been fixed in PR #18

The form that PR has been applied to the mkiocccentry repo via commit 4d60badafca319f126e31b72165c473348b51055

Thank you! Well done!

[xexyl]

[xexyl]

I knew you would be amused as I know you can also read upside down and sideways and diagonally and mirrored and all the combinations.

I was looking for a picture of a hoarding (or if you prefer billboard) that could be easily doctored for another meme I wanted to make (based on a joke that popped into my head last night or so) and then I saw this.

It does remind me of a computer shop that used to be here. The owner deliberately put the sign upside down to draw attention (it worked of course but then most people probably couldn't read it easily or at all). But it made me laugh.

I don't know if this one is deliberate or not but something tells me that it was a mistake.

[xexyl]

As for the decoding bug I really don't know what to do about it. I have been pondering trying to use the decoder you linked to before. It would have to be modified a bit and I agree with your idea about putting it into its own file. It is a real shame but if it works maybe it would be good to do at least for now.

But it might be good to do some research and study and experimenting with the problem to try and get it to work.

Perhaps the next step we should take is to make a test directory with minimal code with the UTF-8 to decode hard coded so we can more easily test it.

I think I will do that and hopefully tomorrow. But if you want to experiment with it please do so.

But with that being said I need sleep. Good night!

[xexyl]

Oh one more thing. I believe that you were friends with Paul Erdős which is why I am sharing this with you. I know one of the judges was and pretty sure it was you. Anyway:

https://www.muckrock.com/news/archives/2015/jul/21/nothing-indicate-nothing-indicate-subject-had-any-/

And good night now.

[lcn2]

Oh one more thing. I believe that you were friends with Paul Erdős which is why I am sharing this with you. I know one of the judges was and pretty sure it was you. Anyway:

https://www.muckrock.com/news/archives/2015/jul/21/nothing-indicate-nothing-indicate-subject-had-any-/

And good night now.

Erdös said that both "Joe" (his way referring to the Soviet Union Government - Joe as in "Joseph Stalin") and "Sam" (his was or referring to the US Government - Sam as in "Uncle Sam") were both interested in him. He was happy to talk about math and did so in the west .. but avoided the Soviet Union.

[xexyl]

Oh one more thing. I believe that you were friends with Paul Erdős which is why I am sharing this with you. I know one of the judges was and pretty sure it was you. Anyway:

https://www.muckrock.com/news/archives/2015/jul/21/nothing-indicate-nothing-indicate-subject-had-any-/

And good night now.

Erdös said that both "Joe" (his way referring to the Soviet Union Government - Joe as in "Joseph Stalin") and "Sam" (his was or referring to the US Government - Sam as in "Uncle Sam") were both interested in him. He was happy to talk about math and did so in the west .. but avoided the Soviet Union.

Okay so was it an umlaut or what I copy pasted?

As for Iosef (as I think his birth name spelling was) Stalin I won't even get started on.

The other one I won't get into either but for different reasons.

I am not in the least bit surprised he avoided the Soviet Union in discussion but it's interesting, all parts.

Thanks for the story!

I hope to start looking at the decoding issue soon but I have other things I have to do today too.

In the meantime I do have to go for now.

[lcn2]

Okay so was it an umlaut or what I copy pasted?

Erdös is an Hungarian name, and he spelled it with a ö.

We knew Erdös well, and we did some mathematics together. There is even a Erdös-Noll conjecture.

[xexyl]

Okay so was it an umlaut or what I copy pasted?

Erdös is an Hungarian name, and he spelled it with a ö.

I knew the former (though not well) but I have seen both with an umlaut and the other diacritic (which I am not sure what it even is). So it's the umlaut. Thanks.

We knew Erdös well, and we did some mathematics together. There is even a Erdös-Noll conjecture.

The last part sounds lovely! I guess you wrote about it together?

[xexyl]

Here's a great one for you .. I was about to go back to sleep. I was in the middle of a word when this happened. Fortunately I was fast enough to grab this screenshot. This is the best one I have seen yet and that's saying a lot.

[xexyl]

On bats:

--

The first known use of bats was on the Cal State University networks
$TALK chat program. The author of the above poem is unknown. (And of course, the original poem did not contain web links.)

--

I read that quite a while back (maybe years ago but not sure). Anyway do you refer to talkd ? I guess that's what you mean. I used to really enjoy that one. A relic of the past as they say.

[lcn2]

On bats:

--

The first known use of bats was on the Cal State University networks
$TALK chat program. The author of the above poem is unknown. (And of course, the original poem did not contain web links.)

--

I read that quite a while back (maybe years ago but not sure). Anyway do you refer to talkd ? I guess that's what you mean. I used to really enjoy that one. A relic of the past as they say.

Yes.

[xexyl]

On bats:

The first known use of bats was on the Cal State University networks
$TALK chat program. The author of the above poem is unknown. (And of course, the original poem did not contain web links.)

I read that quite a while back (maybe years ago but not sure). Anyway do you refer to talkd ? I guess that's what you mean. I used to really enjoy that one. A relic of the past as they say.

Yes.

Thanks. Why do you do it like $TALK though? I have this vague memory but I'm not sure ..

BTW I found some typos, one of which you might want to fix and the other maybe too :-)

First: Is it a bat! Here are some examples: but i think you mean It is a bat! :-)

The second one is in the poem the word 'i' is not capitalised.

[xexyl]

BTW:

HAPPY BIRTHDAY TO YOU,
HAPPY BIRTHDAY TO YOU,
HAPPY BIRTHDAY DEAR BILBO BAGGINS,
HAPPY BIRTHDAY TO YOU!

and ..

HAPPY BIRTHDAY TO YOU,
HAPPY BIRTHDAY TO YOU,
HAPPY BIRTHDAY DEAR FRODO BAGGINS,
HAPPY BIRTHDAY TO YOU!

and ...

HAPPY HOBBIT DAY TO YOU!

---

I'm not sure what I'll do today but I think I might take a break and just read something .. not sure if that's LR or The Hobbit itself but I might very well do that .. along with other things of course.

[xexyl]

[xexyl]

The reference to an apple being in every Apple computer is part of a hilarious episode of The IT Crowd. Well they all are but this is the first one I saw and so I went back and watched the earlier ones and all the ones after it too. They didn't say it was a hoax/scam but I added that because of Jobs' behaviour and treatment of others.

[xexyl]

FYI: with commit f29677f I added a fun file jparse.json which holds some information about this repo including the primary tools. Why?

I would say 'Because!' but the real reason is some other projects have something like this AND because this is a JSON parser so it seems fun. In the process I discovered some typos in comments in the README.md file and some of the tools.

I've not synced this to the other repo and I won't today ... going to try and work on some other things that I have not (well I did somewhat but I did not go as much as I could have). Maybe. I will also be getting food sometime soon too so I probably won't get much more done with that.

Something else came up which has unfortunately messed up part of this day but that's another matter entirely.

[lcn2]

Alternatively it could use the JSON parser to validate it as a string. I added an option for this. On the other hand it might be easier to do the way you suggest as it would just be a swap of meaning of -s. I wonder.

As there is no -s flags for jstrencode(1) and jstrdecode(1) there is nothing to swap. :-) At lease for version 2.0.2.

Right. I'm talking about the newer version. It'll be easier this way I think.

But we don't need a -s flag. The ONLY thing jstrencode(1) and jstrdecode(1) operate on are strings.

[xexyl]

Alternatively it could use the JSON parser to validate it as a string. I added an option for this. On the other hand it might be easier to do the way you suggest as it would just be a swap of meaning of -s. I wonder.

As there is no -s flags for jstrencode(1) and jstrdecode(1) there is nothing to swap. :-) At lease for version 2.0.2.

Right. I'm talking about the newer version. It'll be easier this way I think.

But we don't need a -s flag. The ONLY thing jstrencode(1) and jstrdecode(1) operate on are strings.

Indeed. But the new feature of a previous commit can help make it so that -s can become -d (I think). That's what I mean.

[lcn2]

Alternatively it could use the JSON parser to validate it as a string.

But that's the reason for jstrencode(1) and jstrdecode(1) activate the internal functions related to string processing within the JSON parser.

Validating JSON stuff like true and { "curds" : 5 } and such as what jparse(1) does.

The jstrencode(1) and jstrdecode(1) just operate in strings.

[xexyl]

Alternatively it could use the JSON parser to validate it as a string.

But that's the reason for jstrencode(1) and jstrdecode(1) activate the internal functions related to string processing within the JSON parser.

Validating JSON stuff like true and { "curds" : 5 } and such as what jparse(1) does.

The jstrencode(1) and jstrdecode(1) just operate in strings.

Yes. It was just a thought I was pondering.

[lcn2]

If -d was added to jstrdecode(1) to:

    -d	do not require a leading and trailing double quote (def: do)

BTW: The letter -d can be something else. We just picked d because of the d in "double quote".

Is there a function for -d in jstredcode(1)?

[xexyl]

If -d was added to jstrdecode(1) to:

    -d	do not require a leading and trailing double quote (def: do)

BTW: The letter -d can be something else. We just picked d because of the d in "double quote".

Is there a function for -d in jstredcode(1)?

As of earlier today there is. I think I have swapped it okay .. have to do a few tests first.

[lcn2]

Taking a Greenland 🇬🇱 nap before moving on to Canada 🇨🇦.

[xexyl]

I also added (not committed yet) a simplified interface for parse_json() that doesn't require a filename. It uses parse_json() though. This can be useful for those who want to just parse a string ... though right now it's easy enough to do already. That being said it would be better if we could have a better error message. I won't worry about this change today .. probably.

[xexyl]

Taking a Greenland 🇬🇱 nap before moving on to Canada 🇨🇦.

Don't get too green!

[xexyl]

The new option -d is going to be added soon ... and the -s is gone. Just doing make test now.

Given the time I'll have to look at the other things you found wrong another time, probably tomorrow and not today.

[xexyl]

Done .. and synced to mkiocccentry. Did not update the minimum version in the website tools as it shouldn't matter. I'll look at the other possible issues you discovered but not until tomorrow I'd guess.

[xexyl]

Hmmm .. based on you examples above and based on the fact that to be properly encoded a string has to be surrounded by double quotes I am not sure if the functionality is what you need.

I have to go afk but I'll add a new comment or update this one if you've not seen it when I'm back.

UPDATE 0

Ah. The reason -Q is not showing the same thing as you do is, I see now, that the usage message was wrong/changed. I can fix this and put it in the man page too. I'll check the other things after this is done (though I am not sure if that'll be right after and I'm not sure i I am starting right now either).

UPDATE 1

Actually UPDATE 0 is definitely not what happened. See my comment 2480705661.

[xexyl]

Ugh. I know why the -Q / -e mess. It was from the swapping of terms again. Strange as the files were renamed. I wonder .... well I'll fix it anyway.

[xexyl]

Something is very wrong ... it was not because of that after all. Somehow the functionality of each tool was put in the wrong file. I have no idea how this happened. I know you put in some of those options but whatever the case it can be fixed. Unfortunately it means that we have to figure out what went wrong first.

[xexyl]

Okay I'm totally baffled at what should be what. Has the meaning or use of the options been updated? Because -Q being wrong is not right in the other one (i.e. they weren't swapped by mistake).

Some of the functionality appears to be in the wrong tool.

In commit 3e0c224 you improved the language for -Q of the tools.

In commit bd996d3 you added to jstrencode the -e option and it hasn't changed since then (note I'm seeing this in logs and it would appear, based on what you're saying, that maybe it was changed or you accidentally put it in the wrong file? Not sure). You also removed -m from jstrdecode and you improved the man pages for both tools.

In commit e33ee15 I fixed jstrdecode -Q and I added to jstrdecode -e option as well. The -Q option existed originally before the import.

PLEASE understand that I am NOT blaming you. I'm just trying to figure out what happened so we can get this sorted out. At first I thought maybe I made the mistake even, but it seems like I might not have. Not sure.

I have no idea what needs to happen. Please advise or open a pull request when you're able to as I don't know what you want or need. I'm totally lost here.

Thank you!

[lcn2]

Hi @xexyl,

We have some brief WiFi access and will download the result and test after we process the outstanding PRs.

Regarding GH-issuecomment-2480705661, "no worries". We apologize as for a while we had "view source code only" access and and to make guesses. We also realize we may have overcomplicated the tools with our requests while in the "view source code only" / "limited Internet" / "unstable power" state.

We hope we can clarify soon.

[lcn2]

Regarding GH-issuecomment-2480705661:

We believe the PR for this repo, plus the commits we have pending for the "other repos" should address most, if not all of the issues relating to quoting.

[xexyl]

Hi @xexyl,

We have some brief WiFi access and will download the result and test after we process the outstanding PRs.

Regarding GH-issuecomment-2480705661, "no worries". We apologize as for a while we had "view source code only" access and and to make guesses. We also realize we may have overcomplicated the tools with our requests while in the "view source code only" / "limited Internet" / "unstable power" state.

We hope we can clarify soon.

I know it's late but no problem either. Thanks!

[xexyl]

Regarding GH-issuecomment-2480705661:

We believe the PR for this repo, plus the commits we have pending for the "other repos" should address most, if not all of the issues relating to quoting.

Thanks! I hope so too indeed .. at least too as of yesterday one of the issues in the jstrencode issue is resolved though not all. Thanks.

[xexyl]

QUESTION

Given the problem with what happened with util_test I wonder if we should abandon the use of makefile.local. It would require updating the bug report script but it might be a good idea as it can break things and we no longer need it I think?

What do you think?

UPDATE 0

The more I think on this .. the more I think this is a good idea as it could cause people to have issues like it did me. Even after removing the file if one does not do a make clobber the problem can still persist (that's what happened to me as I was trying to fix it quickly and it was a hard day yesterday).

If one REALLY needs to or what's to modify the command line they can do it manually like with other variables.

Now it is true that most people would not have such a file but it's better to be safe than to cause a potential problem.

[xexyl]

The makefile.local feature was removed here in commit ef45fa8. If you wish me to remove it from dbg or dyn_array (I guess they have it) I would be happy to do that .. tomorrow. I guess the mkiocccentry repo can have this done another time as it's in a code freeze.

This should prevent messes like what happened with mkiocccentry.

UPDATE 0

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning. Have a great day and good luck with the submit server etc.!

[lcn2]

The makefile.local feature was removed here in commit ef45fa8. If you wish me to remove it from dbg or dyn_array (I guess they have it) I would be happy to do that .. tomorrow. I guess the mkiocccentry repo can have this done another time as it's in a code freeze.

This should prevent messes like what happened with mkiocccentry.

UPDATE 0

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning. Have a great day and good luck with the submit server etc.!

See GH-issuecomment-2486345495 and please do not remove it from the "other repo".

[xexyl]

The makefile.local feature was removed here in commit ef45fa8. If you wish me to remove it from dbg or dyn_array (I guess they have it) I would be happy to do that .. tomorrow. I guess the mkiocccentry repo can have this done another time as it's in a code freeze.
This should prevent messes like what happened with mkiocccentry.

UPDATE 0

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning. Have a great day and good luck with the submit server etc.!

See GH-issuecomment-2486345495 and please do not remove it from the "other repo".

As I wrote there: the problem is for the general public. Your idea is interesting though. I asked for questions on what you're getting at. I'm certainly happy to add it back but I think the -include makefile.local is somewhat problematic.

But perhaps you're thinking of something else? In which case it might be good. Of course one does indeed have to use it with care. That being said it could be put in place and totally forgotten. That's how this mess happened.

Please clarify in what you might mean and I'll be happy to modify the changes.

[xexyl]

The makefile.local feature was removed here in commit ef45fa8. If you wish me to remove it from dbg or dyn_array (I guess they have it) I would be happy to do that .. tomorrow. I guess the mkiocccentry repo can have this done another time as it's in a code freeze.
This should prevent messes like what happened with mkiocccentry.

UPDATE 0

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning. Have a great day and good luck with the submit server etc.!

See GH-issuecomment-2486345495 and please do not remove it from the "other repo".

As I wrote there: the problem is for the general public. Your idea is interesting though. I asked for questions on what you're getting at. I'm certainly happy to add it back but I think the -include makefile.local is somewhat problematic.

But perhaps you're thinking of something else? In which case it might be good. Of course one does indeed have to use it with care. That being said it could be put in place and totally forgotten. That's how this mess happened.

Please clarify in what you might mean and I'll be happy to modify the changes.

I did almost write something in the README.md instead about being careful so I can indeed see the usefulness at times. This was more of a safety mechanism for those who are not really aware or forget about it, simply because it is not even obvious that such a file might be included, unless one were to look at the Makefile itself.

I guess you mean something else. And as for Makefile.local instead of makefile.local I know what you mean .. but you had suggested makefile.local initially so I did that.

[lcn2]

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning.

As far as the "other repo", i.e., mkiocccentry repo goes:

The makefile.local will be changed to Makefile.local after the IOCCC28 code freeze is over.

Please DO NOT issue pull requests against mkiocccentry repo as it is in a CODE FREEZE state for which only a significant IOCCC28 impacting urgency could thaw prior to the IOCCC28 release and later judges vacation.

[xexyl]

Okay seems those other repos do indeed have the functionality. If you wish me to remove them I'll look at that tomorrow morning.

As far as the "other repo", i.e., mkiocccentry repo goes:

The makefile.local will be changed to Makefile.local after the IOCCC28 code freeze is over.

Please DO NOT issue pull requests against mkiocccentry repo as it is in a CODE FREEZE state for which only a significant IOCCC28 impacting urgency could thaw prior to the IOCCC28 release and later judges vacation.

I have no intention of doing so. But that's good to know. I agree the change too. I only named it that because you had asked me to name it that.

It does appear your concept you suggest is different from what I removed and that's good. Even so I can certainly add it back but with a caveat.

Anyway must leave. Please clarify over there.

[lcn2]

TIME TO PAUSE

We urgently need to FOCUS on IOCCC28 matters and this will have to respectfully delay for months responding to comments about this repo. Unless we do that, IOCCC28 is not going to start this calendar year ... and we don't want to deal with the consequences of that!

[xexyl]

TIME TO PAUSE

We urgently need to FOCUS on IOCCC28 matters and this will have to respectfully delay for months responding to comments about this repo. Unless we do that, IOCCC28 is not going to start this calendar year ... and we don't want to deal with the consequences of that!

Oh it's no rush. Thanks for that though. Maybe looking at the other thread will give me ideas of what you're thinking of .. not today though.

Best wishes!

[xexyl]

At least the problem was solved though. There certainly are a number of ways to address such a problem in the future and I'll look into your concept which does look different from what we had, at first glance.

Good day!

[xexyl]