zsh-workers
 help / color / mirror / code / Atom feed
From: Itai Seggev <is@cs.hmc.edu>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: get _files to work/bug in subversion in completion
Date: Sat, 9 Jul 2005 14:27:46 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.58.0507091420480.22209@turing> (raw)
In-Reply-To: <1050709174917.ZM17821@candle.brasslantern.com>

On Sat, 9 Jul 2005, Bart Schaefer wrote:

> On Jul 8, 11:07pm, Itai Seggev wrote:
> }
> } In particular, if I do a
> }
> } svn ci -F [tab]
> }
> } to try to get a list of of possible files to use as my changelog, zsh
> } never completes anything. I think this is a bug...
>
> It's a bug in _subversion, I think.
>
> Try adding
>
>    local ret=1
>
> somewhere near the top of the function _svn_subcommand in the file
> Completion/Unix/Command/_subversion and see if that fixes it.  Or better
> yet, delete
>
>        && ret=0
>
>    return ret
>
> from the end of that function, leaving just the _arguments call.  The
> same goes for _svnadmin_subcommand, for that matter.

I tried both of these solutions. (I assume that all I had to do was edit
the files and then ssh in to make use of the new definitions.) Neither
seemed to have any effect. Other suggestions?

--
Itai

Itai Seggev, University of Chicago, Department of Physics

In 1997 a group of programmers started writing a desktop environment
to fix a travesty they didn't create.  Their program promptly found
its way onto un*x systems everywhere. Today, still opposed by a
software monopolist, they survive as soldiers of fortune.  If you share
their vision, if you know you can help, and if you can connect to
internet, maybe you can join... the K-Team.


      reply	other threads:[~2005-07-09 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  6:07 Itai Seggev
2005-07-09 17:49 ` Bart Schaefer
2005-07-09 21:27   ` Itai Seggev [this message]

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.GSO.4.58.0507091420480.22209@turing \
    --to=is@cs.hmc.edu \
    --cc=schaefer@brasslantern.com \
    --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).