From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: emacs-26 0643952: Add documentation to ecomplete.el
Date: Thu, 18 Jan 2018 11:49:35 +0100 [thread overview]
Message-ID: <87bmhrtpa8.fsf@gmx.de> (raw)
In-Reply-To: <20180117105628.5272622EE4@vcs0.savannah.gnu.org> (Lars Ingebrigtsen's message of "Wed, 17 Jan 2018 05:56:28 -0500 (EST)")
larsi@gnus.org (Lars Ingebrigtsen) writes:
> +;; (ecomplete-add-item "larsi@gnus.org" 'mail "Lars Magne Ingebrigtsen <larsi@gnus.org>")
> +;;
> +;; the "larsi@gnus.org" entry will then be updated with that new STRING.
> +
> +;; The interface functions are `ecomplete-add-item' and
> +;; `ecomplete-display-matches', while `ecomplete-setup' should be
> +;; called to read the .ecompleterc file, and `ecomplete-save' are
> +;; called to save the file.
Nice. I will check, whether I could add this to Tramp. Something like
(ecomplete-add-item "remote-host" 'tramp "/ssh:user@remote-host:")
One inconvenience for me is the hard coding of keys in
`overriding-local-map' with lambda functions. I would prefer to have it
customizable, for instance in order to use <up> and <down> instead of
M-n and M-p.
Best regards, Michael.
next parent reply other threads:[~2018-01-18 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180117105626.27351.89699@vcs0.savannah.gnu.org>
[not found] ` <20180117105628.5272622EE4@vcs0.savannah.gnu.org>
2018-01-18 10:49 ` Michael Albinus [this message]
2018-01-18 10:58 ` emacs-26 0643952: Add documentation to ecomplete.el Lars Ingebrigtsen
2018-01-18 11:10 ` Michael Albinus
2018-01-18 11:12 ` Lars Ingebrigtsen
2018-01-18 12:19 ` Michael Albinus
2018-01-18 12:30 ` Lars Ingebrigtsen
2018-01-18 22:40 ` Karl Fogel
2018-01-25 17:20 ` ecomplete and company (was: emacs-26 0643952: Add documentation to ecomplete.el) 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmhrtpa8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.