Re: [PATCH v2 5/8] builtins/source: parse the -i option

2024年5月25日(土) 8:45 Lawrence Velázquez : > On Fri, May 24, 2024, at 9:04 AM, Koichi Murase wrote: > > 2024年5月24日(金) 19:18 Martin D Kealey : > >> On Tue, 21 May 2024 at 23:16, Koichi Murase wrote: > >>> However, I personally do not think the FPATH mechanism is useful > >>> because a file can only co

Re: [PATCH v2 5/8] builtins/source: parse the -i option

On Fri, May 24, 2024, at 9:04 AM, Koichi Murase wrote: > 2024年5月24日(金) 19:18 Martin D Kealey : >> On Tue, 21 May 2024 at 23:16, Koichi Murase wrote: >>> However, I personally do not think the FPATH mechanism is useful >>> because a file can only contain one function per file. Significantly >>> non

Re: [PATCH v2 5/8] builtins/source: parse the -i option

2024年5月24日(金) 19:18 Martin D Kealey : > On Tue, 21 May 2024 at 23:16, Koichi Murase wrote: >> 2024年5月21日(火) 14:56 Phi Debian : >> > 'May be' bash could investigate the ksh93/zsh $FPATH autoload, but don't >> > know if that would be good enough for the initial purpose. >> >> There are already shell

Re: [PATCH v2 5/8] builtins/source: parse the -i option

On Tue, 21 May 2024 at 23:16, Koichi Murase wrote: > 2024年5月21日(火) 14:56 Phi Debian : > > 'May be' bash could investigate the ksh93/zsh $FPATH autoload, but don't > > know if that would be good enough for the initial purpose. > > There are already shell-function implementations at > /examples/fun

compute_lcd_of_matches w/ mismatched upper/lowercase byte counts

This requires case-insensitive completion of two+ words where the the prefix in a word contains the single-byte lowercase form of the multi- byte character occuring in the same position in an earlier word. The words here start consist of one of the following followed by `-': U+212A KELVIN SIG