From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Suggested PATCH: Reorder README a little
Date: Mon, 11 Jun 2001 16:53:16 +0000 [thread overview]
Message-ID: <1010611165317.ZM23036@candle.brasslantern.com> (raw)
Generally, bug reports should not include "reporter" output unless the bug
can *not* be reproduced with "zsh -f". Anybody disagree?
Index: README
===================================================================
diff -c -r1.2 README
--- README 2001/06/01 16:44:28 1.2
+++ README 2001/06/11 16:51:13
@@ -141,15 +141,15 @@
and coordinated by Peter Stephenson <coordinator@zsh.org>. Please send
any feedback and bugs reports to <zsh-workers@sunsite.dk>.
-There is a script "reporter" in the subdirectory Util which will print
-out your current shell environment/setup. If you report a bug, please
-use this script and include the output from sourcing this file. This way,
-the problem you are reporting can be recreated.
-
-You can help even more if you can reproduce the bug starting zsh with
+Reports are most helpful if you can reproduce the bug starting zsh with
the -f option. This skips the execution of local startup files except
/etc/zshenv. If a bug occurs only when some options set try to locate
the option which triggers the bug.
+
+There is a script "reporter" in the subdirectory Util which will print out
+your current shell environment/setup. If you cannot reproduce the bug
+with "zsh -f", use this script and include the output from sourcing this
+file. This way, the problem you are reporting can be recreated.
The known bugs in zsh are listed in the file Etc/BUGS. Check this as
well as the Frequently Asked Questions (FAQ) list before sending a bug
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next reply other threads:[~2001-06-11 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 16:53 Bart Schaefer [this message]
2001-06-11 18:38 ` Bugs list Andrej Borsenkow
2001-06-12 9:24 ` Bart Schaefer
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=1010611165317.ZM23036@candle.brasslantern.com \
--to=schaefer@candle.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).