Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it understand / ‘.say’ $ / too #130

Closed
AlexDaniel opened this issue Apr 16, 2017 · 4 comments
Closed

Make it understand / ‘.say’ $ / too #130

AlexDaniel opened this issue Apr 16, 2017 · 4 comments
Labels
evalable Issues related to Evalable bot testneeded Issue is generally resolved but tests were not written yet

Comments

@AlexDaniel
Copy link
Member

Nowadays evalable allows you to omit m::

<AlexDaniel> say 42
<evalable6> AlexDaniel, rakudo-moar e0e080089: OUTPUT: «42»

However, it only works if you start your message with say. A lot of the times people end their messages with .say, like here.

As always, we should find the amount of times it could've mistakenly triggered in the past if the feature was implemented (use quotable for that).

@AlexDaniel AlexDaniel added the evalable Issues related to Evalable bot label Apr 16, 2017
@AlexDaniel
Copy link
Member Author

That said, sometimes it triggers when people don't want to:

@AlexDaniel
Copy link
Member Author

I noticed that every time it was mistriggered, the snippet produced non-zero exit code. Maybe if we add a check for that it will become significantly better.

See also: #53

@AlexDaniel
Copy link
Member Author

Also maybe reply on camelia: also, but exclude real camelia commands like help.

AlexDaniel added a commit that referenced this issue Jan 31, 2018
This should trigger more and less at the same time. We will no longer
see annoying evals that result in compile time error, but we might see
it being triggered on things that actually work (even if
surprisingly).

Somewhat similar to Braitenberg vehicles, achieves intelligent
behavior using even simpler rules. Can now detect code in any message,
not just starting with “say”. Contrary to the logical approach of
detecting code and then running it, it runs every message first and
then only sends a response if the output is nice (0 exit code, no
warnings, etc.).

Rhesolves #53, #130
@AlexDaniel AlexDaniel added the testneeded Issue is generally resolved but tests were not written yet label Jan 31, 2018
AlexDaniel added a commit that referenced this issue Feb 6, 2018
@AlexDaniel
Copy link
Member Author

This was properly resolved together with #53, and I think there are enough tests for this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
evalable Issues related to Evalable bot testneeded Issue is generally resolved but tests were not written yet
Projects
None yet
Development

No branches or pull requests

1 participant