On Mon, Dec 11, 2023 at 1:09 AM Dan Jacobson wrote:
> Type ^R and some string,
> At the point while we are typing that the search fails, all that
> happens is the word "failed" gets added at front,
>
> (reverse-i-search)`nni': set
> jida^Ci.org/geo/house_numbering/grids/us/il/lake/lake_county/
>
At 2023-12-11T15:09:26+0800, Dan Jacobson wrote:
> Type ^R and some string,
> At the point while we are typing that the search fails, all that
> happens is the word "failed" gets added at front,
Not for me. I also get a visual bell for each character I add to the
pattern once the match fails.
Yo
Type ^R and some string,
At the point while we are typing that the search fails, all that
happens is the word "failed" gets added at front,
(reverse-i-search)`nni': set
jida^Ci.org/geo/house_numbering/grids/us/il/lake/lake_county/
(failed reverse-i-search)`nnii': set
jida^Ci.org/geo/house_number
Fra: Chet Ramey
>On 12/5/23 6:46 PM, Ole Tange via Bug reports for the GNU Bourne Again
SHell wrote:
>> For the (admitedly weirdly named) dirs below TAB completion does not
>> work correctly.
>Thanks for the report. Where did you encounter these directory names?
Test purposes.
GNU Paral
On 11/30/23 5:18 AM, Martin D Kealey wrote:
When I said:
> This change will break scripts that use $((10#$somevar)) to cope with
> somevar having leading zeroes OR BEING EMPTY.
Chet replied:
this clearly invalid syntax
"Clearly Invalid" is a matter of perspective. To me "no d
On 11/30/23 5:18 AM, Martin D Kealey wrote:
If there's a bug tracking system beyond "threads in a mailing list", I'd
like to know how I can get access to it.
https://savannah.gnu.org/support/?group=bash
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars long
Date:Sun, 10 Dec 2023 18:59:22 +0300
From:=?UTF-8?B?T8SfdXo=?=
Message-ID:
| There doesn't have to be a standard way; I'd set it in ~/.profile, you'd
| set it wherever is convenient on your setup.
The point is that the people who want this don't want to have a
On Sunday, December 10, 2023, Koichi Murase wrote:
>
> In that case, a question would be what would be the standard way to
> specify the Bash-specific variable,
>
There doesn't have to be a standard way; I'd set it in ~/.profile, you'd
set it wherever is convenient on your setup.
