Search results

Works like a charm, of course. Sorry for the inconvenience :)

I just noticed that this got already merged, so I better test the upstream code :D

I finally got around testing these, and it doesn't seem to work for me. I'm basically running this code: export function creationCombatHandler(round, opp, text) { const macro = generateWeirdeauxMacro(text); printHtml(`creationCombatHandler returned: <pre>${macro}</pre>`); return...

Ah, not bad, I didn't think about simply keeping the references in the global scope. Should the cleanup of temporaryName perhaps happen in a finally-block? I will try the patch in an hour or two...

That sounds like an ideal Implementation from the frontend side. But you still need to "remember" those functions for the invocation somewhere (or refactor quite some stuff to be able to pass functions from and to the runtime), right?

I started working with the JavaScript Runtime, and I couldn't figure out how to use adventure() with a custom combat filter function defined in the same script. The function is never found, and thus always returns void. (Shouldn't it throw an error if the requested function is not found? Ash...

My screenshot is from Windows Terminal as well, albeit with WSL. But the program itself is definitely not limited to 256 color mode. @philmasterplus, would you mind sharing your js snippet as copiable text, that would be super helpful :)

Unrelated to the errors, but related to the color terminal, here is a small script to test whether KoLmafia and/or your terminal are outputting the colors you expected: const kolmafia = require('kolmafia'); let s = ''; function hex(n) { return ('0' + parseInt(n).toString(16)).slice(-2); }...

Sorry if my code caused any trouble. I tried to keep the formatting as I perceived it is used in the project, even though it's not very "standard Java" in some regards.

I'm just saying, what you are requesting is to do a "completely" different operation, not just "normal" division not working right. There is also integer division in "math", so "how math works" is a somewhat narrow view. Anyway, I just thought this might help to understand why it might not be a...

I don't think it would necessarily break operator precedence, but it would definitely break existing code. This is not what happens. The operation that is happening here is an Integer division, so it's: step 1: "Integer 1 divided by integer 2 is 0" It has nothing to do with the fact that it's...

Thanks for merging! Next stop: input line editing with history :)

Thanks! Could you perhaps get the jar file from https://search.maven.org/artifact/org.fusesource.jansi/jansi/2.3.2/jar ? There have been quite some fixes since 2.1.0, plus that's the version I tested against.

Attached is the latest version of the patches, unchanged since this post:

Is there something I can approve on this patch to get it merged? I have been running it in its current state for a while now without any problems. Are there any open concerns I can address?

I've decided that it makes more sense to have all other tags in the output, but printed in gray, otherwise stuff like tables looks really garbled. It still does not look like much, but better than having the unformatted HTML, and better than just the text:

I've added support for <b> <i> <u> and <s> tags

Ansi Terminal is now configurable: Let me know if you have any more remarks!

Yes, correct, this only influences what is printed to stdout. The GUI is not affected at all.

That should be easy, I hope 😄 Per-user means per-character, right?