Info/ko

이 안내서에서는 info 명령을 사용하여 info 페이지를 둘러보는 방법을 보여드리려 합니다.

info란 무엇인가요?
아마 대부분  문서 시스템에 익숙할 것입니다. man 에서는 항목을 빨리 찾아보는데 좋지만 맨 페이지를 서로 연결하는 구조는 빠져있습니다. 그래서 가 도입됐습니다. info 페이지는  도구를 사용하여 만들었으며, 다른 페이지로 연결할 수 있고, 메뉴를 만들 수 있으며, 일반적으로 탐색이 용이해졌습니다. 다음 장에서는 어떻게 info 페이지를 배치하는지 보도록 하겠습니다.

info 페이지 배치
주로 info 페이지는 에 있습니다. man 디렉터리 배치 방식과는 달리 에는 압축을 풀어낼 수 있는 내용이 있습니다. 이 파일은 다음 형식을 지니고 있습니다:

info 파일 형식

은 페이지의 실제 이름입니다(예: ). 는 다른 노드 레벨을 설계하는 추가 생성자입니다(보통 질문에 대해 info 문서의 최상단 레벨을 참조합니다). 디스크 공간을 절약하려는 목적으로 info 페이지를  압축 형식으로 압축합니다. 추가 info 페이지는  환경 변수로 조회 할 수 있습니다(보통 의 다양한 파일을 통해 설정합니다). 시작한다면 파일을 참고하는 것이 중요합니다. 이 특별한 파일은 매개 변수 없이 info를 실행할 때 사용합니다. 사용자가 탐색할 수 있는 모든 info 페이지 목록이 들어있습니다. info에서 이리저리 탐색하기 위해, 인자를 사용하지 않고 바로 실행해서 가져오도록 해보겠습니다:

Now in the next chapter we'll look at dealing with basic info navigation.

Browsing with menus
Now that info is started, we're given a screen similar to this:

Sample info screen

Right now there are a bunch of entries with an asterisk before them. These are menu items for navigating through different node levels. There are two ways of selecting menus. We'll look at the first now and the other way later. First off, we'll go ahead and look at the  info page. To do so, use the down arrow key until you reach the line for Wget:

Navigating to the wget info menu entry

Once you get to this line, hit the key to select the menu item. This will bring up the info page for  :

The wget info page

Now that we have an info page up, the next section will look at basic navigation.

Basic navigation
In terms of nodes, this is considered the  node for the wget page. Consider the  node to be the same as the table of contents for that particular info page. Now to navigate the actual page itself, you have a couple of different methods. First off is the standard info method. This is using the key to move forward a page and the / keys to move back a page. This is the recommended method as it automatically advances/retreats to the appropriate node in the document. This allows for a somewhat linear browsing for those used to man pages. Another way is through the / keys. These work, but they will not advance/retreat like // will. If you want to skip entire nodes without using //, you can also use the (advance backwards) and  (advance forwards) keys.

As mentioned earlier, there are 2 ways of navigating menus. The other way will now be described here. The numbers  can be used to reference to the first-ninth menu entries in a document. This can be used to quickly peruse through documents. For example, we'll use to reach the   menu entry. So press and it will bring up the   screen:

Resulting Recursive Download screen

Now we're at the  screen. Here is a good time to note a few things. First off the top header section. This header shows the navigation capable from this particular screen. The page indicated by  can be accessed by pressing the  key, and the page indicated by   can be accessed by pressing the  key. Please note that this will only work for the same level. If overused you could round up in totally unrelated content. It's better to use //// to navigate in a linear fashion.

If for some reason you get lost, there are a few ways to get out. First is the key. This will take you straight to the toplevel (table of contents) for the particular info page you're browsing. If you want to return to the last page you looked out, you can do so with the key. If you want to go to the above level, you can do so with the key. Now that you have some idea of navigating a page, the next chapter will look at searching for content.

Navigating to other info pages
Now that you can navigate an individual info page, it's important to look at accessing other info pages. The first obvious way is to go to the info page through the  index listing of info pages. To get to the  index from deep within a document, simply press the  key. From there you can search for the appropriate page you want. However, if you know the actual page, there is an easier way through the  command. To go to an info page by name, type to bring up the prompt and enter the name of the page in parentheses:

Going to an info page by name

This will bring up the libc page as shown here:

Result of the Goto node command

Now that we know how to go to info pages by name, the next section will look at searching for pieces of information using the info page's index.

Searching using an index
In this example we'll see how to lookup the  function of the c library using the   info page's index. You should still be at the libc info page from the last section, and if not, use the Goto node command to do so. To utilize the index search, hit the key to bring up the prompt, then enter your search term. We'll do so for  below:

Entering an index search query

After pressing enter upon completion of our query, we're brought to the  definition for  :

Result of the index search query

We've now successfully performed a search using the  info page index. However, sometimes what we want is in the page itself. The next section will look at performing searches within the page.

Searching using the search command
Starting from the previous location at the  node, we'll look at searching for the   variation of the   function. To perform a search, press the key to bring up the search prompt, and then enter the query (sprintf in this case):

Entering a search query

Hit  and it will show the result of the query:

Result of the search query

And we have the function we need.

Conclusion
This concludes the overview of using info to view info pages. As always comments are both welcome and appreciated.

Additional Program Resources
In order to make things easier for those that wish to browse info pages through a more friendly graphical interface, the following are available:


 * app-text/info2html - Convert info pages to a browse-able HTML format
 * app-text/pinfo -  based info viewer
 * app-text/tkinfo - a  based info browser
 * app-vim/info - a  based info browser

The  browser   also allows you to browse info pages through the   URI.

Acknowledgements
We would like to thank the following authors and editors for their contributions to this guide:


 * Chris White