Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
Greg Wooledge wrote:
On Thu, Jun 01, 2017 at 09:31:24PM -0700, L A Walsh wrote:
Variable names like:
L??v -- (3 letter word pronounced like Leave), (most recent try...)
Here is a demonstration of the cost of what you are proposing. In my
mail user agent, your variable shows up as L??
It's all but impossible to establish an "absolute need" for a new
feature. In the extreme case there is always the argument that one
does not "absolutely need" a feature added to bash, because one could
simply use Bash to launch another tool that provides that feature -
code in Python rather than
On Thu, Jun 01, 2017 at 10:16:30PM -0700, L A Walsh wrote:
> > Should UTF-8 be assumed?
> You realize bash already allows UTF-8 input?
Of course. Both Bash and Readline are able to process multibyte
character input. That's not the same as parsing multibyte sequences in
*code*. See Python's Enhance
On Thu, Jun 01, 2017 at 09:31:24PM -0700, L A Walsh wrote:
> Variable names like:
>
> L??v -- (3 letter word pronounced like Leave), (most recent try...)
Here is a demonstration of the cost of what you are proposing. In my
mail user agent, your variable shows up as L??v.
Source code with your U
