unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Henrik Enberg <henrik.enberg@telia.com>
Cc: Michael Kifer <kifer@cs.sunysb.edu>, emacs-devel@gnu.org
Subject: Re: Completion with M-Tab for custom type 'directory
Date: Sun, 03 Jul 2005 23:02:19 +0200	[thread overview]
Message-ID: <87mzp34n8k.fsf@rocksteady.printf.se> (raw)
In-Reply-To: <42C84855.6040906@student.lu.se> (Lennart Borgman's message of "Sun, 03 Jul 2005 22:19:33 +0200")

Lennart Borgman <lennart.borgman.073@student.lu.se> writes:

> Henrik Enberg wrote:
>
>>Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>>
>>  
>>
>>>Does this work? On w32 I can of course not do M-Tab, but I have another
>>>meta-key to, but that does not seem to work.
>>>    
>>>
>>
>>Doesn't ESC-Tab work on windows?
>>  
>>
> Yes, but I saw some strange things. First I got into that "show initial
> lisp value" state. Then I did not do that any more, but I really do not
> understand why. I start with (customize-option 'my-opt).
>
> Then, in the correct state, I put the point  to the beginning of the
> field. If I then type Esc Tab I get an "Wrong type argument: stringp,
> nil".

Hmm, I get a huge list of symbols to complete against. Even at the
beginning of the field without deleting the initial "nil".

> After moving the point a bit to the right I actually have completion
> working.  But, ...
>
> 1) If there are spaces in the directory name it stops working.

> 2) I can not click with the right button to select from the list. I have
>    set w32-num-buttons to 2. Should not the right button then be
>    mouse-2?

I don't know about windows, but on Unix-likes, the right button would
most probably be button 3.  With a 2 button mouse, you'd either have to
hit both buttons (or the scroll wheel if one exists) to get mouse-2.

> 3) I can not select with RET in the selection list (because viper is
>    active in the completion buffer).

This sounds probably a viper problem.  I don't think it's a good idea to
rebind standard keys in emacs just to get viper working.  Possibly
viper.el should override keys that gets in the way.

  parent reply	other threads:[~2005-07-03 21:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 19:03 Completion with M-Tab for custom type 'directory Lennart Borgman
2005-07-03 19:53 ` Henrik Enberg
2005-07-03 20:19   ` Lennart Borgman
2005-07-03 20:49     ` Lennart Borgman
2005-07-03 21:02     ` Henrik Enberg [this message]
2005-07-03 21:24       ` Lennart Borgman
2005-07-03 21:46         ` Luc Teirlinck
2005-07-03 21:57           ` Lennart Borgman
2005-07-03 21:52         ` Henrik Enberg
2005-07-03 22:00         ` Jason Rumney
2005-07-03 22:07           ` Lennart Borgman
2005-07-03 22:40             ` David Kastrup
2005-07-03 23:14               ` Lennart Borgman
2005-07-03 23:59                 ` Luc Teirlinck
2005-07-04  0:20                 ` David Kastrup
2005-07-04  0:43                 ` Henrik Enberg

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=87mzp34n8k.fsf@rocksteady.printf.se \
    --to=henrik.enberg@telia.com \
    --cc=emacs-devel@gnu.org \
    --cc=kifer@cs.sunysb.edu \
    /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).