From: Clint Adams <schizo@debian.org>
To: Morita Sho <morita-pub-en-debian@inz.sakura.ne.jp>,
501248@bugs.debian.org
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#501248: /usr/share/zsh/functions/Completion/compinstall: compinstall doesn't keep the previous configuration.
Date: Mon, 6 Oct 2008 19:47:00 +0000 [thread overview]
Message-ID: <20081006194700.GC5175@scru.org> (raw)
In-Reply-To: <20081005223201.17132.55292.reportbug@debian>
On Mon, Oct 06, 2008 at 07:32:01AM +0900, Morita Sho wrote:
> Running compinstall will lost the setting that is previously configured using compinstall.
>
> How to reproduce:
>
> % compinstall
> ... Change some settings and exit.
> % compinstall
> ... All settings are reset to the default.
>
> A message "Starting a new completion configuration from scratch." will be
> appears for every compinstall execution.
>
>
> It seems that there is a small typo in line 128 of
> /usr/share/zsh/functions/Completion/compinstall.
>
> [[ -z $newifile || ! -f $newfile ]] && foundold=false
> ^^^^^^^
> There is no such variable named $newfile in this file.
> I think it is a typo ("i" is missing) and it should be $newifile.
Thanks.
Index: Completion/compinstall
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/compinstall,v
retrieving revision 1.13
diff -u -r1.13 compinstall
--- Completion/compinstall 8 Jun 2008 17:53:54 -0000 1.13
+++ Completion/compinstall 6 Oct 2008 19:46:14 -0000
@@ -125,7 +125,7 @@
newifile=$PWD/$newifile
print "[Not absolute path: updating to $newifile]"
fi
- [[ -z $newifile || ! -f $newfile ]] && foundold=false
+ [[ -z $newifile || ! -f $newifile ]] && foundold=false
else
print "I haven't found any existing completion definitions.
If you have some already defined by compinstall, edit the name of the
parent reply other threads:[~2008-10-06 19:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20081005223201.17132.55292.reportbug@debian>]
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=20081006194700.GC5175@scru.org \
--to=schizo@debian.org \
--cc=501248@bugs.debian.org \
--cc=morita-pub-en-debian@inz.sakura.ne.jp \
--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).