From owner-freebsd-arch@freebsd.org Sun Feb 26 22:08:02 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2C71CEE506 for ; Sun, 26 Feb 2017 22:08:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BA2FB5B for ; Sun, 26 Feb 2017 22:08:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id h10so49418151ith.1 for ; Sun, 26 Feb 2017 14:08:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0pIWAnyaIIsaw5MCtN8ZtvGGq17pkWc0aK+csJu5Myg=; b=g9o5DLfl+gfgbOkU8DOZehbP+LlZy1ah4ddZ+3KrWJ6eH1+CmwMGOKkwNy1QWW2/SF xpr1LNar9D0Z2SXd96RWR2NYHrpXYeUXuAs1QeSsZ49nxlL09cfF1Fc6rDc4/R0o9BUz wAxfFDeeaFLgEGFETLjXjGEWp9rxuIf/fdXNqYXzvOMlE/pHZLkyFhCZwZpkhwxXrAfc iadb+58UBbfb68jT4mhAZy8iSvs65L+CX0K2ee5suQIm5uz/Pu2m4ZX1XlgVX9lf6eDO SExO58F/TwT5aRjKjDcZCdVnWei17YQq5zPniuLZPrgiPsTxd+StlhxhabwsfufcR+1y CkFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=0pIWAnyaIIsaw5MCtN8ZtvGGq17pkWc0aK+csJu5Myg=; b=KPo9J+Y+cY3K881/w91jeHICX36EESqnEpQSjGlmdBUfhKkbHmXFBqk/0AmVyhfHyG xX3sBJjJ884jmVxyJ1Z0GOYJYFBfGprP1HJMOYmLOC9Upv2dNToWhA375UoFji9QRCGP AK2PQClqLPjYNrZyHOJ8KckyB2movmT5v52rUXwhD87zyUTifG42AR28KcjJ7SHtYPfp z7tycgQJYRe+39u+YgbJZzDuomIv5YQDCCdMTH0VaNQk8SUROBTHhX/TElH6J3hyJjJ3 vD6DgvALxnPH0WsNTuu/J8PZ8232gcGhoJ/Ai5t5SpGp52h3iJiqk6kAnoqssF56sGjK YNrg== X-Gm-Message-State: AMke39kn1ellG1fDo5zOmR/i1yrSacvNqYV3T6nn/eWualmQi7yP/+7Dl4LamVegd2fDAteX7hXeQeiV1Tb+Hw== X-Received: by 10.36.116.71 with SMTP id o68mr13198162itc.60.1488146880964; Sun, 26 Feb 2017 14:08:00 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.145.132 with HTTP; Sun, 26 Feb 2017 14:08:00 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <20170226190654.GA23029@freefall.freebsd.org> From: Warner Losh Date: Sun, 26 Feb 2017 15:08:00 -0700 X-Google-Sender-Auth: 4PBMchYaHLCbZDTvJIyop5OsvZU Message-ID: Subject: Re: I want to remove troff output support from indent(1) To: Bob Bishop Cc: "Piotr P. Stefaniak" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 22:08:02 -0000 On Sun, Feb 26, 2017 at 1:59 PM, Bob Bishop wrote: > Hi, > >> On 26 Feb 2017, at 19:06, Piotr P. Stefaniak wrote: >> >> indent, the C source reformatting tool, has a -troff option to produce >> roff output. >> >> I have a few issues with it: >> 1) it doesn't work. When I view the resulting file with nroff(1) piped >> to more(1) [etc] > > From man indent: > > "-troff Causes indent to format the program for processing by > troff(1)" > > NB troff. Likely it was always broken with nroff. I know that I used indent from this time with troff output to print things that looked OK. It had to be troff, because nroff didn't work with the laser printer that we had... I have no trouble removing it, but I have first hand experience with it working back in the day. Warner