tested git-bug.exe 0.5.0 (both 386, amd64) on win10 (x64) and win7 (x64)
Installation steps:
extract PortableGit 2.23.0 to C:\PortableGit\
copy git-bug.exe to C:\PortableGit\usr\local\bin\
run PortableGit git-bash.exe (MinGW)
cd to git project
git bug user create
git bug termui << nothing is shown
Any flags to enable verbosity/debug to see what's wrong?
(Update 4 Oct)
Found a workaround for this issue:
winpty git bug termui
However the interactive UI get sluggish after exiting the subprocess editor (e.g. create new bug, add comment)
Amine (a-hilaly) commented (edited)
FWIK there are no flags to enable verbosity for git bug termui. Is there any specific exit status or visual bug we can investigate ?
This might be related to PortableGit if this is what you are using. Did you try using any other environnement ?
Michael Muré (MichaelMure) commented
What terminal are you using ?
Does other commands like git bug add of git bug ls work ?
@A-Hilaly i tried on official Git-2.23.0-64-bit.exe installation.. same issue..
@MichaelMure i'm not sure how to use gocui to test this issue.. none of them appears to offer a bash terminal..
Or do you mean to git clone any one of the projects, and try git bug termui on them using official Git client?
Michael Muré (MichaelMure) commented
I mean install one project that use the gocui library (say, https://github.com/gulyasm/jsonui/releases) and test if it works properly. If not, it's likely that gocui is broken, not git-bug.
hockguan.tok (hgtok) changed the title from termui not displaying anything (on mingw) to termui not displaying anything (on mingw)
hockguan.tok (hgtok) commented
I think we narrowed it, same issue also appears for jsonui
MinGW: cat test.json | ./jsonui_windows_amd64.exe
Result: not working
DOS: type test.json | jsonui_windows_amd64.exe
Result: working!
This lead me to test git-bug on msdos:
MSDOS: git-bug_windows_amd64.exe termui
Result: working!
(But it errors out when I try to create "new bug" on MSDOS, looking for sh. lol )
Have updated bug title to reflect MinGW, as that is my use case
Michael Muré (MichaelMure) commented
So it's a gocui compatibility problem. Not much we can do here.