From owner-freebsd-questions@FreeBSD.ORG Thu Feb 24 23:04:23 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55542106566B for ; Thu, 24 Feb 2011 23:04:23 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1055B8FC0A for ; Thu, 24 Feb 2011 23:04:22 +0000 (UTC) Received: from r55.edvax.de (port-92-195-143-131.dynamic.qsc.de [92.195.143.131]) by mx02.qsc.de (Postfix) with ESMTP id D34311E384; Fri, 25 Feb 2011 00:04:21 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id p1ON4LVO001762; Fri, 25 Feb 2011 00:04:21 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Fri, 25 Feb 2011 00:04:21 +0100 From: Polytropon To: Chip Camden Message-Id: <20110225000421.cd452210.freebsd@edvax.de> In-Reply-To: <20110224225834.GG1983@libertas.local.camdensoftware.com> References: <20110224213322.GA13089@guilt.hydra> <20110224221057.GA13262@guilt.hydra> <20110224223924.GF1983@libertas.local.camdensoftware.com> <4D66DEED.9010105@infracaninophile.co.uk> <20110224225834.GG1983@libertas.local.camdensoftware.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Backtick versus $() X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Feb 2011 23:04:23 -0000 On Thu, 24 Feb 2011 14:58:34 -0800, Chip Camden wrote: > Thanks for that -- though I'll go with: > > set -o vi > > TYVM. I didn't know /bin/sh supported those modes. It's hardly known as /bin/sh is _not_ used for interactive comunication regularly, as it's basically the system's standard scripting shell. It's interactive use is reserved for emergencies, operations performed in single user mode to bring back the system to perform normally. Still, it *CAN* be used for this porpose quite well when configured properly - if needed. I could also say: If you're spending too much time in sh interactive sessions to think about it, you're probably doing something wrong. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...