Re: [PATCH] expand_declaration_argument: handle mixed on/off opts
On 2/13/24 12:58 AM, Grisha Levit wrote: When assigning a variable as part of expanding a compound assignment argument, any [aAgGiIluc] options are treated as either all being on or all being off: Thanks for the report and patch. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/ OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Bug: Ligatures are removed as one character
On 2/19/24 9:26 PM, Avid Seeker wrote: When pressing backspace on Arabic ligatures (including characters with diacritics), they are removed as if they are one character. What's your locale? (Not that I guarantee having it installed.) -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
human-friendly ulimit values?
When setting memory-size limits via "ulimits", users have to manually convert from their intuitive units. E.g., for limiting virtual memory to 8 gigabytes, the invocation is "ulimit -v 8388608", rather than something like "ulimit -v 8gb". If I were to submit a patch for this, is there any chance of it getting accepted?
Re: human-friendly ulimit values?
On Feb 21 2024, Christian Convey wrote: > E.g., for limiting virtual memory to 8 gigabytes, the invocation is "ulimit > -v 8388608", rather than something like "ulimit -v 8gb". Or ulimit -v $((8*1024*1024)) -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Re: human-friendly ulimit values?
On Wed, Feb 21, 2024 at 12:17 PM Andreas Schwab wrote: ... > Or ulimit -v $((8*1024*1024)) > Good point. If a user remembers that "-v" implicitly works in 1024-byte units, that's a good shortcut.
Re: Bug: Ligatures are removed as one character
$ locale LANG=C.UTF-8 LC_CTYPE="C.UTF-8" LC_NUMERIC="C.UTF-8" LC_TIME="C.UTF-8" LC_COLLATE="C.UTF-8" LC_MONETARY="C.UTF-8" LC_MESSAGES="C.UTF-8" LC_PAPER="C.UTF-8" LC_NAME="C.UTF-8" LC_ADDRESS="C.UTF-8" LC_TELEPHONE="C.UTF-8" LC_MEASUREMENT="C.UTF-8" LC_IDENTIFICATION="C.UTF-8" LC_ALL= But it's the same behavior even if bash is launched with: $ LANG=ar_EG.UTF-8 bash On Wednesday, February 21st, 2024 at 16:23, Chet Ramey wrote: > On 2/19/24 9:26 PM, Avid Seeker wrote: > > > When pressing backspace on Arabic ligatures (including characters with > > diacritics), they are removed as if they are one character. > > > What's your locale? (Not that I guarantee having it installed.) > > -- > `The lyf so short, the craft so long to lerne.'' - Chaucer` Ars longa, vita > brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
