On 6/8/20 6:54 PM, bash...@jonkmans.nl wrote:
> Bash Version: 4.4
> Patch Level: 20
> Release Status: release
>
> Description:
> Got a core dump (segmentation fault) when i type: Alt-. Alt-1 Alt-.
You tried to redo `.'. The way this happens is you are in command mode,
run that yank-last-ar
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
Date:Mon, 8 Jun 2020 09:34:34 -0400
From:Greg Wooledge
Message-ID: <20200608133434.ga4...@eeg.ccf.org>
| Those are not standard vi commands, as far as I can tell.
You're right, they're not.
| g$ acts just like $.
| g0 acts just like 0.
| gE acts just like E
On 6/8/20 10:44 AM, Eli Schwartz wrote:
> Well, Greg does have a pretty good point (which is a point I for one
> prioritize in my decision process for "do I personally recommend the use
> of set -e") in that another part of the issue is its doing different
> things across point releases of a shell
On 6/8/20 10:02 AM, Chet Ramey wrote:
> On 6/8/20 7:24 AM, Greg Wooledge wrote:
>> This is part of the set -e nightmare, which is what we keep trying to
>> get you (and everyone else) to understand.
>
> Most of the issue with `set -e' is folks not understanding when it's
> not in effect.
Well, Gr
On 6/7/20 9:28 PM, Dan Shearer wrote:
> Some g commands are implemented, but incorrectly. Examples:
> * g0 is equivalent to 0, rather than 'beginning of screen line when wrapped'
> * g$ is equivalent to $, rather than 'end of screen line when wrapped'
>
> Other g commands are not implemented, just
On 6/8/20 7:24 AM, Greg Wooledge wrote:
> On Mon, Jun 01, 2020 at 05:28:20PM +0700, Robert Elz wrote:
>> in this case:
>>
>> | You're merely the latest person to discover that this applies to you:
>> | http://mywiki.wooledge.org/BashFAQ/105
>>
>> doesn't really apply - the cases reported are si
On Mon, Jun 08, 2020 at 02:28:05AM +0100, Dan Shearer wrote:
> Some g commands are implemented, but incorrectly. Examples:
> * g0 is equivalent to 0, rather than 'beginning of screen line when wrapped'
> * g$ is equivalent to $, rather than 'end of screen line when wrapped'
>
> Other g commands ar
Some g commands are implemented, but incorrectly. Examples:
* g0 is equivalent to 0, rather than 'beginning of screen line when wrapped'
* g$ is equivalent to $, rather than 'end of screen line when wrapped'
Other g commands are not implemented, just ignored. Examples:
* gM is ignored, rather than
On Mon, Jun 01, 2020 at 05:28:20PM +0700, Robert Elz wrote:
> in this case:
>
> | You're merely the latest person to discover that this applies to you:
> | http://mywiki.wooledge.org/BashFAQ/105
>
> doesn't really apply - the cases reported are simply bugs in bash,
> a shell implementing -e c
10 matches
Mail list logo
