Re: shell-backward-kill-word needs to behave more like werase

2021-07-01 Thread Basin Ilya
Upgrading to bash5.1 solved the problem. On 29.06.2021 14:26, Basin Ilya wrote: > I'll try to build bash 5 for Cygwin and reply here > > On 29.06.2021 11:00, Andreas Schwab wrote: >> On Jun 29 2021, Basin Ilya wrote: >> >>> However, shell-backward-kill-word erases the word immedeately >>>

Re: shell-backward-kill-word needs to behave more like werase

2021-06-29 Thread Basin Ilya
I'll try to build bash 5 for Cygwin and reply here On 29.06.2021 11:00, Andreas Schwab wrote: > On Jun 29 2021, Basin Ilya wrote: > >> However, shell-backward-kill-word erases the word immedeately >> preceding the caret plus it erases one additional space. > > Does it? Not for me. > >

Re: shell-backward-kill-word needs to behave more like werase

2021-06-29 Thread Andreas Schwab
On Jun 29 2021, Basin Ilya wrote: > However, shell-backward-kill-word erases the word immedeately > preceding the caret plus it erases one additional space. Does it? Not for me. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780

shell-backward-kill-word needs to behave more like werase

2021-06-28 Thread Basin Ilya
The default werase setting erases the series of white spaces before the caret, then it erases the preceding word (without touching the spaces before the word). I expected that shell-backward-kill-word would do the same with the difference that the entire quoted argument would be erased. However,