Since upgrading to OS X 10.10 Yosemite and thus bash 3.2.53 use of the
PROMPT_COMMAND='history -a; history -n'
workaround to get a single ksh-style history causes the shell to become less
and less responsive until it permanently hangs.
The problem is somewhat intermitant in terms of how quickly
On 10/29/14, 1:31 AM, Graham Jones wrote:
Since upgrading to OS X 10.10 Yosemite and thus bash 3.2.53 use of the
PROMPT_COMMAND='history -a; history -n'
workaround to get a single ksh-style history causes the shell to become less
and less responsive until it permanently hangs.
I wasn't able
Hello,
Would it make sense to add to 'time' builtin a way to measure how long
a file descriptor is been kept open? Something like this.
-- snip
#!/bin/bash
exec 420
time --file-descriptor 42
sleep 10
exec 42-
-- snip
$ ./above_script.sh
real0m10.012s
user0m0.000s
sys 0m0.000s
This
On Wed, Oct 29, 2014 at 02:09:53PM +, Sami Kerola wrote:
Would it make sense to add to 'time' builtin a way to measure how long
a file descriptor is been kept open?
Doesn't really make much sense. If you want multiple independent timers,
there's no reason to tie them to open file
On 10/29/2014 09:35 PM, Pádraig Brady wrote:
On 10/27/2014 10:35 PM, Daniel Colascione wrote:
+@item enable-bracketed-paste
+@vindex enable-bracketed-paste
+If set to @samp{on} and the terminal supports bracketed paste mode,
+configure it to insert each paste into the editing buffer as a
On 10/29/2014 09:42 PM, Daniel Colascione wrote:
On 10/29/2014 09:35 PM, Pádraig Brady wrote:
On 10/27/2014 10:35 PM, Daniel Colascione wrote:
+@item enable-bracketed-paste
+@vindex enable-bracketed-paste
+If set to @samp{on} and the terminal supports bracketed paste mode,
+configure it to
On 10/29/14 5:35 PM, Pádraig Brady wrote:
On 10/27/2014 10:35 PM, Daniel Colascione wrote:
+@item enable-bracketed-paste
+@vindex enable-bracketed-paste
+If set to @samp{on} and the terminal supports bracketed paste mode,
+configure it to insert each paste into the editing buffer as a
On 10/29/14 10:09 AM, Sami Kerola wrote:
Hello,
Would it make sense to add to 'time' builtin a way to measure how long
a file descriptor is been kept open? Something like this.
You can use $SECONDS for this, but you have to do the math and keep track
of the file descriptors yourself.
Chet
