Re: [ PATCH 1/1 ] l10n: zh_{CN,TW} localization update for bash 4.3
On 8/22/15 8:46 AM, Mingye Wang (Arthur2e5) wrote: It appears that bash-4.4 pots are not yet submitted to TP, so maybe you need to submit them first. I don't usually submit the POT files until I get through a round of alpha testing, but I will send them a note today. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: help builtin generates unaligned results for multicolumn widechars.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/22/15 9:59 AM, Mingye Wang (Arthur2e5) wrote: Version: = 4.4-alpha In bash's `help.def' builtin, wdispcolumn() is used to display `help' columns. It terminates the string at wcstr[width - 1], with a comment that assmues each wide character to be exactly one column wide. This works fine with most languages where widechars are, actually, one column wide. But with East Asian languages, more specifically Chinese, Japanese Korean, it would produce terrible results. Maybe bash should consult wcswidth(wcstr+1,displen), or get the `len' in wcsnwidth() changed to some additional int* argument to store it, and consider the the difference between the real width and displen. Thanks. I made some changes along these lines that will be in the next push to the devel branch. Chet - -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlXcfAoACgkQu1hp8GTqdKu7SQCfbDVrAq0/pnrLBLdOD2XLv39o 04kAoII1J+A+j4jYx9Qu/0XaiVt1uXYE =uzw9 -END PGP SIGNATURE-
Re: bash completion escaping bug
On 8/24/15 4:01 PM, Neven Sajko wrote: Hi, I use bash 4.3.039 and there is a bug (not necessarily a recent regression) with its file name completion feature. for example I have this in shell input: db.rc $home/Downloads/games/DOS/Captai and after I press Tab I have this: db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dome\ of\ Darkness.zip Notice the dollar sign which is now erroneously escaped (home is a variable). This is a case for which you need to enable the `direxpand' option. You've presented the bash completion code with an ambiguous case: it needs to backslash-escape characters in the filename that are special to the shell, but you want some of them to be escaped (the spaces) and not others (`$'). The bash interface to the readline completion engine escapes all special characters in the filename, and, without `direxpand', the filename it's presented looks like this: $home/Downloads/games/DOS/Captain Bible in the Dome of Darkness.zip The quoted version is what you see. Enabling `direxpand' will eliminate the ambiguity by expanding the variable to its value before trying to quote the special characters. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Function name conflict with alias in bash-4.3
Hi,
I found a bug in bash-4.3 (4.3.39 in fedora 21), that seems to exists for a
long time (at least from 4.1.2 in Centos 6).
If you have an alias named foobar, you can create a function with the keyword
function (with or without parenthesis) :
$ function foobar { :; }
But you cannot if you don't :
$ foobar() {:;}
-bash: syntax error near unexpected token `('
It's not really critical once you know it, but it's a little bit odd !
Thank you,
Corentin Peuvrel
Re: bash completion escaping bug
for example I have this in shell input: db.rc $home/Downloads/games/DOS/Captai and after I press Tab I have this: db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dome\ of\ Darkness.zip Sorry, the completed command line was wrapped: db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dome\ of\ Darkness.zip Also, I forgot to say that the bug only happens when there are characters in the filename that may be legitimately escaped, blanks in this case.
Re: Function name conflict with alias in bash-4.3
On Tue, Aug 25, 2015 at 06:36:34PM +0200, Corentin Peuvrel wrote:
If you have an alias named foobar, you can create a function with the
keyword function (with or without parenthesis) :
$ function foobar { :; }
But you cannot if you don't :
$ foobar() {:;}
-bash: syntax error near unexpected token `('
unalias foobar
foobar() { ...; }
