Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Robert Elz Newsgroups: gnu.bash.bug Subject: Re: Vi mode and g commands Date: Mon, 08 Jun 2020 22:23:58 +0700 Lines: 27 Approved: bug-bash@gnu.org Message-ID: References: <20200608133434.GA4133@eeg.ccf.org> <16732.1591629838@jinx.noi.kre.to> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1591629887 32505 209.51.188.17 (8 Jun 2020 15:24:47 GMT) X-Complaints-To: action@cs.stanford.edu Cc: Dan Shearer , bug-bash@gnu.org To: Greg Wooledge Envelope-to: bug-bash@gnu.org In-Reply-To: <20200608133434.GA4133@eeg.ccf.org> Received-SPF: permerror client-ip=2001:3c8:9009:181::2; envelope-from=kre@munnari.OZ.AU; helo=munnari.OZ.AU X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <16732.1591629838@jinx.noi.kre.to> X-Mailman-Original-References: <20200608133434.GA4133@eeg.ccf.org> Xref: csiph.com gnu.bash.bug:16372 Date: Mon, 8 Jun 2020 09:34:34 -0400 From: Greg Wooledge Message-ID: <20200608133434.GA4133@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 None of these are surprising, or shouldn't be, there's no 'g' command in vi, the 'g' is just an error (should really flash the screen or something) - then whatever follows it is just the next command. | I see no evidence that 'g' is even a meaningful keystroke in real vi. | Maybe that's why vim chose it as the prefix for so many of their | extension commands. That's correct, there is no 'g' in vi, and as an explanation, that makes sense. kre