On 1/21/18 12:23 PM, gaze...@xmission.com wrote:
> 3) Using Escape v to edit a command line in vi mode works, but leaves the
> keyboard in a funny state. Specifically, it leaves you at the next bash
> prompt, but
> in "vi mode" - i.e, hitting k displays the previous line in the history
> rather
On 1/21/18 12:23 PM, gaze...@xmission.com wrote:
> Bash Version: 4.3
> Patch Level: 48
> Release Status: release
>
>
>
> 2) "shopt -s nullglob" breaks filename tab completion. I found that tab
> completion
> no longer works after I do that "shopt" command.
Do you have bash-completion loaded
On 1/22/18 9:51 AM, Greg Wooledge wrote:
> On Sun, Jan 21, 2018 at 10:23:52AM -0700, gaze...@xmission.com wrote:
>> 1) In a script, when you kill a process, you get a terminal style message
>> about the process being killed. See below for further description.
>
> Here'
On Sun, Jan 21, 2018 at 10:23:52AM -0700, gaze...@xmission.com wrote:
> 1) In a script, when you kill a process, you get a terminal style message
> about the process being killed. See below for further description.
Here's a simpler reproducer (no need for external symlinks or killall
referenced in the Subject line above) is the
most
vexing, but all 3 are interesting.
1) In a script, when you kill a process, you get a terminal style message
about the process being killed. See below for further description.
2) "shopt -s nullglob" breaks filename tab completi
