From owner-freebsd-doc@FreeBSD.ORG Sat Nov 29 17:57:24 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED1551065672 for ; Sat, 29 Nov 2008 17:57:23 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id C1D2B8FC1F for ; Sat, 29 Nov 2008 17:57:23 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 31958 invoked from network); 29 Nov 2008 17:30:42 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 29 Nov 2008 17:30:42 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 9C07B50822; Sat, 29 Nov 2008 12:30:39 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 3DB3F1CD39; Sat, 29 Nov 2008 12:30:39 -0500 (EST) To: freebsd-doc@freebsd.org References: <49305325.9070703@gmail.com> From: Lowell Gilbert Date: Sat, 29 Nov 2008 12:30:38 -0500 In-Reply-To: <49305325.9070703@gmail.com> (Eitan Adler's message of "Fri\, 28 Nov 2008 15\:23\:01 -0500") Message-ID: <44ljv2qw1t.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: tcsh man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2008 17:57:24 -0000 eitanadlerlist@gmail.com (Eitan Adler) writes: > in man 1 tcsh > http://tcshrc.source-forge.net should not have the "-" > The relevant line in src/contrib/tcsh/tcsh.man is > \fIhttp://tcshrc.sourceforge.net\fR. > which does not have a - > Why does the "-" show up? How can it be fixed? That's the line-wrap caused by the URL being split across two lines. I'm not sure what the right fix would be; is there a way to keep a string from being split? Maybe forcing a newline first would be the best that can be done? And such a fix would have to be portable enough to be accept upstream...