FAQ 35 KB

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