issues
search
xilun
/
cbwin
Launch Windows programs from "Bash on Ubuntu on Windows" (WSL)
Other
327
stars
25
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Can't remove cbwin from my pc
#43
ghost
opened
6 years ago
1
Starting parameters for bash.exe
#42
rrezino
opened
7 years ago
0
Some inputted characters skipped in Docker interactive terminal
#41
jelazos7
opened
7 years ago
1
Native Windows support for launching Windows applications
#40
sheldon
opened
7 years ago
1
interactive win32 console programs are broken (input and output)
#39
xilun
closed
7 years ago
5
Optionally start Xming if installed
#38
timfel
closed
7 years ago
2
Vagrant output doesn't wrap correctly
#37
geerlingguy
opened
7 years ago
4
No terminal support
#36
ghost
opened
7 years ago
6
behavior of environment variable inconsistent in regards to case sensitivity
#35
xilun
closed
7 years ago
1
Added path resolution to support unsafe access to bash filesystem.
#34
aHooder
opened
7 years ago
1
Added simple path resolving for the rest of the WSL filesystem.…
#33
aHooder
closed
7 years ago
16
Not work inside zsh
#32
lkytal
closed
7 years ago
14
wstart /mnt/c/windows does not work
#31
marcosdiez
opened
7 years ago
7
sockets for redirections are not using any security
#30
xilun
closed
7 years ago
6
Let cbwin in session mode launch multiple wcmd instances in parallel
#29
fpqc
closed
7 years ago
11
wcmd cmd no longer laggy, but eats characters
#28
fpqc
opened
7 years ago
1
Problem with arguments containing the character "&"
#27
PutoML
opened
7 years ago
1
Use double quotes to prevent word splitting
#26
goreliu
closed
7 years ago
2
Use double quotes to prevent word splitting may be better
#25
goreliu
opened
7 years ago
12
backgrounded & force redirected caller => SIGTTIN
#24
xilun
opened
7 years ago
0
a cmd-like behavior distinguishing between console / GUI target programs might be useful
#23
xilun
opened
7 years ago
1
some win32 console programs "sometimes" do line feed instead of new line, but a workaround seems possible
#22
xilun
opened
7 years ago
1
Default command handler
#21
poma
opened
7 years ago
10
wrun: can't translate a WSL VolFs path to a Win32 one
#20
poma
opened
7 years ago
7
0.9 breaks my use case
#19
fpqc
closed
7 years ago
1
master
#18
marcosdiez
closed
7 years ago
6
find a workaround to mitigate failures of GetExtendedTcpTable()
#17
xilun
opened
7 years ago
1
Text is not aligning right.
#16
TheAggressive
closed
7 years ago
4
start bash.exe from system32 by default
#15
xilun
closed
7 years ago
2
cover safe elevated usage (disallow trivial escalation in that case)
#14
xilun
closed
7 years ago
4
better handle scenarios with a weaker link to the windows console (tmux, xterm&co, etc.)
#13
xilun
opened
8 years ago
7
OUTBASH_PORT is only set for interactive shells
#12
xilun
closed
8 years ago
4
Using outbash with urxvtc and Xming
#11
fpqc
closed
8 years ago
22
manage Win32 processes using Jobs
#10
xilun
closed
8 years ago
2
provide pre-built binaries
#9
xilun
closed
8 years ago
0
msys-style cmdline processing heuristics
#8
Artoria2e5
opened
8 years ago
3
Allow wstart to be invoked from a VolFS cwd
#7
xilun
closed
8 years ago
4
can not pipe from/to Win32 processes
#6
xilun
closed
8 years ago
6
the return status is not propagated to the WSL caller
#5
xilun
closed
8 years ago
0
command line is not propagated to bash.exe launcher
#4
xilun
closed
8 years ago
0
wstart wrun wcmd commands: implementation with netcat has issues
#3
xilun
closed
8 years ago
2
can't set win32 environment
#2
xilun
closed
8 years ago
2
can't set win32 working directory
#1
xilun
closed
8 years ago
2