Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 Sep 2014 13:05:59 -0700
From:      leeoliveshackelford@surewest.net
To:        Polytropon <freebsd@edvax.de>
Cc:        freebsd-questions@freebsd.org, kpneal@pobox.com
Subject:   Re: how to install wireless n.i.c. on FreeBSD 9.1
Message-ID:  <eb10c52d8c81197de5cb23d99ab3da8a@surewest.net>
In-Reply-To: <20140831103329.18f5b713.freebsd@edvax.de>
References:  <c0493cf1a6cb62e193163d781348b8ad@surewest.net> <20140823025527.bd80818d.freebsd@edvax.de> <df00e520b70e5b6fc5c379195956d6b7@surewest.net> <20140826022802.198cd285.freebsd@edvax.de> <3f1e44ea23fb755ae9f8e2390ab2a3d6@surewest.net> <20140830200831.GB12450@neutralgood.org> <20140831103329.18f5b713.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
 

Dear Kpneal and Polytropon, 

Thank you both for your recommendations. Yours truly, Lee 

On 08/31/2014 01:33 AM, Polytropon wrote: 

> On Sat, 30 Aug 2014 16:08:31 -0400, kpneal@pobox.comwrote:
> On Tue, Aug 26, 2014 at 02:38:16PM -0700, leeoliveshackelford@surewest.netwrote: topic, can or do you recommend a character mode programer's editor, that is, an editor that prints a line number to the left of each line? Thank you for any and all comments. Yours truly, Lee I use vi for this, and I've gone to the trouble of compiling FreeBSD's vi AKA "nvi" on the Linux systems I'm forced to use. The vi/nvi option for this is "set number".

This is a good suggestion, as vi (and vi-like editors) are
very common among programmers. Within X, which helps me to
organize my workflow consisting of the use of terminals,
browser windows, debuggers, manpages, Midnight Commander
and other tools, I tend to use gviim (a graphical "enclosure"
for vim, "vi improved"). I didn't improve or customize it
much - just added line numbers, syntax highlighting and a
few other settings. So if you are in X, check out gvim to
see if you like it. If you are in text mode, use the system's
vi. You can enrich it with a custom configuration file,
just like with gvim (which uses ~/.vimrc so it doesn't
conflict with the real vi).

Your suggestion of vi is hereby seconded. :-)

However, for "quick and dirty" stuff (or anything that
isn't actually real programming) I use mcedit via PF4 out
of the Midnight Commander. This editor is very nice and
powerful, but doesn't have line numbers.

 
From owner-freebsd-questions@FreeBSD.ORG  Mon Sep  1 20:41:48 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A4D9D743
 for <freebsd-questions@freebsd.org>; Mon,  1 Sep 2014 20:41:48 +0000 (UTC)
Received: from mail.parts-unknown.org (mail.parts-unknown.org
 [IPv6:2001:470:67:119::4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 88C4A1F11
 for <freebsd-questions@freebsd.org>; Mon,  1 Sep 2014 20:41:48 +0000 (UTC)
Received: by mail.parts-unknown.org (Postfix, from userid 1001)
 id C2AAC8C1090D; Mon,  1 Sep 2014 13:41:47 -0700 (PDT)
Date: Mon, 1 Sep 2014 13:41:47 -0700
From: David Benfell <benfell@parts-unknown.org>
To: freebsd-questions@freebsd.org
Subject: controlled environment for regular expressions?
Message-ID: <20140901204147.GA53086@home.parts-unknown.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr"
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 20:41:48 -0000


--liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi all,

I am having a major problem with regular expression matching returning
different results when run from a script under cron or as a delivery
instruction from postfix rather than from the command line.

I don't even know how to debug this. These are all in scripts and
delivery instructions that I have had working for over a decade. And
when I run them from the command line, they work as expected.

The path for seeking executables should not be at issue. I use the
PATH variable in my crontabs and set it to the same PATH as at a
terminal.

I have encountered this problem with both grep and GNU sed (gsed, from
the port).

This is all stuff that worked until recently, and worked for years
under Linux. The only change I think I've made is to implement an IPv6
tunnel. I hope, really hope, I can safely say that's irrelevant.

I use zsh, also a choice that's over a decade old, for both my command
line and to run scripts.

I've never liked regular expressions. I think they are an awful
kludge. But unfortunately, a major part of my workflow depends on them
working correctly and *predictably*.

Has anyone else encountered problems with this? How do you fix it?

Thanks!
--=20
David Benfell <benfell@parts-unknown.org>
See https://parts-unknown.org/node/2 if you don't understand the
attachment.

--liOOAslEiF7prFVr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJUBNoLAAoJEBV64x4SNmAr7lAQAIq+MsJvOz/uzjE7umOw8JTZ
inPiXGr8xLhvYBtpmVI8Wh376p+HOVQANF7wGgPtxaebTWhch8Jad9PKc8oR4QQR
G4XKbSomkhim1Mxpu9kggFprHmOEpIlfvCx47COc63DfbzfhKn/73mkASZJXAksY
Lf06ic+2xTsxYkJcCg5OwW3b6TDVgjBD16olZuBUvbHvHgJpd2+inqjF8yWbvWbf
EcdqkfbQYAyJUkf0VEQxVaAcvXcZLFmKvyqM4z+i3PFzpfgw6MFKokOZ90Zily+/
qGdWeMOX3Cehe86abKVRuIPXjP+Vd5iIGj3GtI8WVj2lfpKQggkeK88Rc83f0djI
l88CilGJYePl9ylgW+45MC6PNzxCJWcoetnd95A7P22Ec/sFwSl8L9ngHQAOjWM5
crT/UY22h4iFnWpgCWsVH9L2c0/S3WJCyrzY15lTAat9hqu+sQNa5XK29JEl4GG2
aPAqVkA+M9E5yXiTdtirvHmwNCpxp2Z7W5hIP/rGXV7xwQnGiZpm5XYLnJ9asojA
LCSDamU8GMJG0y7HneJZ33X1OqPkdLuJbSu9nQ4Eqm7TlkUABUCccBQnuoR5ORfr
na90fWmkkw+s48iun/L1GwIR0yxHFK0w+OkKi6Ae084eGaGDf4te8AaxauFRD96E
dl+e0hmWGLfDbrgHPvD0
=Jibc
-----END PGP SIGNATURE-----

--liOOAslEiF7prFVr--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eb10c52d8c81197de5cb23d99ab3da8a>