Can it support pipe line input ? echo "pipeinput" | ./readline-cli

[johnwmail]

[slingamn]

What is the question exactly? Your screenshot seems to show readline working as expected with non-terminal input.

[wader]

I think related to chzyer/readline#234

[slingamn]

Oh, that makes sense, the ask is for the program to continue executing? expect(1) is the normal workaround for this, it works with both our fork and upstream.

[slingamn]

#!/usr/bin/expect -f

spawn ./readline-demo
send "pipeinput\n"
interact

produces

$ ./expect-demo 
spawn ./readline-demo
pipeinput
» pipeinput
2024/06/16 05:08:04 you said: "pipeinput"
» 

Integrating this directly into readline is out of scope.

[johnwmail]

The golang-cli still existed ....

[johnwmail]

My golang-cli is will simply call fmt.Scanln and ask the user input login/pass as variable while the cli running.
In the meantime, the cli can either open file, everything work fine,

Until I want make it support either open file or read the pipeline input, the pipeline input break the fmt.Scanln

(like this: echo "filename" | cli or cli -f filename) and while the cli running , it will ask user input login/pass