Marc Vertes

I tested it with yaegi-0.15.1 and the result is correct. I can not reproduce this issue.

I can reproduce this issue without windows with the following sample.go (with a different output): ```go package main import _ "github.com/chromedp/chromedp" func main() { println("hello") } ``` ```console $ yaegi...

Can you provide a test program which fails before and works after your change request? I'm not able to reproduce the issue you mention. We already have the panic wrapped...

I see that some tests are not passing, even if they print the correct results. This is due to eval_tests not trimming spaces in results. Let me fix this.

This is an issue with the REPL where the stop signal is not well propagated. It occurs on other platforms too.

As a workaround `Ctrl-C` followed by a `Ctrl-D` allows to terminate the REPL. The first `Ctrl-C` interrupts the main REPL loop (but not the `for` loop which is in its...

The original code is correct, and the fix is not semantically identical. It seems to be an issue in gawk, in the regex analyzer, see this [message](https://lists.gnu.org/archive/html/bug-gawk/2025-03/msg00009.html). To avoid this...

``` --- txt2man.orig/txt2man +++ txt2man/txt2man @@ -214,7 +214,7 @@ BEGIN { # remove spaces in empty lines sub(/^ +$/,"") } -/^[:space:]*[[:upper:][:digit:]]+[[:upper:][:space:][:digit:][:punct:]]+$/ { +/^[\x09-\x0D\x20]*[[:upper:][:digit:]]+[[:upper:][:space:][:digit:][:punct:]]+$/ { # Section header if ((in_bd +...

I think 214e3e4 fixes the issue of your particular case (by reverting 2 commits before). I also started a test suite to better detect and handle regressions. There is still...