Invoke Win32 applications with Bash on Windows • Hacker News Board

Re: Invoke Win32 applications with Bash on Windows

#41

Post by WorldMaker » Thu, Oct 20, 2016, 3:56 PM UTC

frutiger wrote: post #32

ZenoArrow wrote: post #28

Earlier quoted context omitted.

I would agree with you, but that'd be the first time I've ever heard that called ConEmu. It's much more likely to be called the Windows command shell, Windows command prompt or cmd. As you're clearly already aware, ConEmu is a specific product that provides an enhanced command line experience on Windows.

FWIW, `cmd.exe` is both, the shell and the console. It is not a terminal (not designed to be operated remotely) nor is it emulating a terminal of any kind. As for the parent poster, they must be abusing the term `ConEmu`, a completely separate console program that can run win32 programs (including `cmd.exe`).

If it helps futher square some of the linguistics digressions the parts of cmd.exe that are the console emulator are typically referred to as the ConHost. The ConHost's console emulation is indeed not quite as great a lot of people would like, which is why many Windows users use a different console emulator named ConEmu. Obviously abbreviating the ability of ConHost's console emulation to conemu rather than spell out "console emulation" causes confusion with the ConEmu tool for Windows.

Re: Invoke Win32 applications with Bash on Windows

#42

Post by ZenoArrow » Thu, Oct 20, 2016, 5:57 PM UTC

0xFFC wrote: post #37

ZenoArrow wrote: post #21

Earlier quoted context omitted.

> "Windows ridiculous conemu. I am not going use a console which I can't resize without any problem." Sorry I don't follow. What resizing problems are you having with ConEmu? Works fine when I've tried it. We are talking about the same ConEmu, right? http://conemu.github.io/en/ http://conemu.github.io/en/ResizeAndMove.html

So sorry about late answer. I meant Windows default console emulator. I forgot what they call it exactly.

Ah, fair enough.

Re: Invoke Win32 applications with Bash on Windows

#43

Post by NoGravitas » Thu, Oct 20, 2016, 6:11 PM UTC

WorldMaker wrote: post #39

NoGravitas wrote: post #36

We're not on Windows 10 yet at my workplace, and I don't use Windows at home, so I've only been following loosely in a "this will be nice once I'm finally able to use it" way. But this bit took me by surprise: > 1 Use the same working directory as the CMD or PowerShell prompt > 2 Are run under as the WSL default user > 3 Have the same Windows administrative rights as the calling process and terminal 1 and 3 are not s…

It seems to work pretty well in practice. The entire Ubuntu "system" is essentially installed into a Windows User's home space, which means that all of the Linux users are unique to a Windows user. This is useful in that you can install things that need Linux accounts for services (like say postgresql that uses a postgres user as a service account) and interact with it with sudo -u just as you would on an ordinary Ub…

Thanks. That is a helpful explanation.

Re: Invoke Win32 applications with Bash on Windows

#44

Post by Senji » Thu, Oct 20, 2016, 8:24 PM UTC

kojoru wrote: post #38

NoGravitas wrote: post #36

We're not on Windows 10 yet at my workplace, and I don't use Windows at home, so I've only been following loosely in a "this will be nice once I'm finally able to use it" way. But this bit took me by surprise: > 1 Use the same working directory as the CMD or PowerShell prompt > 2 Are run under as the WSL default user > 3 Have the same Windows administrative rights as the calling process and terminal 1 and 3 are not s…

Every Windows user get a separate Linux. When they run bash for the first time, system asks them to create a default linux user. Typically, this is also the only user. Mapping Linux users to Windows users would be quite problematic, e. g. with user such as nobody or apache that are typical to Linux.

Solved problem, see Samba

Re: Invoke Win32 applications with Bash on Windows

#45

Post by flukus » Thu, Oct 20, 2016, 10:35 PM UTC

TazeTSchnitzel wrote: post #23

flukus wrote: post #16

Earlier quoted context omitted.

Why does this trigger so many people?

Why is “trigger” used jokingly now? Unless you think the people responding have PTSD or a similar condition.

Because self diagnosed PTSD sufferers on Tumblr made a mockery of it.

The word has uses outside of the PTSD context though, like gun or database triggers.

Re: Invoke Win32 applications with Bash on Windows

#46

