zsh-users
 help / color / mirror / code / Atom feed
From: William Scott <wgscott@chemistry.ucsc.edu>
To: Nikolai Weibull <mailing-lists.zsh-users@rawuncut.elitemail.org>
Cc: zsh-users <zsh-users@sunsite.dk>
Subject: Re: Adding a prefix to certain filename completions
Date: Tue, 5 Jul 2005 08:09:47 -0700 (PDT)	[thread overview]
Message-ID: <Pine.OSX.4.58.0507050807220.17701@vanunu.ucsc.edu> (raw)
In-Reply-To: <20050705080757.GB5333@puritan.pnetwork>


Hi Nikolai:

This expands on my previous reply:


#!/bin/zsh -f
#  newvim

inputfilearray=( "$@" )

LIMIT=$#
for ((i = 1; i <= $LIMIT; i++ )) do
        eval file="\$$i"
        if [[ -f $inputfilearray[i] &&
                   $inputfilearray[i] == "$(basename $inputfilearray[i])" ]]
        then
             inputfilearray[i]="./$inputfilearray[i]"
        else
             :
        fi
done

command vim "$inputfilearray"




There is probably an easier way, but it works.

Bill





On Tue, 5 Jul 2005, Nikolai Weibull wrote

> William Scott wrote:
>
> > If I am understanding the question correctly, I think you need
> > something like
> >
> > compadd -P "./"
> >
> > but I don't know if that will cure the problem with the + signs.
>
> Adding the ./ prefix certainly helps, as Vim won't see the + signs as
> special any more.  However, the solution I was looking for would
> automatically add the ./ prefix when completing a filename beginning
> with a + (perhaps only if vim is the command in command position).  So
> I need even more basic information than the compadd command-line.  I was
> hoping it could be done using zstyles.
>
> > Born in Chicago, IL USA; currently residing in Santa Crud, CA
>
> :-),
>         nikolai
>
> --
> Nikolai Weibull: now available free of charge at http://bitwi.se/!
> Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
> main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
>


  reply	other threads:[~2005-07-05 15:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 19:37 Nikolai Weibull
2005-07-05  0:13 ` William Scott
2005-07-05  8:07   ` Nikolai Weibull
2005-07-05 15:09     ` William Scott [this message]
2005-07-05 15:23     ` William Scott
2005-07-05  4:23 ` Thomas Köhler
2005-07-05  8:09   ` Nikolai Weibull
2005-07-05 14:25     ` William Scott
2005-07-05 17:28       ` Nikolai Weibull
2005-07-05 16:56         ` John Reese
2005-07-05 17:07         ` William Scott
2005-07-06  5:00       ` Bart Schaefer
2005-07-06 11:31         ` Nikolai Weibull
2005-07-07  2:02           ` Nikolai Weibull
2005-07-07  5:40             ` Bart Schaefer
2005-07-07  7:21               ` Dan Nelson
2005-07-07 10:58               ` Nikolai Weibull
2005-07-07 11:18                 ` Peter Stephenson
2005-07-07 11:58                   ` Doug Kearns
2005-07-07 12:11                   ` Nikolai Weibull
2005-07-07 12:54                     ` Peter Stephenson
2005-07-07 19:00                       ` Thomas Köhler
2005-07-07 14:51                 ` William Scott
2005-07-07 15:57                   ` Nikolai Weibull
2005-07-08  1:24                 ` Bart Schaefer
2005-07-08 10:12                   ` Nikolai Weibull
2005-07-05 17:01 ` Bart Schaefer
2005-07-05 19:14   ` Nikolai Weibull

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=Pine.OSX.4.58.0507050807220.17701@vanunu.ucsc.edu \
    --to=wgscott@chemistry.ucsc.edu \
    --cc=mailing-lists.zsh-users@rawuncut.elitemail.org \
    --cc=zsh-users@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).