info

[Member ThakurMsh]

My respects to All…
Can you please tell me why there are no necessary packages to be called correctly info info?

$ info info
info: No menu item 'info-stnd' in node '(dir)Top'
th@deb:~
$ sudo apt install info
[sudo] пароль для th: 
Чтение списков пакетов… Готово
Построение дерева зависимостей       
Чтение информации о состоянии… Готово
Уже установлен пакет info самой новой версии (6.5.0.dfsg.1-4+b1).
Обновлено 0 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
th@deb:~

[Anonymous]

Helpful

Up

0

::

> why

Instead, can we just do “how”?

At the command prompt, simply type: info
Immediately after the info program launches, you can press H (or other, may be locale-specific) for help or to access a tutorial regarding usage and navigation.

Alternatively, at the command prompt you can type info --help

[Anonymous]

Helpful

Up

0

::

Debian embraces “man” (manpage) encapsulation of helpdocs. Except for packages maintained by GNU, very few debian-packaged programs will provide documentation intended for display via the “info” viewer utility.

About 2 years ago, curiosity toward what I (we) might be missing led me to compare the content within the “info” vs “man” formatted documentation. Of the 20+ sets of documentation I reviewed, none of the “man” documents seemed less complete, less comprehensive, in comparison to their sibling “info” document.

[Member ThakurMsh]

Helpful

Up

0

::

When I call info then

`File: dir, Node: Top, This is the top of the INFO tree.

This is the Info main menu (aka directory node).
A few useful Info commands:

‘q’ quits;
‘H’ lists all Info commands;
‘h’ starts the Info tutorial;
‘mTexinfo RET’ visits the Texinfo manual, etc.

</blockquote>

it should be like this

<blockquote>
File: dir, Node: Top This is the top of the INFO tree

This (the Directory node) gives a menu of major topics.
Typing “q” exits, “?” lists all Info commands, “d” returns here,
“h” gives a primer for first-timers,
“mEmacs<Return>” visits the Emacs manual, etc.

In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.

* Menu:

Archiving
* Xorrecord: (xorrecord). Emulates CD/DVD/BD program cdrecord
* Xorriso: (xorriso). Burns ISO 9660 on CD, DVD, BD.
* Xorrisofs: (xorrisofs). Emulates ISO 9660 program mkisofs

Basics
* Common options: (coreutils)Common options.
* Coreutils: (coreutils). Core GNU (file, text, shell) utilities.
* Date input formats: (coreutils)Date input formats.
* File permissions: (coreutils)File permissions.
Access modes.
* Finding files: (find). Operating on files matching certain criteria.

C++ libraries
* autosprintf: (autosprintf). Support for printf format strings in C++.

Compression
* Gzip: (gzip). General (de)compression of files (lzw).

DOS
* Mtools: (mtools). Mtools: utilities to access DOS disks in Unix.

Editors
* JED: (jed). The JED editor
* nano: (nano). Small and friendly text editor.

Emacs
* Emacs FAQ: (efaq). Frequently Asked Questions about Emacs.

GNU Gettext Utilities
* ISO3166: (gettext)Country Codes.
ISO 3166 country codes.
* ISO639: (gettext)Language Codes.
ISO 639 language codes.
* xgettext: (gettext)xgettext Invocation.
Extract strings into a PO file.
* autopoint: (gettext)autopoint Invocation.
Copy gettext infrastructure.
………`

the hyperlink system is a little more convenient.

• This reply was modified 2 years, 4 months ago by ThakurMsh.
• This reply was modified 2 years, 4 months ago by ThakurMsh.
• This reply was modified 2 years, 4 months ago by ThakurMsh.

[Moderator Brian Masinick]

Helpful

Up

0

::

@Skidoo: I agree. A great percentage of the time, in places where both man and info are available, more than half of the time, the content of the material was virtually identical. As you note, however, man documentation is much more common, and it is frequently more comprehensive too.

If for any reason we chose to use info documentation instead of man documentation, we’d end up either converting it or rewriting an extremely large percentage of documents. Going from man to info would not be practical.

I do not personally advocate any major documentation changes, other than updating to match current features and software changes.

If we ever do decide to offer any different format, I’d want it to be:
1) a universal documentation format
2) able to read online from all current devices

By the time we’d be interested in doing that, there may be different systems and applications; no need for further speculation until (or if) that day arises.

--
Brian Masinick

[Member ThakurMsh]

Helpful

Up

0

::

@masinick,thank you very much. got it.
@skidoo,thank you very much.

[Author]

Posts