From: "Andreas Röhler" <andreas.roehler@online.de>
To: help-gnu-emacs@gnu.org
Subject: Re: dabbrev problem...
Date: Fri, 14 Sep 2007 12:20:55 +0200 [thread overview]
Message-ID: <200709141220.56405.andreas.roehler@online.de> (raw)
In-Reply-To: <1189713098.097690.296390@22g2000hsm.googlegroups.com>
Am Donnerstag, 13. September 2007 21:51 schrieb cons:
> (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))
What about this:
(defun dabbrev-expand-before-point (arg)
(interactive "*p")
(skip-chars-backward " \t\r\n\f")
(dabbrev-expand arg)
(unless (eq (preceding-char) ?\ )
(insert " ")))
Andreas Röhler
next prev parent reply other threads:[~2007-09-14 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:51 dabbrev problem cons
2007-09-14 10:20 ` Andreas Röhler [this message]
[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=200709141220.56405.andreas.roehler@online.de \
--to=andreas.roehler@online.de \
--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).