time keyword evaluates following command's (builtin) argument

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE

Re: time keyword evaluates following command's (builtin) argument

On Tue, Jan 16, 2018 at 10:50:34AM +0200, Anti Räis wrote: > Description: > Bash unexpectedly evaluates a builtin command argument when it is > executed after `time` keyword. This does not happen when the builtin > command is executed at later time or with different type of argument. > ali

[annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

I asked on StackExchange prior to this: https://apple.stackexchange.com/questions/310965/stop-iterm2-from-using-disk-disk-cannot-be-ejected Initially I thought it was specific to the terminal e

Re: time keyword evaluates following command's (builtin) argument

On 1/16/18 3:50 AM, Anti Räis wrote: > Bash Version: 4.3 > Patch Level: 48 > Release Status: release > > Description: > Bash unexpectedly evaluates a builtin command argument when it is > executed after `time` keyword. This does not happen when the builtin > command is executed at later time

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

hack the kernel and fix the bug in osx where it's supposed to be fixed On 1/16/18, Danyel Bayraktar wrote: > I asked on StackExchange prior to this: > https://apple.stackexchange.com/questions/310965/stop-iterm2-from-using-disk-disk-cannot-be-ejected >

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

True, I did mention that in the stackexchange. Not sure it’s a bug, but it’s definitely a design flaw in my opinion. However, Apple probably has no interest in fixing this as apps already depend on the behaviour. And in principle, as you do mention hacking, I’m not sure if disabling this “"feat

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

On Tue, Jan 16, 2018 at 10:36:47PM +0800, Danyel Bayraktar wrote: > Initially I thought it was specific to the terminal emulator, but it is > actually due to the design of OS X. My problem is that when cd’ing into the > external drive to run an `ls`, I’m not really “using” it and should be able

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

On 1/16/18 11:26 AM, Greg Wooledge wrote: > On Tue, Jan 16, 2018 at 10:36:47PM +0800, Danyel Bayraktar wrote: >> Initially I thought it was specific to the terminal emulator, but it is >> actually due to the design of OS X. My problem is that when cd’ing into the >> external drive to run an `ls`,

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.

On 2018-01-16 at 22:36 +0800, Danyel Bayraktar wrote: > This is my first e-mail here — I would love to help implement this if you > give me some pointers and a contribution guide. > > Best regards, > Danyel. As Greg mentions, this is the same on other Unix systems too. Now, as you mention, this