From: Eric Hanchrow <offby1@blarg.net>
Subject: Re: Fwd: version 1.84 of cperl-mode.el takes away my control over abbrevs
Date: Sun, 14 Jan 2007 11:56:08 -0800 [thread overview]
Message-ID: <874pqtjsbr.fsf@offby1.atm01.sea.blarg.net> (raw)
In-Reply-To: E1H5uc1-0008WH-EZ@fencepost.gnu.org
>>>>> "Richard" == Richard Stallman <rms@gnu.org> writes:
Glen> I think all you can do is define the abbrevs you
Glen> don't want to expand to themselves, rather than
Glen> deleting them. A bit ugly.
Richard> This solution seems natural to me, not ugly, so I think
Richard> we should just document it.
Richard> Would you like to try that?
--- cperl-mode.el 09 Dec 2006 22:54:46 -0800 1.84
+++ cperl-mode.el 14 Jan 2007 11:54:32 -0800
@@ -352,7 +352,15 @@
(defcustom cperl-electric-keywords nil
"*Not-nil (and non-null) means keywords are electric in CPerl.
-Can be overwritten by `cperl-hairy' if nil."
+Can be overwritten by `cperl-hairy' if nil.
+
+Uses abbrev-mode to do the expansion. If you want to use your
+own abbrevs in cperl-mode, but do not want keywords to be
+electric, you must redefine cperl-mode-abbrev-table: do
+\\[edit-abbrevs], search for cperl-mode-abbrev-table, and, in
+that paragraph, delete the words that appear at the ends of lines, and
+that begin with \"cperl-electric\".
+"
:type '(choice (const null) boolean)
:group 'cperl-affected-by-hairy)
--
A special circle of hell should be reserved for video
executives who place previews at the beginnings of DVDs.
-- Roger Ebert
next prev parent reply other threads:[~2007-01-14 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mz4okjsz.fsf@offby1.atm01.sea.blarg.net>
2007-01-12 23:35 ` Fwd: version 1.84 of cperl-mode.el takes away my control over abbrevs Glenn Morris
2007-01-14 1:56 ` Richard Stallman
2007-01-14 19:56 ` Eric Hanchrow [this message]
2007-01-16 0:37 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874pqtjsbr.fsf@offby1.atm01.sea.blarg.net \
--to=offby1@blarg.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.