From: Chong Yidong <cyd@stupidchicken.com>
To: Bob Nnamtrop <bobnnamtrop@gmail.com>
Cc: 9038@debbugs.gnu.org
Subject: bug#9038: 24.0.50; limit expand-abbrev in viper mode state change
Date: Sat, 09 Jul 2011 15:32:46 -0400 [thread overview]
Message-ID: <87r55zw8pt.fsf@stupidchicken.com> (raw)
In-Reply-To: <CAKV0tLMrKBjxizBzrpOv3dxQzKUmHK+pPB-3rXRsR8abTSExEg@mail.gmail.com> (Bob Nnamtrop's message of "Sat, 9 Jul 2011 11:09:52 -0600")
Bob Nnamtrop <bobnnamtrop@gmail.com> writes:
> Changing from viper insert state to vi state (called "changing state"
> below for brevity) causes expand-abbrev to run if abbrev's are turned
> on. This is good but I think the rule for if an abbrev is expanded
> should agree with the rule in self-insert-command when in insert mode.
> Thus "changing state" should only attempt to expand abbrev if and only
> if the previous char has word syntax. This is easily achieved with the
> following patch (against trunk):
Looks reasonable; checked into trunk. Thanks.
prev parent reply other threads:[~2011-07-09 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 17:09 bug#9038: 24.0.50; limit expand-abbrev in viper mode state change Bob Nnamtrop
2011-07-09 19:32 ` Chong Yidong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r55zw8pt.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=9038@debbugs.gnu.org \
--cc=bobnnamtrop@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).