X-Spam-Check-By: sourceware.org Message-ID: <46B8C3B5.63251179@dessent.net> Date: Tue, 07 Aug 2007 12:10:45 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Looking for man pages References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Bob McConnell wrote: > This is not exactly a cygwin question, but can anyone point me to a > decent man page about writing Makefiles for GNU make 3.81? I tried to > use info, but can't make heads nor tails of the navigation methods for > that atrocity. The 'info' program has a long history of being either loved, hated, or mildly tolerated. I'm not going to wander into that flamewar, but I will point out that arguing about the 'info' program is missing the point of the texinfo format completely. The idea behind texinfo is a format-independent way of writing documentation. 'info' is just one of a million ways to view this same documentation. You can also view it in html using your favorite browser, e.g. . There are a half a dozen other formats here: . That you don't like using 'info' is no excuse at all to dismiss the texinfo documentation, which for the projects that use it (notably all the official GNU projects) is typically fairly extensive -- much more so than any man page. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/