On 11/22/22 5:01 PM, Chet Ramey wrote:
Thanks for the report. It's an easy fix; bash was optimizing away the
fork
and therefore not printing the timing information.
Awesome!
Hitting it with a hammer: $10
Knowing WHERE to hit it: $9,990
«grin»
--
:- Dabe
On 11/21/22 9:32 PM, Koichi Murase wrote:
`git bisect' finds the following commit (2022-01-31) which introduced
the behavior:
commit b325b0e96bd05c76bbfc4d60d0707fc93d58f03f (HEAD, refs/bisect/bad)
execute_cmd.c
- execute_in_subshell: call optimize_subshell_command for (list)
On 11/21/22 7:36 PM, Emanuele Torre wrote:
On Mon, Nov 21, 2022 at 07:07:08PM -0500, d...@dabe.com wrote:
emanuele6 suspects it has to do with
https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00107.html
No, actually later, I said that it has probably been introduced earlier
On 8/27/21, 5:22 PM, Dabrien 'Dabe' Murphy wrote:
On 8/27/21, 4:09 PM, Chet Ramey wrote:
That circumstance is a pathname consisting solely of one or more
slashes,
separated from the previous word by whitespace. I'll fix it.
The code has been like this since January, 2004. That's pretty dated
On 8/27/21, 4:09 PM, Chet Ramey wrote:
Thanks for the report. That circumstance is a pathname consisting
solely of
one or more slashes, separated from the previous word by whitespace. I'll
fix it.
Awesome! :-D
PS — Another pathological test case is, e.g.:
ls / / / //
The code
On 11/3/16, 4:21 PM, Chet Ramey wrote:
Quote Removal makes sense during command EXECUTION (since you wouldn't want
your quotes passed in with the arguments) but it doesn't make sense during
(readline) EDITING, IMHO...
OK. So let's talk about a mechanism to provide alternate behavior. The
[NOTE] Below is a message I started to write listing a whole slew of
cases where `shell-expand-line` didn't Do What I Mean.
After familiarizing myself with the source code, however, I was
pleasantly surprised to discover that there's actually a one line one
character fix for almost every
On 10/29/15, 4:00 PM, Greg Wooledge wrote:
Do you have a PROMPT_COMMAND variable? Or something unusual in your
PS1 variable? (Doesn't look it from the copy/paste, but you never
know.) Or do you have a DEBUG trap?
Oh yeah, I definitely make extensive use of the PROMPT_COMMAND; that's
how I
On Tue, 24 Aug 2010, Dennis Williamson wrote:
On 8/23/10 3:17 PM, Dabrien 'Dabe' Murphy wrote:
I'd prefer it if, after exiting my $EDITOR, bash simply stuffed the
results back into my readline buffer. Particularly, if I decide to
abandon my changes, I find it worrisome that the shell goes
Is it possible to C-xC-e /without/ immediately executing the resulting
command?
To my mind, editing the buffer and executing it are two different
things -- the latter having potentially dire consequences...
I'd prefer it if, after exiting my $EDITOR, bash simply stuffed the
results back
10 matches
Mail list logo
