I would like for the following to evaluate the code and print the output of "a" (ignoring the name ping at the end)

lorem:
!js const a=1; a @lorem#42

sbot:
`1`

vs

sbot:
``

Lots of great shit happens, and pinning comments can rarely capture entire sagas, like Jellek's, for people to read and/or have context without constantly playing back old stories. So, I propose the introduction of a command, provisionally named !chronicle for this text.

Syntax

!chronicle @user_mention number &comment

• The user is a mention of the user to be archived,
  • if user is @all, or @everyone, no messages are filtered, and the last N messages are grabbed and logged.
• The number is the last X messages a user sent. This will prevent unrelated messages being in there, but comes at the cost of the caller having to count relevant messages.
• The command is the rest of the arguments joined by spaces, it is then included in the proposed header (below)

Archiving format

I would suggest a rather raw, file-based archival for easy browsing on whatever host it ends up being on, with a following format:

# $user-YYYY-MM-DD.txt
Author: $user
Time: YYYY-MM-DD hh:mm (UTC)
Comment: $comment
--- 
$user: Now this is a story all about how
$user: My life for flipped - turned upside down
... 

Additionally to flat file storage, I would suggest the command trigger the generated archive file to be commited to a git repository, and the git repository being pushed to origin. This would mean that any story captured would be immediately available with a git host (like github)

Alternative command name

Just some I came up with:

• !log
• !capture
• !saga

Open Problems

• Should there be some sort of two-stage mechanism that would announce the cut-off message by that user and require conformation and logging it? This would prevent message counting but introduce spam to the channel and make it more awkward to use.
  • This could be solved if the cut-off messages are PMd to the user for adjustment before confirmation, but would mean additional development effort.
• If going with the git commit feature, there should also be a !chronicle link command that reads origin and spits it out to discord.

!timer should send the reminder to the channel that it was set in, instead of consolidating everything to a single channel.

Current functionality causes reminders from all connected servers to be sent to the same place

name: `try { throw new Error('a'); } catch { console.log(e) }`

sbot: 
``

https://github.com/raylu/sbot/blob/master/code_eval.py#L7:L29
Should also read from "stderr" and not just "stdout"