{"session": "c35e7375-7ce3-4bc3-b1ae-7cdf73bd1488", "env": "main", "command": "journal message process 24434 \"plugins shouldn't react to that stuff or any features\" todo:3999 >/dev/null 2>&1; journal helper say 230 \"Coco, refinement of 3999 from the user: plugins and features don't act on a [journal] prompt in the hook either; if anything should see it, the hook dispatches one event for it and the handlers run async, never in the hook's answer.\" 2>&1 | tail -1; journal message reply 24434 \"Agreed, Sir Jesse. The hook answers a [journal] prompt at once, with no plugin or feature acting in it. If anything does need to see it, the hook raises one event and the handlers run afterwards, out of the hook's way. I've added that to Coco's to-do 3999.\" 2>&1 | tail -1", "parts": ["journal message process 24434 \"plugins shouldn't react to that stuff or any features\" todo:3999 >/dev/null 2>&1", "journal helper say 230 \"Coco, refinement of 3999 from the user: plugins and features don't act on a [journal] prompt in the hook either; if anything should see it, the hook dispatches one event for it and the handlers run async, never in the hook's answer.\" 2>&1 | tail -1", "journal message reply 24434 \"Agreed, Sir Jesse. The hook answers a [journal] prompt at once, with no plugin or feature acting in it. If anything does need to see it, the hook raises one event and the handlers run afterwards, out of the hook's way. I've added that to Coco's to-do 3999.\" 2>&1 | tail -1"]}