From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Cc: 279417-forwarded@bugs.debian.org
Subject: [lunz@falooley.org: Bug#279417: zsh: "make" completion issues "bad option" warnings for some Makefiles]
Date: Tue, 2 Nov 2004 18:13:04 -0500 [thread overview]
Message-ID: <20041102231304.GA15509@scowler.net> (raw)
Attachment mentioned in the forwarded message at the bottom is at
http://bugs.debian.org/cgi-bin/bugreport.cgi/Makefile?bug=279417&msg=3&att=1
This prevents the warnings, though I don't know if there's a deeper
problem occurring here.
Index: Completion/Unix/Command/_make
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_make,v
retrieving revision 1.11
diff -u -r1.11 _make
--- Completion/Unix/Command/_make 12 Oct 2004 20:05:13 -0000 1.11
+++ Completion/Unix/Command/_make 2 Nov 2004 23:09:54 -0000
@@ -38,7 +38,7 @@
;;
esac
else
- print $ret
+ print -- $ret
return
fi
done
----- Forwarded message from Jason Lunz <lunz@falooley.org> -----
Date: Tue, 02 Nov 2004 17:31:05 -0500
From: Jason Lunz <lunz@falooley.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#279417: zsh: "make" completion issues "bad option" warnings for some Makefiles
Package: zsh
Version: 4.2.1-9
Severity: normal
For some Makefiles, trying to complete make targets pollutes the screen
with error messages from within the completion code. For example:
[barton](2) % make expandVars:36: bad option: -I
expandVars:36: bad option: -W
expandVars:36: bad option: -h
make
completions of type: file
Makefile x
The attached Makefile snippet reproduces the above behavior.
Jason
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.10-rc1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
----- End forwarded message -----
next reply other threads:[~2004-11-02 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 23:13 Clint Adams [this message]
2004-11-10 17:27 ` Wayne Davison
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=20041102231304.GA15509@scowler.net \
--to=clint@zsh.org \
--cc=279417-forwarded@bugs.debian.org \
--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).