Post by timgws » Fri, Oct 21, 2016, 12:20 AM UTC

shados wrote: post #34

Now they just need a better terminal emulator. Windows 10 made some minor but much needed adjustment, but I still end up using Cmdr (a nicely preconfigured ConEmu), and it's decent enough, but it pales over a nicely configured iTerm2 or what most popular Linux distros come with out of the box.

I second this. Someone porting iTerm2 to Windows would make my day.

Re: Invoke Win32 applications with Bash on Windows

#47

Post by TazeTSchnitzel » Fri, Oct 21, 2016, 1:28 AM UTC

flukus wrote: post #45

TazeTSchnitzel wrote: post #23

Earlier quoted context omitted.

Why is “trigger” used jokingly now? Unless you think the people responding have PTSD or a similar condition.

Because self diagnosed PTSD sufferers on Tumblr made a mockery of it. The word has uses outside of the PTSD context though, like gun or database triggers.

> Because self diagnosed PTSD sufferers on Tumblr made a mockery of it.

Why would them being self-diagnosed matter? Why would you react to it having been “made a mockery of” by reinforcing this supposed mockery? It only makes it worse for people who have to deal with it.

Re: Invoke Win32 applications with Bash on Windows

#48

Post by flukus » Fri, Oct 21, 2016, 2:37 AM UTC

TazeTSchnitzel wrote: post #47

flukus wrote: post #45

Earlier quoted context omitted.

Because self diagnosed PTSD sufferers on Tumblr made a mockery of it. The word has uses outside of the PTSD context though, like gun or database triggers.

> Because self diagnosed PTSD sufferers on Tumblr made a mockery of it. Why would them being self-diagnosed matter? Why would you react to it having been “made a mockery of” by reinforcing this supposed mockery? It only makes it worse for people who have to deal with it.

> Why would them being self-diagnosed matter?

Because the self diagnosis is largely made up by people who don't understand what PTSD even is. It's like someone declaring they have cancer without going to a doctor.

> Why would you react to it having been “made a mockery of” by reinforcing this supposed mockery?

Because it's become part of the lexicon now. I don't think there's any going back. My usage was the "new" usage, no relation to PTSD was intended.

Re: Invoke Win32 applications with Bash on Windows

#49

Post by ygra » Fri, Oct 21, 2016, 5:17 AM UTC

frutiger wrote: post #32

ZenoArrow wrote: post #28

Earlier quoted context omitted.

I would agree with you, but that'd be the first time I've ever heard that called ConEmu. It's much more likely to be called the Windows command shell, Windows command prompt or cmd. As you're clearly already aware, ConEmu is a specific product that provides an enhanced command line experience on Windows.

FWIW, `cmd.exe` is both, the shell and the console. It is not a terminal (not designed to be operated remotely) nor is it emulating a terminal of any kind. As for the parent poster, they must be abusing the term `ConEmu`, a completely separate console program that can run win32 programs (including `cmd.exe`).

Cmd.exe is just the shell. The console window is handled by conhost, as are any terminal emulation things.

Re: Invoke Win32 applications with Bash on Windows

#50

Post by tracker1 » Fri, Oct 21, 2016, 6:01 AM UTC

WorldMaker wrote: post #40

tracker1 wrote: post #15

Earlier quoted context omitted.

I have to agree... I'm still using the bash that comes with git for windows. It actually works (mostly) as one would expect it to work. Also, not being able to edit the WSL filesystem from inside a windows editor is a huge loss in terms of usage. It's worse than using Samba/CIFS to share a directory and edit across to a full VM. I happen to like my gui editor, but prefer to run in Linux.

If you had to you can touch things in the WSL VolFS by browsing the appropriate %AppData% subfolder. I'm presuming Microsoft isn't encouraging that right now with this Interop tooling for several reasons. At a guess one of them might be that apparently the Unix things like permissions and Unix-style metadata are stored in NTFS alternate streams (~"resource forks") that they may be worried some Windows programs might…

It actually doesn't work right, and MS just closed the issue. I'd be fine with cifs automounts in the linux subsystem for windows file directories... I mean it may take a little work, but in the end, I want to edit files with a windows gui editor, and run them via the LSW applications. Until I can do that, it's an also ran on the desktop... and until it can be used for docker with linux containers on the server, it doesn't do much use there either.