Re: man bash does not list 'in' as a builtin command

2019-11-26 Thread Chet Ramey
On 11/25/19 8:15 PM, Clint Hepner wrote: Alternatively, maybe a short list of sections at the top of the man page would provide a hint. The man page format is pretty entrenched. This is an opportunity for other tools to fill the gap. For example, imagine the man page started out like this:

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Dennis Williamson
On Tue, Nov 26, 2019, 9:50 AM Алексей Шилин wrote: > В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет: > > You have printable characters enclosed. For example, \u. _Each_ > > sequence of unprintable characters needs to be separately enclosed > > _without_ enclosing the printable ones. > >

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Алексей Шилин
В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет: > You have printable characters enclosed. For example, \u. _Each_ > sequence of unprintable characters needs to be separately enclosed > _without_ enclosing the printable ones. > > The first part of your prompt is what needs to be corrected.

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Алексей Шилин
В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет: > You have printable characters enclosed. For example, \u. _Each_ > sequence of unprintable characters needs to be separately enclosed > _without_ enclosing the printable ones. They're all part of the escape sequence. Try: printf '\e]0;hell

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Greg Wooledge
On Tue, Nov 26, 2019 at 07:35:09AM -0600, Dennis Williamson wrote: > On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин wrote: > > And they *are* enclosed: PS1='\[\e]0;\u@\h: \w\a\]${debian_chroot... > > You have printable characters enclosed. For example, \u. _Each_ sequence of > unprintable characters

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Dennis Williamson
On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин wrote: > В Пн, 25/11/2019 в 18:29 -0800, L A Walsh пишет: > > Multi-byte or not, invisible characters need to be enclosed > > as documented under 'PROMPTING': > > > > \[ begin a sequence of non-printing characters, which could > >

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

2019-11-26 Thread Алексей Шилин
В Пн, 25/11/2019 в 18:29 -0800, L A Walsh пишет: > Multi-byte or not, invisible characters need to be enclosed > as documented under 'PROMPTING': > > \[ begin a sequence of non-printing characters, which could > be used to embed a terminal control sequence into the >

Re: man bash does not list 'in' as a builtin command

2019-11-26 Thread Robert Elz
Date:Mon, 25 Nov 2019 19:13:19 -0800 From:Peter Benjamin Message-ID: <14db6b9f69f249db60a0f92df80339d88efba152.ca...@peterbenjamin.com> | Only those RESERVED WORDS when tried at the CLI, alone, that generate a | 'confusing' error message, It is possible for some