zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: PATCH: Re: Correction of files after ~/
Date: Fri, 23 Mar 2001 10:53:05 +0100 (MET)	[thread overview]
Message-ID: <200103230953.KAA07731@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Thu, 22 Mar 2001 17:41:52 +0000


Peter Stephenson wrote:

> Correction/approximation of filenames which begin with a `~' appears to be
> broken.  I think this has happened before.  I'm not aware of any styles I
> have that would affect this (note careful phrasing).

This was dependend on the matchers one used.  Complicated ones could
lead _path_files to end up with the uncorrected word as an `expanded'
path which made _path_files return zero...

> Could somebody who understands this put some tests with leading ~'s into
> the completion part of the test suite?

Since this was really caused by ~ being expanded to the home directory 
I'm not sure how to do that.

Bye
 Sven

Index: Completion/Core/_path_files
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/_path_files,v
retrieving revision 1.36
diff -u -r1.36 _path_files
--- Completion/Core/_path_files	2001/02/13 09:23:34	1.36
+++ Completion/Core/_path_files	2001/03/23 09:52:22
@@ -364,8 +364,10 @@
 	    else
 	      exppaths=( "$exppaths[@]" ${^tmp2}/${tpre}${tsuf} )
 	    fi
-          else
+          elif [[ ${tpre}${tsuf} = */* ]]; then
 	    exppaths=( "$exppaths[@]" ${tpre}${tsuf} )
+
+	    ### this once was in an `else' (not `elif')
 	  fi
         fi
         continue 2

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


             reply	other threads:[~2001-03-23  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23  9:53 Sven Wischnowsky [this message]
2001-03-23 13:57 Sven Wischnowsky

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=200103230953.KAA07731@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.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).