@JeffSchaller et al, so I flagged one comment-turned-into-chat message an hour ago, noting a discussion that already happened and was deleted twice. Somehow that single flag was ok, and the comment/message got removed, but anything else I flag on that same discussion is inappropriate?
@ilkkachu I might be missing part of the picture, but your most recent flags seem to have been marked 'helpful'. I moved the comments to chat, but haven't seen anything since then.
@JeffSchaller, I wonder if chat flags go somewhere else(tm). I flagged a few messages from the now-chat, basically because the whole discussion is without value. But I didn't flag them all, so the result was a partial and even more useless chat record. :D I tried to flag the rest too, and got popups for declines, but I don't know where they show or who the flags even go to.
@ilkkachu ahhh, I think that helps explain it. Chat flags go "network"-wide, where "network" is some crazy division between SO and SE and something else. So any moderator in that network who happens to be online and wants to handle chat flags could jump in and do things. Looks like someone deleted chat messages, like you said.
I think that the chat room will eventually be deleted, so you two can gather whatever useful information there is and apply any updates that are needed. (being agnostic to the content here)
ahhh, I thought they got deleted after people stopped talking in them. SE trivia doesn't manage to stick in my head very long. If you're both done talking there, I could try to delete the room. I just wanted the comment string to take place elsewhere until it was settled.
I'm not sure how to interpret that; it looks like I do have the option to delete it. If I did that, I'd also go and delete the 'moved to chat' comment that points there. Would that be OK with you? I should probably say this in that room.
@JeffSchaller perhaps. But the moving to chat breaks the unwritten contract there is about chat messages, namely that they can be deleted at will. And as we saw with the flags, apparently breaks other functionality too.
@MichaelHomer, yes, probably just that. Why they'd do that, I have no idea. But I'm not really interested in editing that answer for completeness. If it's wrong, that's different.
@FaheemMitha I think I experienced this (shell vs no shell) behaviour today. I had to kludge a shell script to run some calculations on a half-defunct HPC cluster (the scheduler was down). It included a 21-element loop, each iteration 60 minutes long. I made a mistake and each of them were to die after 30 minutes... When I noticed the mistake I wanted to kill the "job", but since I executed the script with ./script_name.sh I couldn't kill it, only the processes spawned
I had to change to running my script as bash script_name.sh in order to be able to kill it directly
In my original setting the simplest solution was to rename one of the input files temporarily so that the subsequent loop iterations all failed instantly...
