zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: Vincent Lefevre <vincent@vinc17.org>, 413521@bugs.debian.org
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#413521: typo in zshoptions(1) man page
Date: Mon, 5 Mar 2007 12:32:58 -0500	[thread overview]
Message-ID: <20070305173258.GA5529@scowler.net> (raw)
In-Reply-To: <20070305154547.GA4288@vin.lip.ens-lyon.fr>

>    HIST_SAVE_BY_COPY
>       When  the  history  file  is re-written, we normally write out a
>       copy of the file named $HISTFILE.new and then rename it over the
>       old  one.  However, if this option is unset, we instead truncate
>       the old history file and write out the new version in-place.  If
>       one  of  the  history-appending  options is enabled, this option
>       only has an affect when the enlarged history file  needs  to  be
>                   ^^^^^^
> 
> should be "effect".

Index: Doc/Zsh/options.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/options.yo,v
retrieving revision 1.52
diff -u -r1.52 options.yo
--- Doc/Zsh/options.yo	12 Feb 2007 16:43:41 -0000	1.52
+++ Doc/Zsh/options.yo	5 Mar 2007 17:32:16 -0000
@@ -616,7 +616,7 @@
 the file named $HISTFILE.new and then rename it over the old one.
 However, if this option is unset, we instead truncate the old
 history file and write out the new version in-place.  If one of the
-history-appending options is enabled, this option only has an affect
+history-appending options is enabled, this option only has an effect
 when the enlarged history file needs to be re-written to trim it
 down to size.  Disable this only if you have special needs, as doing
 so makes it possible to lose history entries if zsh gets interrupted


           reply	other threads:[~2007-03-05 17:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070305154547.GA4288@vin.lip.ens-lyon.fr>]

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=20070305173258.GA5529@scowler.net \
    --to=schizo@debian.org \
    --cc=413521@bugs.debian.org \
    --cc=vincent@vinc17.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).