unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: `guile-debugging' feature requests
Date: Mon, 04 Sep 2006 08:01:39 +0100	[thread overview]
Message-ID: <87d5ac9kto.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87psgwaz2w.fsf@laas.fr> ( Ludovic Courtès's message of "Mon, 26 Jun 2006 14:19:51 +0200")

ludovic.courtes@laas.fr (Ludovic Courtès) writes:

> I'm not an Emacs expert, so I'm afraid I won't be able to provide you
> with the exact patch needed to make it work.  ;-)
>
> `hippie-expand' works by calling the functions listed in
> `hippie-expand-try-functions-list' which is documented as follows:
>
>   The list of expansion functions tried in order by `hippie-expand'.  To
>   change the behavior of `hippie-expand', remove, change the order of,
>   or insert functions in this list.
>
> These should be one-argument functions that are passed a previous
> completion result.  Hippie provides a number of such functions out of
> the box: `try-complete-file-name', `try-complete-lisp-symbol', etc.
>
> Unfortunately, from a quick look at `hippie-exp.el', it seems that these
> functions pass their result by mutating `he-expand-list' which is not
> exported.  Thus, in order to implement hippie-compatible completion
> functions, either hippie-expand has to be adapted, or your own
> completion function has to be made part of hippie-expand (which it not
> possible in your case).  :-(

I just took a quick look at this.  In Emacs 21.4
hippie-expand-try-functions-list is "exported" by a defcustom:

(defcustom hippie-expand-try-functions-list
  '(try-complete-file-name-partially
    try-complete-file-name
    ...))

So I think all that's needed here is to write a
gds-try-complete-for-hippie-expand function, then document that you
(the user) can add this to hippie-expand-try-functions-list.

Apart from figuring out the calling convention for a try-complete
function, this looks pretty simple; I'll report back soon.

Regards,
     Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2006-09-04  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:58 `guile-debugging' feature requests Ludovic Courtès
2006-06-23 13:31 ` Neil Jerram
2006-06-26 12:19   ` Ludovic Courtès
2006-09-04  7:01     ` Neil Jerram [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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d5ac9kto.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.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.
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).