From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam question
Date: Fri, 17 Aug 2001 08:50:10 +0000 [thread overview]
Message-ID: <3B7C45BC.A9A8680E@null.net> (raw)
In-Reply-To: <059001c12697$765da3d0$3cf7c6d4@SOMA>
Boyd Roberts wrote:
> anyone like to blow away tabs on any given windows app?
I carry around a utility I originally developed at Geotronics
(early 1980s) called "retab" that transforms from one set of
tabs stops to another in one pass; it can turn all tabs to an
appropriate number of spaces by specifying -o +1. The manual
page could be improved, but here it is:
NAME
retab - detab|entab utility
SYNOPSIS
retab [ [ -io ] global_options ] [ -i input_options ] [ -o
output_options ]
DESCRIPTION
Retab reformats text containing combinations of spaces and
tabs in accordance with user-specified input and output tab
stops; trailing spaces and tabs are removed. Retab is suit-
able for use as a filter or as a stand-alone utility.
Options following -i apply to the input text; those follow-
ing -o apply to the output text; all others, including those
following -io, apply to both input and output. Options may
consist of a filename (standard input or output used if no
file specified) and/or tab stop specifications. Tab stops
are specified as a list of column numbers (the leftmost
print position is column # 1) optionally followed by the
increment of a regularly-spaced series of stops past the
last explicitly given column number; the increment is speci-
fied in the form +n. Unspecified input or output tab stops
are assumed to be UNIX standard (equivalent to specifying 9
+8).
EXAMPLE
$ retab -i foo -o +5
interprets the tab settings in file ``foo'' according to the
standard eight-column spacing while printing on a terminal
having hardware stops set in every fifth column.
SEE ALSO
newform(1).
DIAGNOSTICS
In case of malfunction, retab terminates with an error mes-
sage and returns non-zero exit status.
AUTHOR
Douglas A. Gwyn, BRL/VLD-VMB
next prev parent reply other threads:[~2001-08-17 8:50 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 10:45 [9fans] ls -R rog
2001-08-08 17:08 ` [9fans] Sam question gene garbutt
2001-08-14 9:44 ` Douglas A. Gwyn
2001-08-14 17:02 ` [9fans] h is for help in tp Rick Hohensee
2001-08-16 21:07 ` [9fans] Sam question Boyd Roberts
2001-08-17 8:50 ` Douglas A. Gwyn [this message]
2001-08-17 10:27 ` Re[2]: " Matt
2001-08-17 12:14 ` Boyd Roberts
2001-08-17 12:35 ` Re[2]: " Matt
2001-08-20 8:56 ` Douglas A. Gwyn
2001-08-20 11:11 ` Boyd Roberts
2001-08-20 16:25 ` Sam Ducksworth
2001-08-20 15:11 ` Boyd Roberts
2001-08-21 8:37 ` Ozan Yigit
2001-08-21 9:31 ` Boyd Roberts
2001-08-22 2:52 ` Donald Brownlee
2001-08-17 10:22 ` Re[2]: " Matt
2001-08-14 12:41 rob pike
2001-08-17 14:15 rob pike
2001-08-17 16:58 ` Boyd Roberts
2001-08-20 8:56 ` Douglas A. Gwyn
2001-08-17 14:22 rob pike
2001-08-17 16:32 David Gordon Hogan
2001-08-17 16:55 ` Lucio De Re
2001-08-17 17:08 ` Boyd Roberts
2001-08-17 17:28 ` Louis Beleos
2001-08-17 17:45 ` Lucio De Re
2001-08-17 17:04 ` Boyd Roberts
2001-08-17 17:04 ` Steve Kilbane
2001-08-18 1:36 ` Boyd Roberts
2001-08-19 6:31 ` Lucio De Re
2001-08-17 17:00 rob pike
2001-08-17 22:22 geoff
2001-08-17 22:35 David Gordon Hogan
2001-08-18 4:47 ` Rick Hohensee
2001-08-19 6:29 ` Lucio De Re
2001-08-18 7:38 nigel
2001-08-18 8:31 ` Steve Kilbane
2001-08-20 8:57 ` Luis Fernandes
2001-08-20 11:10 ` Boyd Roberts
2001-08-18 11:06 ` Boyd Roberts
2001-08-19 6:57 ` Lucio De Re
2001-08-19 10:54 ` Boyd Roberts
2001-08-19 11:13 ` Lucio De Re
2001-08-19 12:02 ` Boyd Roberts
2001-08-19 12:23 ` Lucio De Re
2001-08-19 16:17 ` Steve Kilbane
2001-08-19 20:57 ` Dan Cross
2001-08-19 12:44 rob pike
2001-08-19 15:05 bwc
2001-08-19 15:59 ` Boyd Roberts
2001-08-19 18:06 rob pike
2001-08-20 12:06 bwc
2008-07-17 22:56 [9fans] sam question Skip Tavakkolian
2008-07-18 0:28 ` erik quanstrom
2008-07-18 0:45 ` Pietro Gagliardi
2008-07-18 10:01 ` roger peppe
2008-07-18 13:22 ` Russ Cox
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=3B7C45BC.A9A8680E@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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.
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).