From: "Florian Kaufmann" <sensorflo@gmail.com>
Subject: Re: how to make dabbrev expand to 2nd/3rd/... last occurence?
Date: 13 Oct 2006 02:46:05 -0700 [thread overview]
Message-ID: <1160732765.697697.126990@m73g2000cwd.googlegroups.com> (raw)
In-Reply-To: <lnmz80ka8z.fsf@mfk.tu-dresden.de>
> ,----[ C-h f dabbrev-expand RET ]
> | dabbrev-expand is an interactive autoloaded Lisp function in `dabbrev'.
...
> | If the cursor has not moved from the end of the previous expansion and
> | no argument is given, replace the previously-made expansion
> | with the next possible expansion not yet tried.
Thank you Holger
Tststs, I'm sorry to have asked a question that is so obviously in the
help. I actually read the help before I posted my question, but
obviously very carelessly.
Flo
prev parent reply other threads:[~2006-10-13 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 12:53 how to make dabbrev expand to 2nd/3rd/... last occurence? Florian Kaufmann
2006-10-12 15:36 ` Florian Kaufmann
2006-10-13 8:31 ` Holger Sparr
[not found] ` <lnmz80ka8z.fsf@mfk.tu-dresden.de>
2006-10-13 9:46 ` Florian Kaufmann [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=1160732765.697697.126990@m73g2000cwd.googlegroups.com \
--to=sensorflo@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.
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).