Date: Mon, 7 Sep 2015 07:28:44 -0453.75 From: "William A. Mahaffey III" <wam@hiwaay.net> To: freebsd-questions@freebsd.org Subject: Re: GCC question Message-ID: <55ED81B2.7050406@hiwaay.net> In-Reply-To: <50324.13908.bm@smtp111.sbc.mail.ne1.yahoo.com> References: <55EAEE19.2060807@hiwaay.net> <55EAF922.2020906@hiwaay.net> <55EC25FE.4070802@ShaneWare.Biz> <55EC501E.10403@hiwaay.net> <441tebcrzw.fsf@lowell-desk.lan> <50324.13908.bm@smtp111.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/07/15 02:30, Thomas Mueller wrote: > from Lowell Gilbert: > >> The full form of the documentation is in an info file. Type "info gcc" >> to get it. If you use emacs, you'll find its info browser is better than >> the command line version. In fact, if you don't use emacs, you might be >> best off with an online version, such as from >> https://gcc.gnu.org/onlinedocs/ > There is a port, misc/pinfo, that I find helpful for reading an info file in the absence of KDE and Konqueror that I had years back with Linux Slackware. > > Otherwise, I find info user-hostile, plain text would be better. Many times, I went through an info file as straight text with "less" and found that better than info. > > Tom I definitely 2nd that motion, I do *NOT* like info at all, man pages are my preference (or plain text, or *maybe* HTML), or else decently formatted online help from the CLI, i.e. 'gcc -h <topic>' or 'gcc --help <topic>' .... A little more effort for the developer, but *FAR* preferable to info for me. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55ED81B2.7050406>