Gary Kline wrote:
Giorgos Keramidas wrote:
Watch out for shells with funny 'expansion rules', like csh(1) :)
[...]
Man! truer words, (c)... . One o the very few suggestions
left for improving shells [ and/or subshells ] is a flag,
say '-N' which would have *nothing* to be
On Jan 14, 2007, at 1:44 PM, Gary Kline wrote:
Man! truer words, (c)... . One o the very few suggestions
left for improving shells [ and/or subshells ] is a flag,
say '-N' which would have *nothing* to be escaped. In other
words a '$' or '' would be interpreted
On 2007-01-15 10:21, Chuck Swiger [EMAIL PROTECTED] wrote:
On Jan 14, 2007, at 1:44 PM, Gary Kline wrote:
Man! truer words, (c)... . One o the very few suggestions
left for improving shells [ and/or subshells ] is a flag,
say '-N' which would have *nothing* to be escaped. In
On Tue, Jan 16, 2007 at 12:04:23AM +0200, Giorgos Keramidas wrote:
On 2007-01-15 10:21, Chuck Swiger [EMAIL PROTECTED] wrote:
On Jan 14, 2007, at 1:44 PM, Gary Kline wrote:
Man! truer words, (c)... . One o the very few suggestions
left for improving shells [ and/or subshells ] is a
On Jan 15, 2007, at 2:29 PM, Gary Kline wrote:
OMG! I managed to break a new shell war :)
/me ducks and runs very far away
No! no, cometh backeth, Giorgos! No war, just peace, love
and flowers:-)
% cd /usr/ports/mail/imap-uw/ make extract cd work/imap-2004g
% tail -3
On Mon, Jan 15, 2007 at 02:45:57PM -0800, Chuck Swiger wrote:
On Jan 15, 2007, at 2:29 PM, Gary Kline wrote:
OMG! I managed to break a new shell war :)
/me ducks and runs very far away
No! no, cometh backeth, Giorgos! No war, just peace, love
and flowers:-)
% cd
Thanks for all the ways, gents. (I never thought of tr,
but now that seems like an option.) A week+ ago I tried
perl using 's/\xNN//g' from the cmdline, but nojoy.
The online docs said that \N{xx} would catch a hex character;
that's what was fuzzy.
On 2007-01-14 12:15, Gary Kline [EMAIL PROTECTED] wrote:
Thanks for all the ways, gents. (I never thought of tr, but now that
seems like an option.) A week+ ago I tried perl using 's/\xNN//g'
from the cmdline, but nojoy. The online docs said that \N{xx} would
catch a hex character; that's
On Sun, Jan 14, 2007 at 10:31:04PM +0200, Giorgos Keramidas wrote:
On 2007-01-14 12:15, Gary Kline [EMAIL PROTECTED] wrote:
Thanks for all the ways, gents. (I never thought of tr, but now that
seems like an option.) A week+ ago I tried perl using 's/\xNN//g'
from the cmdline, but nojoy.
o
Anybody know if I can do a perl substitution of the scads of
\x80\x9D to simple double-quotes () from the command line?
I've got many HTML files with this strange syntax (must be from
Windows) that I'd like to make human-readable for myself. I
know how
On 2007-01-13 18:45, Gary Kline [EMAIL PROTECTED] wrote:
Anybody know if I can do a perl substitution of the scads of
\x80\x9D to simple double-quotes () from the command line?
You already have part of the syntax right:
,
| [EMAIL
o
Anybody know if I can do a perl substitution of the scads of
\x80\x9D to simple double-quotes () from the command line?
80 hex = 200 octal
9D hex = 235 octal
cat k | tr \200 \ | tr \235 \ k.new
--
Matt Emmerton
___
freebsd-questions@freebsd.org
cat k | tr \200 \ | tr \235 \ k.new
Or, skipping the unnecessary cat and invoking tr only once
tr \200\235 \\ k k.new
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
13 matches
Mail list logo
