README 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176
  1. Contents
  2. --------
  3. Introduction
  4. Dependencies
  5. Features
  6. Mini-documentation
  7. Where to get more information
  8. Reporting problems
  9. Introduction
  10. ------------
  11. GNU Midnight Commander (also referred to as MC) is a user shell with
  12. text-mode full-screen interface. It can be run on the OS console,
  13. in xterm and other terminal emulators.
  14. GNU Midnight Commander allows you to manage files while making most of
  15. you screen and giving you a clear representation of the filesystem, yet
  16. it's simple enough to be run over a telnet or ssh session.
  17. GNU Midnight Commander is released under the GNU General Public
  18. License version 2.0 or any later version. A copy of the file is
  19. included with this distribution package.
  20. Dependencies
  21. ------------
  22. To compile the GNU Midnight Commander you need to have a copy of the
  23. glib library version 1.2.x or 2.0.x, available at
  24. ftp://ftp.gtk.org/pub/gtk/
  25. Features
  26. --------
  27. GNU Midnight Commander was conceived as a free clone of John Socha's
  28. Norton Commander (TM). It also takes the best from more recent software
  29. with similar interfaces. GNU Midnight Commander comes with mouse support
  30. on xterm and optionally on the Linux console.
  31. Some features are specific to the POSIX environment MC runs on, some are
  32. familiar to the users of similar software for other operating systems.
  33. The features include:
  34. * Built in Virtual File System: manipulate remote file systems
  35. through the FTP and SMB protocols or over secure shell, browse
  36. contents of tar, ar, rpm, zip, cpio, lha and rar archives just
  37. like local files.
  38. * Almost all operations work with the virtual file system,
  39. enabling you to do complex tasks, like viewing files in
  40. archives on an FTP server.
  41. * Mouse support on most terminal emulators for X Window System
  42. as well as on the Linux console.
  43. * Learn Keys: GNU Midnight Commander may be configured at run
  44. time to support any kind of input keys for a given terminal,
  45. making its operation possible even on most weird terminals.
  46. * Text and hex editors are available for you to use (hex editor
  47. is a part of the viewer).
  48. * Hotlist allows you to keep a list of common visited locations,
  49. including remote sites and directories inside archives.
  50. * Command completion: By pressing Alt-Tab in any place where a
  51. filename or an executable are expected, GNU Midnight Commander
  52. will complete the name for you. If you press Alt-Tab for the
  53. second time, you get a list box with all possible completions.
  54. * Subshell support: Run your commands by a real shell
  55. interpreter. GNU Midnight Commander interacts with bash,
  56. tcsh and zsh to provide you with all of the facilities
  57. available in your preferred shell.
  58. * Find file command can search for the file contents.
  59. * Background operations allow you to copy or move files from
  60. any virtual file system while you do other tasks (i.e., you
  61. can do background FTP copies).
  62. * FTP proxy is supported.
  63. * Linux file recovery: If you are using Linux, you can recover
  64. deleted files from an ext2 or ext3 partition with the undelete
  65. file system. This is a low level file recovery function that
  66. can recover files deleted by any program on Linux.
  67. * External panelization: You can run any arbitrary external
  68. command and GNU Midnight Commander will display the output
  69. generated as a file listing that can be manipulated as a
  70. regular directory.
  71. * Emacs-like key bindings are used in all widgets.
  72. * Context dependent actions (open, view, edit) are available.
  73. * The built-in file viewer, together with the context dependent
  74. actions is used to format man pages on the fly, coloring mail
  75. messages and more.
  76. * The built-in editor supports syntax highlighting and external
  77. actions, such as spell checking and formatting.
  78. Mini-documentation
  79. ------------------
  80. These are hints for the text mode edition:
  81. * Use the F-Keys for invoking the commands in the function key bar.
  82. If your terminal doesn't support F-keys, you can use the <ESC digit>
  83. sequence to invoke the corresponding F-digit key.
  84. * Tab changes the current panel.
  85. * All input lines have emacs-like key-bindings (command history is
  86. accessed through the M-p and M-n keys).
  87. * The panels accept C-n, C-p for browsing the panel (like in Emacs).
  88. * M-Enter copies the currently selected file name to the input line.
  89. * M-Tab completes the current word (or tries to).
  90. * The Virtual File System is a cute addition to the project, you may
  91. browse in tar and compressed tar files as well as browsing remote
  92. machines with the mcfs file system.
  93. * Please read the manual page.
  94. * Read the file TODO for the current projects.
  95. You can access the whole documentation online with the F1 key,
  96. although it's not as nice as the groff printed manual page :-)
  97. Where to get more information
  98. -----------------------------
  99. There is a webpage for GNU Midnight Commander at
  100. http://www.midnight-commander.org/
  101. This page also has current information about mailing lists and some
  102. useful advices how to report bugs.
  103. You can download the latest version of GNU Midnight Commander from
  104. ftp://ftp.gnu.org/gnu/mc/
  105. Reporting problems
  106. ------------------
  107. There are two mailing lists, mc@gnome.org and mc-devel@gnome.org. Use
  108. mc-devel@gnome.org if you are prepared for a more technical discussion
  109. with the developers of the package, otherwise use mc@gnome.org.
  110. Please don't sent HTML e-mail to either of those mailing lists.
  111. Include the output of "mc --version", the operating system and the
  112. distribution (if applicable) you are using, the compiler and the
  113. configure flags used to compile the program (if you know them).
  114. If the program crashed and produced a core dump, please provide a
  115. stack trace of the program.
  116. You can do this by running gdb like this:
  117. gdb mc core
  118. (gdb) where