Re: Minor utf32-to-utf8 bug

2019-11-11 Thread Chet Ramey
On 11/10/19 9:07 AM, István Pásztor wrote:
> Hi
> 
> The encoding of six bytes long utf-8 sequences is buggy. Today unicode
> requires at most 4 bytes long utf-8 sequences but if we handle 5 and 6 too
> then let's do it the right way.

Thanks for the report and fix.

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/



blink-matching-paren breaks closing parenthesis binding

2019-11-11 Thread Nikolaos Kakouros
In my .bashrc, I have:


```
bind -x '")": bash_function'
bind 'set blink-matching-paren'
```

If I type `)` in bash, nothing happens. Blinking works. If I reverse the order 
of the commands, then blinking stops working and the binding works.

I think I understand the reason behind this; `blink-matching-paren` uses `)` to 
run the blinking function, sth like a hidden default binding. 

I thought I should mention this as it is not documented anywhere and I don't 
know if it could be considered a bug or a documentation issue.

Could the matching paren functionality be triggered manually from within the 
`bash_function` function? That could also be mentioned in the docs.