zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: tricky.c (was messages from Andrej and Bart)
Date: Wed, 10 Mar 1999 17:32:28 +0100 (MET)	[thread overview]
Message-ID: <199903101632.RAA17756@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Bart Schaefer's message of Wed, 10 Mar 1999 08:20:52 -0800 (PST)


Bart Schaefer wrote:

>  > The problem is that after expansion, the code can't find out
>  > what came from the expansion in cases like `${foo}x<TAB>'.
> 
> Hrm ... so what was happening in the old completion code in this case?

Thinks went utterly wrong, even worse than what the new code did
before the patch: 

  % echo $PWD:h<TAB>
  % echwischnow/

... of course, the result depends on the last pathname component.

>  > So the patch just uses the expanded prefix if it has the problem that
>  > the expanded prefix contains slashes and the original string doesn't.
>  > Maybe a better solution would be to do nothing in such cases.
> 
> Does this apply only to file completion?  What if the expansion happens
> in some other context where slashes aren't special?

The error occured only in the code that is used when completing
filenames. In other contexts the expanded prefix would be used and
completed.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-03-10 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-10 16:32 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-10  9:25 Sven Wischnowsky
1999-03-10 16:20 ` Bart Schaefer

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=199903101632.RAA17756@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).