zsh-workers
 help / color / mirror / code / Atom feed
From: greg@alphatech.com (Greg Klanderman)
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@math.gatech.edu, greg@alphatech.com
Subject: Re:  bug in 3.1.4 completion
Date: Wed, 4 Nov 1998 19:32:27 -0500 (EST)	[thread overview]
Message-ID: <13888.61979.554790.869235@catbus.alphatech.com> (raw)
In-Reply-To: <199811040904.KAA29172@beta.informatik.hu-berlin.de>


>>>>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
Sven> 
Sven> greg@alphatech.com wrote:

Thanks for the patch, I'll try it with 3.1.5 after you follow up
to Bart's question.


>> [how to improve complete-in-word]

Sven> That would be expand-or-complete-prefix with a little hacking (the remove-
Sven> the-matched-prefix-of-the-suffix part), not too hard.

OK, I implemented it as a shell function and it works nicely.
I'm having a suffix removal problem but that might be fixed 
by your patch.

>> While I'm on little nits, it would be nice if the FIGNORE variable
>> were not used when listing completions:

Sven> I'm not too sure about this one, since C-d should list the completions 
Sven> and if there are other matching files the ignored ones aren't
Sven> completions. If there are no other files fignore will be ignored and
Sven> the files will be listed. I could be convinced to list the ignored
Sven> files separately (this indeed may make sense).

I believe tcsh works as I suggest.  Not that that's a good reason 
to change, but it makes sense to me that if you're listing
completions, that you be shown everything that matches what you've
typed so far, because then you can get to an otherwise ignored file if 
you want.  This is pretty minor, I'm not going to argue it.

Sven> We got many requests for this. For 3.1.5 there is a proposed patch
Sven> that adds a generic way to control the matching behavior of
Sven> completion. With this you can get case-insensitive completion, partial 
Sven> word completion and several other things.

I'll look for it sometime in the future...

Hey, one more minor suggestion - if you abort a command you're typing
(C-c or C-g) it'd be nice to indicate that on the aborted line so it
doesn't look like you actually executed it.  Csh prints "^C" at the
end of the line, for example.

Greg


  parent reply	other threads:[~1998-11-05  0:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-04  9:04 Sven Wischnowsky
1998-11-04 17:31 ` Bart Schaefer
1998-11-04 17:59 ` Bart Schaefer
1998-11-05  0:32 ` Greg Klanderman [this message]
1998-11-05 16:12 ` Greg Klanderman
  -- strict thread matches above, loose matches on Subject: below --
1998-11-05 16:34 Sven Wischnowsky
1998-11-05 10:47 Sven Wischnowsky
1998-11-05  8:02 Sven Wischnowsky
1998-11-03 17:28 Greg Klanderman

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=13888.61979.554790.869235@catbus.alphatech.com \
    --to=greg@alphatech.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@math.gatech.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).