all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-26 0643952: Add documentation to ecomplete.el
Date: Thu, 18 Jan 2018 11:58:21 +0100	[thread overview]
Message-ID: <m3inbza0xe.fsf@gnus.org> (raw)
In-Reply-To: <87bmhrtpa8.fsf@gmx.de> (Michael Albinus's message of "Thu, 18 Jan 2018 11:49:35 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> 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.

Hm, yes; doing it via a traditional keymap would make more sense.  (And
<up> and <down> should be bound by default, I think.)  I can't recall
why I did it that way (if I was the one that did it).  Hm...  probably
just because it was easier since it defines those lambdas...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2018-01-18 10:58 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   ` emacs-26 0643952: Add documentation to ecomplete.el Michael Albinus
2018-01-18 10:58     ` Lars Ingebrigtsen [this message]
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=m3inbza0xe.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.