unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chming <chming@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: try-expand-dabbrev weird behavior when "No further expansions  found"
Date: Wed, 2 Dec 2009 15:12:53 -0800	[thread overview]
Message-ID: <ab4823ab0912021512h363a7ce7ta4ef3188a5a2662a@mail.gmail.com> (raw)
In-Reply-To: <ab4823ab0912021203m5e376a5chc800d3450fb362c0@mail.gmail.com>

I reverted the change of hippie-exp.el@1.43 back to @1.42. It works now.

Could someone double check this change?

Thanks,

Ming

On Wed, Dec 2, 2009 at 12:03 PM, Chming <chming@gmail.com> wrote:
> Hi all,
>
> My emacs is updated the latest version from cvs. When I use
> try-expand-dabbrev with M-/, if "No further expansions found" happens,
> the cursor will jump to some other place. The following is my setting
> about the dabbrev. Does someone know if something is wrong?
>
> Thanks,
>
> Ming
>
> (setq hippie-expand-try-functions-list
>      '(
>        try-expand-dabbrev
>        try-expand-dabbrev-visible
>        try-expand-dabbrev-all-buffers
>        try-expand-dabbrev-from-kill
>        try-expand-list
>        try-expand-list-all-buffers
>        try-expand-line
>        try-expand-line-all-buffers
>        try-expand-all-abbrevs
>        try-complete-file-name-partially
>        try-complete-file-name
>        try-expand-whole-kill
>        )
>      )
> (eval-after-load "dabbrev" '(defalias 'dabbrev-expand 'hippie-expand))
> (setq dabbrev-case-fold-search t)
> (setq dabbrev-case-replace t)
> (setq dabbrev-abbrev-skip-leading-regexp "[^ ]*[<>=*]")
> (setq dabbrev-abbrev-char-regexp "\\sw\\|\\s_")
>




  reply	other threads:[~2009-12-02 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 20:03 try-expand-dabbrev weird behavior when "No further expansions found" Chming
2009-12-02 23:12 ` Chming [this message]
2009-12-03  1:34   ` try-expand-dabbrev weird behavior when "No further expansions Stefan Monnier

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=ab4823ab0912021512h363a7ce7ta4ef3188a5a2662a@mail.gmail.com \
    --to=chming@gmail.com \
    --cc=emacs-devel@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.
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).