Man vs. Info: documenting the software
in [Shell]
|
Prev: Remove certain characters in a filename
Next: x12a403
From: Stephane CHAZELAS on 4 Feb 2010 05:37 2010-02-02, 07:20(+00), Seebs: [...] > "info gcc" gives me a huge nest of menus I have to pick from to find > a given option. And a table of contents and an index, just like a book. > "man gcc" gives me something where "/msoft-float" gets > me to the right option without me having to figure out what category > that information was put in. /msoft-float (smsoft-float in info) may get you to the right option. imsoft is more likely to as it will take you to index entries that contain msoft. And if it's not the right one, press ",". Same, instead of "man 3 printf" you can do "info libc --index-search printf" (info libc printf works as well but gets you to another printf related topic unfortunately), and you get the context around. Again, same principle as a book. You look in the index of your libc book for printf and are taken to the "formatted output" section. Or you can do "info coreutils printf" for the printf command (man 1 printf). [...] > I said "GNU coding standards". Not "every last possible thing which GNU > has ever specified". (That said: Consider "true --help" or "echo > --version".) $ true --help Usage: /bin/true [ignored command line arguments] or: /bin/true OPTION Exit with a status code indicating success. --help display this help and exit --version output version information and exit NOTE: your shell may have its own version of true, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports. Report true bugs to bug-coreutils(a)gnu.org GNU coreutils home page: <http://www.gnu.org/software/coreutils/> General help using GNU software: <http://www.gnu.org/gethelp/> For complete documentation, run: info coreutils 'true invocation' See "help true" if your shell is bash for the builtin ;), or <Meta-H> in zsh (assuming you have run-help setup (see info zsh --index-search run-help)) or true --help or true --man POSIX and LSB specifies that "echo --version" should output "--version<LF>" (just as "echo -e" should output "-e<LF>" in POSIX but not LSB). -- St�phane
From: Stephane CHAZELAS on 4 Feb 2010 05:47 2010-02-3, 07:47(+01), Sidney Lambe: > On comp.unix.shell, Ivan Shmakov <ivan(a)main.uusia.org> wrote: > > The post is simply unreadable for all the superfluous garbage > in it and weird formatting. [...] As it happens, it's a properly formatted MIME message, but written in UTF-8. There was a time when only iso-8859-1 (and no encoding) and then iso-8859-15 were supported on the english speaking usenet, gnus was known to be a common offender at the time. I don't know if it's still the case (is it?), but it's true that slrn for one still doesn't support converting charsets. There's not much point using UTF-8 here. -- St�phane
From: Stephane CHAZELAS on 4 Feb 2010 05:51 2010-02-03, 09:34(+06), Ivan Shmakov: > >>>>>> "SM" == Sven Mascheck <mascheck(a)email.invalid> writes: >>>>>> "IS" == Ivan Shmakov wrote: >>>>>> "S" == Seebs <usenet-nospam(a)seebs.net> writes: > > S> I use about fifteen programs in which /foo<return> yields a search > S> for foo. I am not very motivated to learn another interface... > > IS> Do you use / to search the Bash history as well? > > SM> Do you mean especially Seebs, or those who actually use set -o vi? > > ... I wonder, whether Vim will ever support anything to the > effect of ???set -o emacs???? [...] http://www.vim.org/scripts/script.php?script_id=300 -- St�phane
From: Ben Finney on 4 Feb 2010 06:08 Stephane CHAZELAS <stephane_chazelas(a)yahoo.fr> writes: > 2010-02-3, 07:47(+01), Sidney Lambe: > > On comp.unix.shell, Ivan Shmakov <ivan(a)main.uusia.org> wrote: > > > > The post is simply unreadable for all the superfluous garbage in it > > and weird formatting. > [...] > > As it happens, it's a properly formatted MIME message, but written in > UTF-8. I don't know about Sidney, but I see Ivan's messages with correct character encoding *and* superfluous garbage and weird formatting. To wit: Ivan is not using the conventional '> ' quote leader, instead using an obnoxiously verbose reply quoting format (which seems to be common to a number of people, but is no less obnoxious for that). That makes his messages painful to read because of all the superfluous garbage and weird formatting. Ivan may have something valuable to say in each message, but the quoting style makes his messages too difficult to wade through so I usually skip them. -- \ “None can love freedom heartily, but good men; the rest love | `\ not freedom, but license.” —John Milton | _o__) | Ben Finney
From: Stephane CHAZELAS on 4 Feb 2010 07:39
2010-02-04, 22:08(+11), Ben Finney: > Stephane CHAZELAS <stephane_chazelas(a)yahoo.fr> writes: > >> 2010-02-3, 07:47(+01), Sidney Lambe: >> > On comp.unix.shell, Ivan Shmakov <ivan(a)main.uusia.org> wrote: >> > >> > The post is simply unreadable for all the superfluous garbage in it >> > and weird formatting. >> [...] >> >> As it happens, it's a properly formatted MIME message, but written in >> UTF-8. I was wrong about slrn not supporting various charsets. It seems it's no longer the case (though best results are achieved if you're in a utf8 locale and posting in utf8). > I don't know about Sidney, but I see Ivan's messages with correct > character encoding *and* superfluous garbage and weird formatting. > > To wit: Ivan is not using the conventional \u2018> \u2019 > quote leader, instead Those Unicode quoting characters above have no exact mapping in ascii or iso-8859-1/15, so if I want to post in iso-8859-15, I've got to resort to approximations (`...'). > using an obnoxiously verbose reply quoting format (which seems to be > common to a number of people, but is no less obnoxious for that). > > That makes his messages painful to read because of all the superfluous > garbage and weird formatting. Ivan may have something valuable to say in > each message, but the quoting style makes his messages too difficult to > wade through so I usually skip them. Strange that you'd find it hard to read given that you both seem to be using the same news reader software. I'd expect that kind of gnus style formatting to be properly displayed in gnus. See http://www.faqs.org/faqs/gnus-faq/ question Q2.2 and http://www.xemacs.org/Documentation/packages/html/supercite.html I quite like the fact that every quoted line keeps track of its original author, but in a long thread, it becomes difficult to track what replies to what. As the FAQ entry says, some love it, some hate it. -- St�phane |