From owner-freebsd-doc Mon Jun 10 23:50:29 2002 Delivered-To: freebsd-doc@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C9B3637B412 for ; Mon, 10 Jun 2002 23:50:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g5B6o3t31758; Mon, 10 Jun 2002 23:50:03 -0700 (PDT) (envelope-from gnats) Date: Mon, 10 Jun 2002 23:50:03 -0700 (PDT) Message-Id: <200206110650.g5B6o3t31758@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Martin Heinen Subject: Re: docs/39089: Confusing part about setting/viewing environment vars in section 3.7 of the Handbook Reply-To: Martin Heinen Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/39089; it has been noted by GNATS. From: Martin Heinen To: Marc Fonvieille Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: docs/39089: Confusing part about setting/viewing environment vars in section 3.7 of the Handbook Date: Tue, 11 Jun 2002 08:46:26 +0200 On Mon, Jun 10, 2002 at 09:53:22AM +0200, Marc Fonvieille wrote: > Confusing part about setting/viewing environment vars in section 3.7 of > the Handbook. Telling that you can use setenv or export to view > variables is quite confusing for the *newbie* (the use of echo $VARNAME > is described below that part in that section). Agreed, using set/setenv to list variables is confusing, but it's a useful feature that we should mention. > Bourne shells > - To view or set an environment variable differs somewhat from > + To set an environment variable differs somewhat from > shell to shell. For example, in the C-Style shells such as > tcsh and csh, you would use > - setenv to set and view environment variables. > + setenv to set environment variables. > Under Bourne shells such as sh and > - bash, you would use set and > - export to view and set your current environment > + bash, you would use > + export to set your current environment > variables. For example, to set or modify the > EDITOR environment variable, under csh or > tcsh a This omits that you can use setenv/set to list all environment variables. How about adding the following sentence to the end of this paragraph: To view all current environment environment variables use setenv without any arguments under C-Style shells or set under Bourne shells. -- Marxpitn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message