FAQ 33 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897
  1. GNU Midnight Commander
  2. Frequently Asked Questions
  3. The newest version of this document is available at
  4. http://savannah.gnu.org/cgi-bin/viewcvs/mc/mc/FAQ?rev=HEAD&content-type=text/plain
  5. * 1 Getting started
  6. + 1.1 What is Midnight Commander?
  7. + 1.2 Does it run on my machine?
  8. + 1.3 Does it work with my terminal?
  9. + 1.4 What else do I need to run MC?
  10. + 1.5 Is GNU Midnight Commander Public Domain? Copyrighted?
  11. + 1.6 Where can I get GNU Midnight Commander?
  12. + 1.7 I don't have FTP access. Where can I get MC?
  13. + 1.8 I cannot compile MC. What should I do?
  14. * 2 Keyboard
  15. + 2.1 What does documentation mean with the C-?, M-? and F?
  16. keys?
  17. + 2.2 Why don't function keys (or some other key) work?
  18. + 2.3 How do I use function keys F11 to F20?
  19. + 2.4 Why does the ESC key behave funny?
  20. + 2.5 How can I add the plus sign (+) on the command line?
  21. + 2.6 C-o doesn't work!
  22. + 2.7 What 'keys' are the "a1" and "c1" keys mentioned in the
  23. manual?
  24. + 2.8 How do I change the key bindings?
  25. * 3 Mouse
  26. + 3.1 How do I enable mouse support?
  27. + 3.2 How do I cut and paste text with mouse?
  28. + 3.3 How do I get the extension dependent pop-up menu to
  29. pop up?
  30. * 4 Display
  31. + 4.1 Why do I keep getting "Terminal not powerful enough for
  32. SLang" or "Terminal not powerful enough for SLsmg"?
  33. + 4.2 Why don't line drawing characters work?
  34. + 4.3 Can one use latin-1 characters without losing the lines?
  35. + 4.4 I have problems with entering/viewing national
  36. characters!
  37. + 4.5 How can I get colors?
  38. + 4.6 My color_xterm goes completely (or partially) black!
  39. + 4.7 Where can I get xterm or rxvt?
  40. + 4.8 I got colors working with MC but the other programs
  41. don't work at all anymore!
  42. + 4.9 Why are there both terminfo and termcap? Wouldn't one
  43. database be enough?
  44. * 5 Graphical user interface
  45. + 5.1 Xview, Tk and Gnome editions?
  46. + 5.2 Why is MC linked with X libraries?
  47. * 6 Command line problems
  48. + 6.1 How do I stay in the last directory when I exit Midnight
  49. Commander?
  50. + 6.2 How can I access command line history?
  51. + 6.3 How can I complete commands, file names, variable names
  52. and so on?
  53. + 6.4 I am using ksh. Can I use functions defined in the
  54. .kshrc within MC?
  55. + 6.5 Is there any way to include additional options or hot
  56. keys to MC?
  57. * 7 Virtual file systems
  58. + 7.1 How can I see the contents of a tar archive?
  59. + 7.2 How do I get out of a tar archive?
  60. + 7.3 How do I do anonymous ftp with MC?
  61. + 7.4 How do I do non-anonymous ftp with MC?
  62. + 7.5 How do I close an ftp connection?
  63. + 7.6 Why aren't the contents of ftp panel updated?
  64. + 7.7 What kind of proxy server works with Midnight Commander?
  65. * 8 Internal editor
  66. + 8.1 When I try pasting to the internal editor, it indents
  67. the amount of indenting increases with each line!
  68. + 8.2 Is it possible to use Colorer for syntax highlighting?
  69. * 9 Other common problems
  70. + 9.1 Is there any way to 'bookmark' favorite ftp-fs links?
  71. + 9.2 When I start Midnight Commander, nothing happens!
  72. * 10 Development
  73. + 10.1 Who has written Midnight Commander?
  74. + 10.2 Do I dare to use a development version?
  75. + 10.3 How can I report a bug/request for a feature?
  76. + 10.4 How can I join the development?
  77. * 11 More information
  78. + 11.1 This document didn't answer my question. Where else
  79. can I look for an answer?
  80. + 11.2 What mailing lists are there for Midnight Commander?
  81. + 11.3 Where should I look on the World Wide Web for MC stuff?
  82. + 11.4 Are the mailing lists archived anywhere?
  83. * 12 Legal issues
  84. + 12.1 Authorship
  85. + 12.2 Feedback is invited
  86. + 12.3 Disclaimer and copyright
  87. 1 Getting started
  88. 1.1 What is Midnight Commander?
  89. GNU Midnight Commander is a user-friendly yet powerful file manager
  90. and visual shell, useful to novice and guru alike. It provides a
  91. clear, user-friendly, and somewhat protected interface to a Unix
  92. system while making many frequent file operations more efficient and
  93. preserving the full power of the command prompt. After some
  94. practice, you will wonder how you could ever live without it.
  95. 1.2 Does it run on my machine?
  96. GNU Midnight Commander runs on POSIX (Unix-like) operating systems,
  97. such as GNU/Linux, FreeBSD, Mac OS X, Solaris, HP-UX and others. It
  98. can also be compiled under Cygwin on Windows.
  99. GNU Midnight Commander uses GNU Autoconf which should automatically
  100. configure it for every Unix clone. Following configurations have
  101. been tested in the past (this list is very old):
  102. * i386-*-linux1.x, 2.x
  103. * alpha-linux-linux2
  104. * sparc-linux-linux2.x
  105. * sparc64-linux-linux2.1
  106. * mips-sgi-irix5.x, 6.x
  107. * mips-dec-ultrix4.3
  108. * rs6000-ibm-aix3.2.5
  109. * sparc-sun-sunos4.1
  110. * sparc-sun-solaris2.3, 2.4, 2.5
  111. * sparc-sun-netbsd1.0
  112. * hppa-hp-hpux9
  113. * hppa-hp-hpux7
  114. * m68k-apple-aux
  115. * unixware
  116. * mc88110-aviion-dgux5.4R2.01
  117. * i386-*-sco3.2v4.2
  118. * i386-*-sco3.2v5
  119. 1.3 Does it work with my terminal?
  120. Yes, it does.
  121. Because GNU Midnight Commander is a full screen program it doesn't
  122. run on dummy terminals but anything more advanced will do (like
  123. vt100). If your terminal works with vi, emacs, elm or pine it will
  124. work with GNU Midnight Commander.
  125. 1.4 What else do I need to run MC?
  126. You need a POSIX (Unix compatible) operating system. If you are
  127. running Windows, use Cygwin.
  128. To compile any edition you need to have glib 1.2.x or newer
  129. installed. It's available at ftp://ftp.gtk.org/pub/gtk/. If you
  130. don't have glib installed already, please note that glib 2.x is much
  131. harder to compile, so your first choice should be glib 1.2.10.
  132. If you want to use mouse on the Linux console you need the gpm daemon
  133. from ftp://ftp.systemy.it/pub/develop/. You need nothing extra to
  134. use mouse on xterm.
  135. If you do not want to use the S-Lang library you could try using
  136. ncurses version 4.1 and above.
  137. 1.5 Is GNU Midnight Commander Public Domain? Copyrighted?
  138. Midnight Commander is under GNU Public License which basically means
  139. that you may freely copy, change and distribute it, but that you may
  140. not impose any restrictions on further distribution, and that you
  141. must make the source code available. This is not the same as Public
  142. Domain. For details, the GNU license is included in GNU Midnight
  143. Commander source distribution (the COPYING file).
  144. Midnight Commander is now officially a part of the GNU project.
  145. All the authors of GNU Midnight Commander have given all their rights
  146. on the program to the Free Software Foundation.
  147. 1.6 Where can I get GNU Midnight Commander?
  148. The main site is ftp://ftp.gnome.org/pub/GNOME/stable/sources/mc/
  149. 1.7 I don't have FTP access. Where can I get MC?
  150. Most GNU/Linux distributions include GNU Midnight Commander. For
  151. example, Debian, Mandrake, Red Hat, Slackware and SuSE.
  152. 1.8 I cannot compile MC. What should I do?
  153. Make sure you have read the INSTALL file in the sources. Report the
  154. error messages exactly as they appear, mention the versions of your
  155. OS, your compiler and whatever else software you think is relevant.
  156. If you have compile problems in the VFS code, try disabling it by
  157. using "--without-vfs" switch. As the last resort, you can use
  158. precompiled binaries from the GNU Midnight Commander website.
  159. 2 Keyboard
  160. 2.1 What does documentation mean with the C-?, M-? and F? keys?
  161. GNU Midnight Commander documentation uses emacs style names for
  162. keyboard keys.
  163. C stands for the Ctrl key. For example, C-f means that you should
  164. hold down the Ctrl key and press the f key.
  165. M stands for the Meta key. Your terminal might call it Alt or
  166. Compose instead of Meta. For example, M-f means that you should hold
  167. down the Meta/Alt/Compose key and press the f key. If your terminal
  168. doesn't have Meta, Alt or Compose or they don't work you can use Esc.
  169. For M-f press the Esc key and then press the f key.
  170. Sometimes Ctrl and Alt are used instead of C and M for simplicity.
  171. Keep in mind that Alt can actually be Meta on some keyboards.
  172. F? stands for a function key. If your terminal doesn't have function
  173. keys or they don't work you can use Esc. For example, for F3 press
  174. the Esc key and then press the 3 key.
  175. 2.2 Why don't function keys (or some other key) work?
  176. Your terminfo or termcap database has missing or incorrect
  177. definitions for function keys. Type "mc -V" to see what terminal
  178. database is being used. If the result is "using the S-Lang library
  179. with terminfo database" and you are using a very old terminfo
  180. database, consider installing one of the enhanced terminfo files
  181. included in GNU Midnight Commander source distribution. For example,
  182. if you are using xterm type "tic xterm.ti".
  183. If the result is "using the S-Lang library with termcap database" you
  184. should fix your /etc/termcap database.
  185. Up-to-date termcap and terminfo databases are available here:
  186. http://www.tuxedo.org/~esr/terminfo/
  187. ftp://dickey.his.com/ncurses/
  188. You can force Midnight Commander to use the termcap database by
  189. giving --with-termcap option to the configure script. The default
  190. is to use terminfo.
  191. If you don't have permissions to edit terminal databases you can use
  192. Learn keys feature of Midnight Commander instead. Press Esc 9 o k
  193. and follow instructions.
  194. If all else fails you can emulate function keys by first pressing the
  195. ESC key and then one of the number keys. For example, if you want to
  196. produce F9, press ESC, then 9. If you don't have a ESC key on your
  197. keyboard you can try alt-9 or meta-9.
  198. 2.3 How do I use function keys F11 to F20?
  199. These are normally mapped to function keys F1 to F10 with Shift held,
  200. e.g. function key F13 can be activated by pressing Shift-F3. You can
  201. define the keys this way in the Options->Learn Keys dialog. The
  202. convention for PC keyboards is that F11-20 always means Shift with
  203. F1-10.
  204. You may find that on the Linux console with some keyboard layouts
  205. Shift-Fn is interpreted as F(n+12), not as F(n+10). This is a result
  206. of non-uniformity of keyboard layouts. This is not an intended
  207. behavior and it may be fixed some day. In the meantime, use "Learn
  208. Keys" to remedy this inconvenience.
  209. 2.4 Why does the ESC key behave funny?
  210. Midnight Commander uses the ESC key as a prefix for simulating the
  211. Meta and Alt keys (for terminals which don't have Meta or Alt, see
  212. the three previous questions). For example, pressing ESC-a is the
  213. same as pressing Meta-a. In addition most terminals use ESC for
  214. internal representation of arrow keys, function keys and other
  215. enhanced keys. If you want to use ESC to cancel things you have to
  216. press it twice i.e. ESC-ESC. If you find this cumbersome you can
  217. generally use F10 to cancel. Alternatively turn on the old_esc_mode
  218. setting in the ~/.mc/ini file. The old_esc_mode setting makes ESC
  219. work as a prefix only if another key is pressed within 0.5 seconds.
  220. After 0.5 seconds the ESC key cancels. There is no way to make ESC
  221. cancel immediately (if we want to be able to use arrows keys and
  222. function keys).
  223. 2.5 How can I add the plus sign (+) on the command line?
  224. Press C-q first, then press the + sign.
  225. The plus key is the hotkey for the select files command. If you want
  226. to add a literal plus on to the command line you must quote it by
  227. pressing C-q first.
  228. Another common key which needs the C-q prefix is backslash "\".
  229. 2.6 C-o doesn't work!
  230. Maybe C-o is a stty control character on your terminal. See man stty
  231. for details on how to list and change stty control characters.
  232. 2.7 What 'keys' are the "a1" and "c1" keys mentioned in the manual?
  233. The "a1" key is the key which has the "a1" caption on it.
  234. The "c1" key is the key which has the "c1" caption on it.
  235. If you have to ask what these two keys are your keyboard hasn't
  236. probably got them. Actually, I have never seen a keyboard which has
  237. got them.
  238. 2.8 How do I change the key bindings?
  239. There is no generic way to reconfigure the key bindings. You can use
  240. the "Learn Keys" dialog to assign keys to some actions listed in that
  241. dialog. However, most actions cannot be redefined to use different
  242. keys.
  243. 3 Mouse
  244. 3.1 How do I enable mouse support?
  245. Invoke mc like this (without quotes): "mc -x". If this doesn't work
  246. upgrade to a terminal which compatible with the Xterm mouse
  247. sequences.
  248. Alternatively, on Linux console you can use gpm.
  249. 3.2 How do I cut and paste text with mouse?
  250. Hold down shift key while using mouse to cut and paste.
  251. 3.3 How do I get the extension dependent pop-up menu to pop up?
  252. It was developed for the GNOME edition. The text-mode edition
  253. doesn't support this feature yet.
  254. 4 Display
  255. 4.1 Why do I keep getting "Terminal not powerful enough for SLang" or
  256. "Terminal not powerful enough for SLsmg"?
  257. This means that your terminfo databases do not contain the correct
  258. definitions for your terminal.
  259. You could try using a different terminal setting. If you use csh or
  260. tcsh:
  261. setenv TERM vt100
  262. or if you use sh, bash, ksh or zsh:
  263. export TERM=vt100
  264. If this doesn't help you can recompile MC to use termcap instead of
  265. terminfo:
  266. ./configure --with-termcap
  267. make
  268. 4.2 Why don't line drawing characters work?
  269. Since version 4.0.13 there's the command line option -a to force use
  270. of charaters +, |, - for line drawing (only available when compiled
  271. with S-Lang). Use the -a option if any of the suggestions below
  272. doesn't help.
  273. In general, there are three cases:
  274. * Lines are shown as ASCII characters like this
  275. +---------+
  276. | |
  277. +---------+
  278. This also happens when you use the -a option. Other than that
  279. possible reason is 1 or 2 (see below).
  280. * Lines are shown as lower case characters like this
  281. lqqqqqqqqqk
  282. x x
  283. mqqqqqqqqqj
  284. Possible reason is 1 or 2 (see below).
  285. * Lines are shown as blanks or missing characters. Possible reason
  286. is 2 or 3 (see below).
  287. The reason for the problem is one of following:
  288. 1. Your terminal might not support line drawing characters. VT100
  289. compatible terminals, rxvt and xterm and color_xterm do support
  290. them.
  291. 2. Your terminfo or termcap database might have missing or incorrect
  292. definitions for line drawing characters. Set the acsc variable
  293. in the terminfo database like this:
  294. acsc=a\376k\277l\332m\300j\331n\305w\302v\301u\264t\303q\304x
  295. \263h\2600\333
  296. Don't forget issue 'tic' command. This supposes you are using PC
  297. character set. The octal values might be different for other
  298. character sets. If you are using termcap instead of terminfo,
  299. you should modify above solution appropriately.
  300. 3. Your terminal font might not support line drawing characters.
  301. Try changing the font.
  302. Here is Miguel's answer to Torben on this subject.
  303. Torben:
  304. When I load consolefonts/iso01.f16, I get perfectly right national
  305. characters, but the line drawing characters in mc get wrong. Is it
  306. a mc problem, or is it a problem with the font? (I guess it is).
  307. Is there a trick?
  308. Miguel:
  309. First of all, we should determine whether the font has line drawing
  310. characters or not.
  311. If it has line drawing characters, then a new terminfo entry should
  312. be written for this specific case. Let's call this linux-iso01.
  313. The acsc variable should be modified to reflect which characters
  314. are used to do the line drawing.
  315. If it does not have line drawing characters, then we should get rid
  316. of the switch to acsc sequences and make the acsc sequence be just
  317. a mapping to the ugly +, -, |, - characters.
  318. You can get your terminfo definition by running the infocmp
  319. program, making the proper changes and running the tic program to
  320. compile your new terminfo database.
  321. 4.3 Can one use latin-1 characters without losing the lines?
  322. Yes, you need a correct font and a correct termcap/terminfo database.
  323. For font, if you use xterm try "xterm -fn fixed".
  324. For termcap/terminfo database, change the acsc capability in the
  325. database.
  326. 4.4 I have problems with entering/viewing national characters!
  327. Upgrade to version 4.0.12 or newer.
  328. From the Options - Display Bits dialog select Full 8 bits or ISO
  329. 8859-1. In addition, select 8 bit input from the same dialog.
  330. 4.5 How can I get colors?
  331. Invoke mc like this (without quotes): "mc -c".
  332. If you get colors, be happy.
  333. If your terminal stays black and white, your terminal doesn't support
  334. color. You might want to upgrade to a terminal which compatible with
  335. the ANSI color sequences.
  336. If your terminal goes completely black, see the next question.
  337. More detailed answer:
  338. Check that your terminal supports color. color_xterm, rxvt and Linux
  339. console do support, most other terminals don't. You can test color
  340. support with following simple C program:
  341. #include <stdio.h>
  342. int main (void){
  343. printf ("\033[32m Hello world! \033[m\n");
  344. return 0;
  345. }
  346. Compile and run it. If you see "Hello world!" text in green your
  347. terminal supports color, otherwise not (however, for color_xterm see
  348. also the next question).
  349. Check whether you are using Ncurses or the S-Lang library (type
  350. "mc -V" to find out).
  351. With S-Lang library you can force color support by setting the
  352. environment variable COLORTERM to any value.
  353. If you use ncurses library, check that your terminfo database
  354. supports color. If not, you should install one of the enhanced
  355. terminfo databases included in GNU Midnight Commander source
  356. distribution.
  357. You might want to set the TERM environment variable so that you are
  358. using the correct terminfo database or termcap entry.
  359. If you use color_xterm (or rxvt) the correct value might be
  360. xterm-color, xtermc or simply xterm.
  361. If you use Linux console the correct value for TERM is linux or
  362. console.
  363. 4.6 My color_xterm goes completely (or partially) black!
  364. Some color_xterm terminals define all colors as black instead of the
  365. standard ANSI colors. This makes them go completely black when you
  366. try to use Midnight Commander with colors.
  367. You will have to override the defaults. Create a file
  368. "color.defaults" which has the following contents:
  369. color_xterm*color0: Black
  370. color_xterm*color1: Red
  371. color_xterm*color2: Green
  372. color_xterm*color3: Yellow
  373. color_xterm*color4: Blue
  374. color_xterm*color5: Magenta
  375. color_xterm*color6: Cyan
  376. color_xterm*color7: White
  377. color_xterm*background: White
  378. color_xterm*foreground: Black
  379. (replace color_xterm with the name of your color_xterm, color_xterm
  380. mentions its name in its title bar)
  381. Now type:
  382. xrdb -merge color.defaults
  383. Alternatively you can add the suggested contents of the
  384. color.defaults file to your .Xdefaults or .Xresources file (or what
  385. ever the name of your X configuration file is). Or you can replace
  386. your non-ANSI color_xterm with an ANSI color_xterm.
  387. 4.7 Where can I get xterm or rxvt?
  388. xterm is included with the X Window System, so you probably already
  389. have it if you have X. This version is not actively maintained, but
  390. Thomas Dickey maintains his more advanced version of xterm at
  391. ftp://dickey.his.com/xterm/
  392. rxvt has its own site http://www.rxvt.org/ - get the latest version
  393. there.
  394. 4.8 I got colors working with MC but the other programs don't work at
  395. all anymore!
  396. Midnight Commander uses terminfo database (if available) but many
  397. other programs use termcap database. If you set the TERM environment
  398. variable to a value which has no corresponding entry in termcap
  399. database those programs stop working. You should add the new value
  400. of TERM to the termcap database.
  401. Example: If you have set TERM to xterm-color locate from /etc/termcap
  402. the line which starts:
  403. xterm|vs100|xterm terminal emulator
  404. Change it to start:
  405. xterm|xterm-color|vs100|xterm terminal emulator
  406. 4.9 Why are there both terminfo and termcap? Wouldn't one database be
  407. enough?
  408. You might want to read the Unix-Haters Handbook at
  409. http://catalog.com/hopkins/unix-haters/handbook.html. It lists many
  410. more reasons why Unix sucks.
  411. You can configure which terminal database you want to use with the
  412. "--with-termcap" and "--with-terminfo" flags of configure. If you
  413. don't specify them, the configure script will try to use terminfo if
  414. available otherwise it will use termcap.
  415. 5 Graphical user interface
  416. 5.1 Xview, Tk and Gnome editions?
  417. Xview and Tk and GNOME editions have been removed from the sources.
  418. 5.2 Why is MC linked with X libraries?
  419. GNU Midnight Commander is linked with X libraries to read key
  420. modifiers from the X Server. It may be helpful to distinguish
  421. between keys that the terminal emulator reports in the same way, e.g.
  422. PgUp and Ctrl-PgUp. Versions of GNU Midnight Commander after 4.6.0
  423. will load X libraries dynamically on the systems that support it.
  424. 6 Command line problems
  425. 6.1 How do I stay in the last directory when I exit Midnight Commander?
  426. See the description of the -P option in the Options section of the
  427. manual.
  428. 6.2 How can I access command line history?
  429. Alt-h shows the last commands you executed from the command line.
  430. Duplicates are suppressed from the history. Commands executed from
  431. the subshell prompt are not shown.
  432. You can put previous commands to the command line with Alt-p. Alt-n
  433. moves you forward in history.
  434. Since version 4.1.15 all the input widgets have permanent history.
  435. You can summon the history listbox by pressing M-h.
  436. 6.3 How can I complete commands, file names, variable names and so on?
  437. Just press M-Tab. Press M-Tab again to get a listbox if there are
  438. multiple possible completions.
  439. 6.4 I am using ksh. Can I use functions defined in the .kshrc within
  440. MC?
  441. Sorry, MC only supports bash, tcsh and zsh functions. Ksh functions
  442. are not supported because ksh lacks the necessary hooks needed for
  443. subshell integration.
  444. Switch to bash or zsh. They are both quite compatible with ksh.
  445. Your ksh functions should work as such or after minimal changes.
  446. 6.5 Is there any way to include additional options or hot keys to MC?
  447. Yes, F2 invokes an user menu which fully configurable. You can add
  448. any shell commands to the user menu. See the mc(1) man page for more
  449. info.
  450. Another way to add functionality is the external panelize feature.
  451. See the mc(1) man page for more info.
  452. And finally, you can code any feature you want yourself. MC source
  453. code is free which means you can change it anyway you want. There
  454. are some limitations to make sure MC stays free. See GNU General
  455. Public License for details.
  456. 7 Virtual file systems
  457. 7.1 How can I see the contents of a tar archive?
  458. If you use keyboard just move the selection bar on the tar file and
  459. press enter. If you use mouse just double-click on the tar file.
  460. The recognized suffixes for tar archives are .tar, .tar.gz and .tgz.
  461. You can also enter a tar archive by typing "cd filename#utar" where
  462. filename is the name of the archive. In this case, the suffix is not
  463. important.
  464. 7.2 How do I get out of a tar archive?
  465. Just press enter on the toplevel ".." file or change to a non-tar
  466. directory. Just typing "cd" with no parameters is enough (it will
  467. take you to your home directory).
  468. 7.3 How do I do anonymous ftp with MC?
  469. Just type "cd ftp://hostname" where hostname is the name of the host
  470. you want to connect. Alternatively, select FTP link from the Left or
  471. Right menu and type the name of the host you want to connect.
  472. 7.4 How do I do non-anonymous ftp with MC?
  473. Non-anonymous ftp works just like the anonymous ftp but you give the
  474. login name with the host name. For example, type "cd
  475. ftp://username@hostname".
  476. 7.5 How do I close an ftp connection?
  477. Just change to a non-ftp directory. Simply typing "cd" with no
  478. parameters is enough (it will take you to your home directory).
  479. GNU Midnight Commander closes ftp connection automatically after a
  480. timeout or on exit. It's possible to force disconnect by selecting
  481. "Command" -> "Active VFS List" in the menu and using the "Free VFSs
  482. Now" button.
  483. 7.6 Why aren't the contents of ftp panel updated?
  484. Update is skipped because there would be a serious performance
  485. penalty. Constantly updating directory panels through a ftp
  486. connection would take too much time.
  487. You can use C-r to force an update.
  488. 7.7 What kind of proxy server works with Midnight Commander?
  489. There are two kinds of ftp proxies: proxies for ftp clients and
  490. proxies for web browsers.
  491. Midnight Commander only supports ftp proxies which are meant for ftp
  492. clients. Common WWW proxies (like Squid) are not supported. A rule
  493. of thumb is that if a ftp proxy requires a web browser, it won't work
  494. with Midnight Commander.
  495. 8 Other common problems
  496. 8.1 When I try pasting to the internal editor, it indents the amount of
  497. indenting increases with each line!
  498. Either turn of 'Return does autoindent' in the editor options or
  499. update GNU Midnight Commander to version 4.6.0 or above - it doesn't
  500. autoindent when you are holding Shift.
  501. 8.2 Is it possible to use Colorer for syntax highlighting?
  502. Yes if you submit the patch. There are no legal problems with it
  503. because it's licensed under GPL now. The homepage of Colorer is
  504. http://colorer.sourceforge.net/
  505. 9 Other common problems
  506. 9.1 Is there any way to 'bookmark' favorite ftp-fs links?
  507. Use the directory hotlist. Just press control-backslash. If your
  508. national keyboard layout doesn't have backslash key, just press the
  509. control key with the key which is the backslash key in the English
  510. keyboard layout.
  511. 9.2 When I start Midnight Commander, nothing happens!
  512. First, invoke MC without subshell support: "mc -u". If this helps
  513. check the shell you are using. Subshell support works best with
  514. bash, although tcsh and zsh are also supported. You might want to
  515. upgrade your shell to a newer version. If you use something else
  516. than bash, tcsh or zsh, subshell support is disabled automatically.
  517. If disabling subshell doesn't help, try to reconfigure MC with
  518. "--with-included-slang" and "--with-termcap" options and recompile.
  519. If this helps, something is wrong with your terminfo database or
  520. shared S-Lang library. For better terminfo databases see chapter 4
  521. of this FAQ. For a better S-Lang library, upgrade to a newer version
  522. or keep using the "--with-included-slang" option.
  523. Another reason is problems with gpm. Try using "--nomouse" option to
  524. see if it makes any difference. Restarting gpm can help. Sometimes
  525. it's enough to move the mouse.
  526. Also, if you have the DISPLAY environment variable set, but the X
  527. server is unreachable (e.g. it's firewalled), this can also cause a
  528. delay at startup. Unset DISPLAY to see if that's the case.
  529. 10 Development
  530. 10.1 Who has written Midnight Commander?
  531. Midnight Commander was started by Miguel de Icaza and he is the
  532. maintainer of the package. Other authors have joined the project
  533. later:
  534. * Mauricio Plaza (early releases)
  535. * Janne Kukonlehto (joined Sep 27 1994)
  536. * Radek Doulik (joined Oct 30 1994)
  537. * Fred Leeflang (joined Nov 2 1994)
  538. * Dugan Porter (joined Dec 1 1994)
  539. * Jakub Jelinek (joined Feb 8 1995)
  540. * Ching Hui (joined Jun 27 1995)
  541. * Andrej Borsenkow (joined Jul 1996)
  542. * Paul Sheer (joined Nov 1 1996)
  543. * Norbert Warmuth
  544. * Alex I. Tkachenko
  545. Alessandro Rubini has been specially helpful with debugging and
  546. enhancing of the mouse support. John E. Davis has made his S-Lang
  547. library available to us and answered many questions about it.
  548. Many people have contributed bug reports, feature suggestions and
  549. small code bits (alphabetical order):
  550. * Thomasz Cholewo
  551. * Juan Jose Ciarlante
  552. * Alexander Dong (OS/2 port, NT port updates)
  553. * Erwin van Eijk
  554. * Torben Fjerdingstad
  555. * Massimo Fontanelli
  556. * Juan Grigera (NT port)
  557. * Gerd Knorr
  558. * Sergey Ya. Korshunoff
  559. * Jean-Daniel Luiset
  560. * Wim Osterholt
  561. * Antonio Palama (old DOS port)
  562. * Thomas Pundt
  563. * Marcelo Roccasalva
  564. * Ilya Rybkin
  565. * Vadim Sinolits
  566. * Jon Stevens
  567. * Adam Tla/lka
  568. 10.2 Do I dare to use a development version?
  569. That's up to you to decide. Development versions may have nasty bugs
  570. at some points of time. It's up to you to judge whether the new
  571. features and fixes for the bugs you know outweigh the risk of unknown
  572. bugs.
  573. 10.3 How can I report a bug/request for a feature?
  574. You might first want to get the newest development version to see if
  575. the bug is fixed or the feature is added already.
  576. Send your report/request to mc-devel@gnome.org or mc@gnome.org.
  577. These mailing lists are the most certain way to contact the
  578. developers. Remember to mention if you are not on the mailing list
  579. to make sure that you will receive a copy of replies.
  580. Give as much details as possible. A too long message is a lot better
  581. than a too short message.
  582. For segmentation faults a stack backtrace is appreciated. You can
  583. produce stack backtrace as follows:
  584. * If segmentation fault produced a core file:
  585. 1. Load the core file by typing "gdb mc core" or "dbx mc core".
  586. 2. Type "where".
  587. 3. Cut and paste the results to your message.
  588. * If segmentation fault didn't produce a core file:
  589. 1. Load mc by typing "gdb mc" or "dbx mc".
  590. 2. Start mc by typing "run".
  591. 3. Try to reproduce the segmentation fault by doing whatever
  592. you did last time when the segmentation fault occurred.
  593. 4. Type "where".
  594. 5. Cut and paste the results to your message.
  595. 6. For the future you might want to check out what is the
  596. command in your shell to allow producing of the core files.
  597. Usually it is "limit coredumpsize unlimited" or "ulimit
  598. coredumpsize" or "ulimit -c unlimited".
  599. 10.4 How can I join the development?
  600. To join the development just code the feature you want to add and
  601. send your patch for inclusion. Email address is mc-devel@gnome.org.
  602. Before you start coding check the latest development version. It
  603. might be that your feature has already been implemented.
  604. Note that the authors of GNU Midnight Commander have given all their
  605. rights on the program to the Free Software Foundation. You will have
  606. to do the same if you contribute non-trivial patches. Otherwise we
  607. have to reject your patches in order to avoid copyright problems.
  608. 11 More information
  609. 11.1 This document didn't answer my question. Where else can I look for
  610. an answer?
  611. Read messages from the Discussion (mailing list archive) or read the
  612. Manual.
  613. Upgrade to a newer version of Midnight Commander. Many problems are
  614. fixed in the new versions.
  615. If you still can't find an answer, post your question to the Midnight
  616. Commander mailing list. Its address is mc@gnome.org.
  617. 11.2 What mailing lists are there for Midnight Commander?
  618. Following mailing lists discuss about Midnight Commander:
  619. mc@gnome.org
  620. General discussion of GNU Midnight Commander
  621. To subscribe visit
  622. http://mail.gnome.org/mailman/listinfo/mc/
  623. mc-devel@gnome.org
  624. Technical development discussion
  625. To subscribe visit
  626. http://mail.gnome.org/mailman/listinfo/mc-devel/
  627. 11.3 Where should I look on the World Wide Web for MC stuff?
  628. There is a WWW page for Midnight Commander. The URL is:
  629. http://www.ibiblio.org/mc/
  630. 11.4 Are the mailing lists archived anywhere?
  631. The mc and mc-devel lists are archived on the World Wide Web. There
  632. are links to the archives on the mailing list pages (see 10.2).
  633. 12 Legal issues
  634. 12.1 Authorship
  635. Questions and Answers was written by Janne Kukonlehto. Parts of it
  636. originate from Ian Jackson, Miguel de Icaza, Dugan Porter, Norbert
  637. Warmuth and Paul Sheer.
  638. 12.2 Feedback is invited
  639. Send your comments about this document and GNU Midnight Commander to
  640. mc@gnome.org
  641. 12.3 Disclaimer and copyright
  642. Note that this document is provided as is. The information in it is
  643. not warranted to be correct; you use it at your own risk.
  644. You can use Questions and Answers according to GNU General Public
  645. License (see the COPYING file in GNU Midnight Commander source
  646. distribution). Questions and Answers is not public domain.