From: cons <consspam@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: dabbrev problem...
Date: Thu, 13 Sep 2007 12:51:38 -0700 [thread overview]
Message-ID: <1189713098.097690.296390@22g2000hsm.googlegroups.com> (raw)
I really like and use the dabbrev feature of copying the following
words with SPC M-/ SPC M-/ ... etc. So much infact that I want to do a
command that saves me that extra SPC-press. Basically, the command
should just execute 'dabbrev-expand' if there is a SPC before point,
or else insert a SPC and then execute 'dabbrev-expand':
(defun complete-further (arg)
"Insert space if necessary and then call dabbrev-expand."
(interactive "*P")
(if (not (eq (preceding-char) ?\s))
(insert ?\s))
(dabbrev-expand arg))
The only problem is that it ain't working :(
What am I doing wrong?
Best regards,
/Stefan
next reply other threads:[~2007-09-13 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:51 cons [this message]
2007-09-14 10:20 ` dabbrev problem Andreas Röhler
[not found] ` <mailman.853.1189765115.18990.help-gnu-emacs@gnu.org>
2007-09-14 12:39 ` cons
2007-09-14 14:24 ` Andreas Röhler
[not found] ` <mailman.871.1189779748.18990.help-gnu-emacs@gnu.org>
2007-09-14 20:12 ` cons
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=1189713098.097690.296390@22g2000hsm.googlegroups.com \
--to=consspam@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).