Hi All,
I posted a question to STKO and someone suggest I should open a 'feature
request' here.
https://stackoverflow.com/questions/68065039/bash-completion-after-a-multiline-string
Thanx in advance,
Phi
On 6/20/21 4:05 AM, Oğuz wrote:
$ set -o posix
$ uname &>/dev/null
$
`uname &' and `>/dev/null' should be parsed as two separate commands;
that, if I'm not missing anything, is what POSIX says. But bash
doesn't do that in POSIX mode, and redirects both stderr and stdout to
`/dev/n
21 Haziran 2021 Pazartesi tarihinde Chet Ramey yazdı:
>
> You're right, and it's not worth changing at this point. It's come up
> before, and the bash interpretation is much more useful and compatible.
Okay then
>
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>
On 6/20/21 12:51 PM, Teemu Leisti wrote:
Bash Version: 5.1
Patch Level: 4
Release Status: release
Description:
When using ctrl-R to search in the command history, Bash highlights
the searched string, but not its first character.
Repeat-By:
1. Open Bash, and command: abcdef
2. Click Ctrl-R, and
On 6/16/21 2:04 AM, konsolebox wrote:
Thanks, that worked well. Is there a chance a feature that would
allow this be defaulty implemented in the next version? If yes, what
would be the strategy?
Someone in IRC asked about this too just recently.
Any thoughts in this?
I'll
You're right; the cursor was a block when I saw the bug, but when I changed it
to I-beam, command search worked as expected. When using a block cursor, it's
shown as a highlight of the character under the cursor, and the highlighting of
the searched string seems to be reversing that.
So my bug rep
