FAQ 37 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994
  1. Midnight Commander
  2. Questions and Answers
  3. The newest version of this document is available at
  4. http://www.gnome.org/mc/answers.html
  5. The [NEW] tag marks the sections which have been added recently.
  6. The [UPDATED] tag marks the sections which have been updated recently.
  7. * 1 Getting started
  8. + 1.1 What is Midnight Commander?
  9. + 1.2 Does it run on my machine?
  10. + 1.3 Does it work with my terminal?
  11. + 1.4 What else do I need to run MC?
  12. + 1.5 Is Midnight Commander PD? Copyrighted?
  13. + 1.6 Where can I get Midnight Commander?
  14. + 1.7 I don't have FTP access. Where can I get MC?
  15. * 2 Keyboard
  16. + 2.1 What does documentation mean with the C-?, M-? and F?
  17. keys?
  18. + 2.2 [UPDATED] Why don't function keys (or some other key)
  19. work?
  20. + 2.3 How do I use function keys F11 to F20?
  21. + 2.4 Why does the ESC key behave funny?
  22. + 2.5 How can I add the plus sign (+) on the command line?
  23. + 2.6 [NEW] C-o doesn't work!
  24. + 2.7 [NEW] What 'keys' are the "a1" and "c1" keys mentioned in
  25. the manual?
  26. * 3 Mouse
  27. + 3.1 How do I enable mouse support?
  28. + 3.2 How do I cut and paste text with mouse?
  29. + 3.3 [NEW] How do I get the extension dependant pop-up menu to
  30. pop up?
  31. * 4 Display
  32. + 4.1 Why do I keep getting "Terminal not powerful enough for
  33. SLang"?
  34. + 4.2 Why don't line drawing characters work?
  35. + 4.3 Can one use latin-1 characters without losing the lines?
  36. + 4.4 I have problems with entering/viewing national
  37. characters!
  38. + 4.5 How can I get colors?
  39. + 4.6 My color_xterm goes completely (or partially) black!
  40. + 4.7 Where can I get color_xterm?
  41. + 4.8 I got colors working with MC but the other programs don't
  42. work at all anymore!
  43. + 4.9 Why are there both terminfo and termcap? Wouldn't one
  44. database be enough?
  45. * 5 Graphical user interface
  46. + 5.1 [UPDATED] Xview, Tk and Gnome editions?
  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 [UPDATED] 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 .kshrc
  54. 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 [UPDATED] What kind of proxy server works with Midnight
  65. Commander?
  66. * 8 Other common problems
  67. + 8.1 How do I get the internal editor to work?
  68. + 8.2 [UPDATED] Why doesn't "mcedit newfile" work?
  69. + 8.3 Is there any way to 'bookmark' favourite ftp-fs links?
  70. + 8.4 When copying the directories lose their original date,
  71. uid and gid!
  72. + 8.5 Why I keep getting: "There is no disk in the drive.
  73. Please insert a disk into drive D:"?
  74. + 8.6 [UPDATED] When I start Midnight Commander, nothing
  75. happens!
  76. + 8.7 When I try to view a file MC hangs!
  77. * 9 Development
  78. + 9.1 Who has written Midnight Commander?
  79. + 9.2 Do I dare to use a development version?
  80. + 9.3 How can I report a bug/request for a feature?
  81. + 9.4 How can I join the development?
  82. * 10 More information
  83. + 10.1 This document didn't answer my question. Where else can
  84. I look for an answer?
  85. + 10.2 What mailing lists are there for Midnight Commander?
  86. + 10.3 Where should I look on the World Wide Web for MC stuff?
  87. + 10.4 Are the mailing lists archived anywhere?
  88. * 11 Administrivia
  89. + 11.1 Authorship
  90. + 11.2 [UPDATED] File formats
  91. + 11.3 Feedback is invited
  92. + 11.4 Disclaimer and copyright
  93. 1 Getting started
  94. 1.1 What is Midnight Commander?
  95. The Midnight Commander is a user-friendly yet powerful file manager
  96. and visual shell, useful to novice and guru alike. It provides a
  97. clear, user-friendly, and somewhat protected interface to a Unix
  98. system while making many frequent file operations more efficient and
  99. preserving the full power of the command prompt. You will wonder how
  100. you could ever live without it.
  101. For more thorough description take a look at the announcement of
  102. Midnight Commander 4.0.
  103. 1.2 Does it run on my machine?
  104. Yes, Midnight Commander can run on almost any machine, including Unix
  105. clones, Windows 95/NT and OS/2. Midnight Commander does not run on
  106. Macintosh.
  107. Midnight Commander uses GNU autoconfigure which can automatically
  108. configure Midnight Commander for use on almost any (if not every) Unix
  109. clone. Following configurations have been tested:
  110. * i386-*-linux1.x, 2.x
  111. * alpha-linux-linux2
  112. * sparc-linux-linux2.x
  113. * sparc64-linux-linux2.1
  114. * mips-sgi-irix5.x, 6.x
  115. * mips-dec-ultrix4.3
  116. * rs6000-ibm-aix3.2.5
  117. * sparc-sun-sunos4.1
  118. * sparc-sun-solaris2.3, 2.4, 2.5
  119. * sparc-sun-netbsd1.0
  120. * hppa-hp-hpux9
  121. * hppa-hp-hpux7
  122. * m68k-apple-aux
  123. * unixware
  124. * mc88110-aviion-dgux5.4R2.01
  125. * i386-*-sco3.2v4.2
  126. * i386-*-sco3.2v5
  127. * i386-*-windows-nt-3.51, 4.0
  128. * i386-*-windows95
  129. * i386-*-os2
  130. See http://www.gnome.org/mc/download.html.
  131. There is also a preliminary Ms-Dos port at
  132. http://www.gnome.org/cgi-bin/mc/download/DOS/.html (but no Ms-Dos
  133. binary).
  134. Windows 95/NT port can be compiled with Microsoft Visual C++, Borland
  135. C++, Cygwin32 and Mingw32.
  136. 1.3 Does it work with my terminal?
  137. Yes, it does.
  138. Because Midnight Commander is a full screen program it doesn't run on
  139. dummy terminals but anything more advanced will do (like vt100). If
  140. your terminal works with vi, emacs, elm or pine it will work with
  141. Midnight Commander.
  142. The XView and Tk editions currently under development will require an
  143. X terminal.
  144. 1.4 What else do I need to run MC?
  145. You need an Unix compatible operating system or Windows 95/NT or OS/2.
  146. If you want to use mouse on the Linux console you need General Purpose
  147. Mouse server from iride.unipv.it: /pub/gpm/. You need nothing extra to
  148. use mouse on xterm.
  149. To compile the XView edition (currently under development) you need
  150. XView library. Xpm library and X11 non-rectangular shape extensions
  151. are recommended.
  152. To compile the Tk edition (currently under development) you need
  153. Tk-4.0 libraries. Compilation of the Tk version won't be easy. Contact
  154. Miguel for details.
  155. If you do not want to use the slang library you could try using
  156. ncurses (we recommend only version 4.1 and above).
  157. You can get it along with other curses libraries, too, but results may
  158. not be pretty or even usable.
  159. 1.5 Is Midnight Commander PD? Copyrighted?
  160. Midnight Commander is under GNU Public License which basically means
  161. that you may freely copy, change and distribute it, but that you may
  162. not impose any restrictions on further distribution, and that you must
  163. make the source code available. This is not the same as Public Domain.
  164. For details, the GNU license is included in the Midnight Commander
  165. source distribution (the COPYING file).
  166. Midnight Commander is nowadays officially a part of GNU project. All
  167. the authors of the Midnight Commander have given all their rights on
  168. the program to the Free Software Foundation.
  169. 1.6 Where can I get Midnight Commander?
  170. See http://www.gnome.org/mc/download.html. There are about seventy
  171. download sites. Note that the newest files might not be present on all
  172. the download sites yet.
  173. In short: the main site is ftp://ftp.nuclecu.unam.mx/linux/local/ and
  174. the sunsite.unc.edu mirrors have MC in the
  175. /pub/Linux/utils/file/managers/mc directory.
  176. 1.7 I don't have FTP access. Where can I get MC?
  177. Most Linux CD-ROMs include Midnight Commander. For example, Slackware,
  178. Yggdrasil, S.U.S.E., Jurix, RedHat, Caldera and Debian.
  179. 2 Keyboard
  180. 2.1 What does documentation mean with the C-?, M-? and F? keys?
  181. Midnight Commander documentation uses emacs style names for keyboard
  182. keys.
  183. C stands for the Ctrl key. For example, C-f means that you should hold
  184. down the Ctrl key and press the f key.
  185. M stands for the Meta key. Your terminal might call it Alt or Compose
  186. instead of Meta. For example, M-f means that you should hold down the
  187. Meta/Alt/Compose key and press the f key. If your terminal doesn't
  188. have Meta, Alt or Compose or they don't work you can use Esc. For M-f
  189. press the Esc key and then press the f key.
  190. F? stands for a function key. If your terminal doesn't have function
  191. keys or they don't work you can use Esc. For example, for F3 press the
  192. Esc key and then press the 3 key.
  193. 2.2 [UPDATED] Why don't function keys (or some other key) work?
  194. Your terminfo or termcap database has missing or incorrect definations
  195. for function keys. Type "mc -V" to see what terminal database is being
  196. used. If the result is "using the S-Lang library with terminfo
  197. database" you should install one of the enhanced terminfo databases
  198. included in the Midnight Commander source distribution. For example,
  199. if you are using xterm type "tic xterm.ti".
  200. If the result is "using the S-Lang library with termcap database" you
  201. should fix your /etc/termcap database.
  202. Better termcap and terminfo databases are available here:
  203. http://sagan.earthspace.net/~esr/terminfo/
  204. Best terminfo database is bundled with ncurses 4.2.
  205. You can select whether Midnight Commander will use terminfo or termcap
  206. database by giving --with-terminfo or --with-termcap option to the
  207. configure. Default is terminfo if found, otherwise termcap.
  208. If you don't have permissions to edit terminal databases you can use
  209. Learn keys feature of Midnight Commander instead. Press Esc 9 o k and
  210. follow instructions.
  211. If all else fails you can emulate function keys by first pressing the
  212. ESC key and then one of the number keys. For example, if you want to
  213. produce F9, press ESC, then 9. If you don't have a ESC key on your
  214. keyboard you can try alt-9 or meta-9.
  215. 2.3 How do I use function keys F11 to F20?
  216. These can mapped to function keys F1 to F10 with Shift held. eg.
  217. function key F13 can be activated by pressing Shift-F3. You can define
  218. the keys this way in the Options menu. The convention for PC keyboards
  219. is that F11-20 always means Shift with F1-10
  220. Note! Windows 95/NT and OS/2 ports use F11 and F12 keys to change the
  221. current disk drive. In this case F11 and F12 mean the real F11 and F12
  222. keys, not shift-F1 and shift-F2.
  223. 2.4 Why does the ESC key behave funny?
  224. Midnight Commander uses the ESC key as a prefix for simulating the
  225. Meta and Alt keys (for terminals which don't have Meta or Alt, see the
  226. three previous questions). For example, pressing ESC-a is the same as
  227. pressing Meta-a. In addition most terminals use ESC for internal
  228. representation of arrow keys, function keys and other enhanced keys.
  229. If you want to use ESC to cancel things you have to press it twice i.
  230. e. ESC-ESC. If you find this cumbersome you can generally use F10 to
  231. cancel. Alternatively turn on the old_esc_mode setting in the
  232. ~/.mc.ini file. The old_esc_mode setting makes ESC work as a prefix
  233. only if another key is pressed within 0.5 seconds. After 0.5 seconds
  234. the ESC key cancels. There is no way to make ESC cancel immediately
  235. (if we want to be able to use arrows keys and function keys).
  236. X terminals allow more control over keyboard, so these ESC limitations
  237. might not concern the forthcoming XView and Tk editions of the
  238. Midnight Commander.
  239. 2.5 How can I add the plus sign (+) on the command line?
  240. Press C-q first, then press the + sign.
  241. The plus key is the hotkey for the select files command. If you want
  242. to add a literal plus on to the command line you must quote it by
  243. pressing C-q first.
  244. Another common key which needs the C-q prefix is backslash "\".
  245. 2.6 [NEW] C-o doesn't work!
  246. Maybe C-o is a stty control character on your terminal. See man stty
  247. for details on how to list and change stty control characters.
  248. 2.7 [NEW] What 'keys' are the "a1" and "c1" keys mentioned in the manual?
  249. The "a1" key is the key which has the "a1" caption on it.
  250. The "c1" key is the key which has the "c1" caption on it.
  251. If you have to ask what these two keys are your keyboard hasn't
  252. probably got them. Actually, I have never seen a keyboard which has
  253. got them.
  254. 3 Mouse
  255. 3.1 How do I enable mouse support?
  256. Invoke mc like this (without quotes): "mc -x". If this doesn't work
  257. upgrade to a terminal which compatible with the Xterm mouse sequences.
  258. Alternatively, on Linux console you can use GPM.
  259. 3.2 How do I cut and paste text with mouse?
  260. Hold down shift key while using mouse to cut'n'paste.
  261. 3.3 [NEW] How do I get the extension dependant pop-up menu to pop up?
  262. You need a tk or xview edition (use the --with-tk or --with-xview
  263. configure option when compiling). Normal MC (text-mode edition)
  264. doesn't support this feature yet.
  265. In the tk and xview editions you can access the extension dependent
  266. pop-up menu by pressing the right mouse button.
  267. 4 Display
  268. 4.1 Why do I keep getting "Terminal not powerful enough for SLang"?
  269. This means that your terminfo databases do not contain the correct
  270. definitions for your terminal.
  271. You could try using a different terminal setting. If you use csh or
  272. tcsh:
  273. setenv TERM vt100
  274. or if you use sh, bash, ksh or zsh:
  275. export TERM=vt100
  276. If this doesn't help you can recompile MC to use termcap instead of
  277. terminfo:
  278. ./configure --with-termcap
  279. make
  280. 4.2 Why don't line drawing characters work?
  281. Since version 4.0.13 there's the commandline option -a to force use of
  282. +, |, - for line drawing (only available when compiled with SLang).
  283. Use this -a option if any of the suggestions below doesn't help.
  284. In general, there are three subcases:
  285. * Lines are shown as ASCII characters like this
  286. +---------+
  287. | |
  288. +---------+
  289. This also happens when you use the -a option. Other than that
  290. possible reason is 1, 2 or 3 (see below).
  291. * Lines are shown as lower case characters like this
  292. lqqqqqqqqqk
  293. x x
  294. mqqqqqqqqqj
  295. Possible reason is 2 or 3 (see below).
  296. * Lines are shown as blanks or missing characters. Possible reason
  297. is 3 or 4 (see below).
  298. The reason for the problem is one of following:
  299. 1. Your curses library might not support line drawing characters.
  300. Slang, Ncurses and System V curses do support them, BSD curses
  301. doesn't. MC uses Slang by default so this is not usually a
  302. problem.
  303. 2. Your terminal might not support line drawing characters. Vt100
  304. compatible terminals, rxvt, xterm and color_xterm do support them.
  305. 3. Your terminfo or termcap database might have missing or incorrect
  306. definations for line drawing characters. Set the acsc variable in
  307. the terminfo database like this:
  308. acsc=a\376k\277l\332m\300j\331n\305w\302v\301u\264t\303q\304x\263h
  309. \2600\333
  310. Don't forget issue 'tic' command. This supposes you are using pc
  311. character set. The octal values might be different for other
  312. character sets. If you are using termcap instead of terminfo, you
  313. should modify above solution appropriately.
  314. 4. Your terminal font might not support line drawing characters. Try
  315. changing the font.
  316. Here is Miguel's answer to Torben on this subject.
  317. Torben:
  318. When I load consolefonts/iso01.f16, I get perfectly right national
  319. characters, but the line drawing characters in mc get wrong. Is it
  320. a mc problem, or is it a problem with the font? (I guess it is).
  321. Is there a trick?
  322. Miguel:
  323. First of all, we should determine whether the font has line drawing
  324. characters or not.
  325. If it has line drawing characters, then a new terminfo entry should
  326. be written for this specific case. Let's call this linux-iso01. The
  327. acsc variable should be modified to reflect which characters are
  328. used to do the line drawing.
  329. If it does not have line drawing characters, then we should get rid
  330. of the switch to acsc sequences and make the acsc sequence be just
  331. a mapping to the ugly +, -, |, - characters.
  332. You can get your terminfo definition by running the infocmp
  333. program, making the proper changes and running the tic program to
  334. compile your new terminfo database.
  335. 4.3 Can one use latin-1 characters without losing the lines?
  336. Yes, you need a correct font and a correct termcap/terminfo database.
  337. For font, if you use xterm try "xterm -fn fixed".
  338. For termcap/terminfo database, change the acsc capability in the
  339. database.
  340. 4.4 I have problems with entering/viewing national characters!
  341. Upgrade to version 4.0.12 or newer.
  342. From the Options - Display Bits dialog select Full 8 bits or ISO
  343. 8859-1. In addition, select 8 bit input from the same dialog.
  344. 4.5 How can I get colors?
  345. Invoke mc like this (without quotes): "mc -c".
  346. If you get colors, be happy.
  347. If your terminal stays black and white, your terminal doesn't support
  348. color. You might want to upgrade to a terminal which compatible with
  349. the ANSI color sequences.
  350. If your terminal goes compelety black, see the next question.
  351. More detailed answer:
  352. First, check that your terminal supports color. Color_xterm, rxvt and
  353. Linux console do support, most other terminals don't. You can test
  354. color support with following simple C program:
  355. #include <stdio.h>
  356. int main (void){
  357. printf ("\033[32m Hello world! \033[m\n");
  358. return 0;
  359. }
  360. Compile and run it. If you see "Hello world!" text in green your
  361. terminal supports color, otherwise not (however, for color_xterm see
  362. also the next question).
  363. Second, check that you are using Ncurses or the Slang library (type
  364. "mc -V" to find out), in addition some System V curses implementations
  365. do support color, most don't.
  366. With Slang library you can force color support by setting the
  367. environment variable COLORTERM to any value.
  368. Third, if you use ncurses library, check that your terminfo database
  369. supports color. If not you should install one of the enhanced terminfo
  370. databases included in the Midnight Commander source distribution.
  371. Fourth, you might want to set the TERM environment variable so that
  372. you use the correct terminfo database or termcap entry.
  373. If you use color_xterm (or rxvt) the correct value might be
  374. xterm-color, xtermc or simply xterm.
  375. If you use Linux console the correct value for TERM is linux or
  376. console.
  377. 4.6 My color_xterm goes completely (or partially) black!
  378. Some color_xterm terminals define all colors as black instead of the
  379. standard ANSI colors. This makes them go completely black when you try
  380. to use Midnight Commander with colors.
  381. You will have to override the defaults. Create a file "color.defaults"
  382. which has the following contents:
  383. color_xterm*color0: Black
  384. color_xterm*color1: Red
  385. color_xterm*color2: Green
  386. color_xterm*color3: Yellow
  387. color_xterm*color4: Blue
  388. color_xterm*color5: Magenta
  389. color_xterm*color6: Cyan
  390. color_xterm*color7: White
  391. color_xterm*background: White
  392. color_xterm*foreground: Black
  393. (replace color_xterm with the name of your color_xterm, color_xterm
  394. mentions its name in its title bar)
  395. Now type:
  396. xrdb -merge color.defaults
  397. Alternatively you can add the suggested contents of the color.defaults
  398. file to your .Xdefaults or .Xresources file (or what ever the name of
  399. your X configuration file is). Or you can replace your non-ANSI
  400. color_xterm with an ANSI color_xterm.
  401. 4.7 Where can I get color_xterm?
  402. Try ftp.x.org: /contrib/utilities/colour_xterm.tar.gz.
  403. Alternatively, rxvt is a better choice, see
  404. http://www.gnome.org/cgi-bin/mc/download/rxvt/.html
  405. 4.8 I got colors working with MC but the other programs don't work at all
  406. anymore!
  407. Midnight Commander uses terminfo database (if available) but many
  408. other programs use termcap database. If you set the TERM environment
  409. variable to a value which has no corresponding entry in termcap
  410. database those programs stop working. You should add the new value of
  411. TERM to the termcap database.
  412. Example: If you have set TERM to xterm-color locate from /etc/termcap
  413. the line which starts:
  414. xterm|vs100|xterm terminal emulator
  415. Change it to start:
  416. xterm|xterm-color|vs100|xterm terminal emulator
  417. 4.9 Why are there both terminfo and termcap? Wouldn't one database be
  418. enough?
  419. You might want to read the Unix-haters handbook at
  420. http://www.digital.de/people/jmh/Unix_Haters/unix-haters.html. It
  421. lists many more reasons why Unix sucks.
  422. You can configure which terminal database you want to use with the
  423. "--with-termcap" and "--with-terminfo" flags of configure. If you
  424. don't specify them, the configure script will try to use terminfo if
  425. available otherwise it will use termcap.
  426. 5 Graphical user interface
  427. 5.1 [UPDATED] Xview, Tk and Gnome editions?
  428. Get the newest development version, give the "--with-xview" or
  429. "--with-tk" or "--with-gnome" option to the configure and otherwise
  430. compile as usual. See Download.
  431. Xview, Tk and Gnome editions are work in progress, they are not as
  432. robust as the text mode edition.
  433. 6 Command line problems
  434. 6.1 How do I stay in the last directory when I exit Midnight Commander?
  435. See the description of the -P option in the Options section of the
  436. manual.
  437. 6.2 [UPDATED] How can I access command line history?
  438. You can browse previous commands with M-p and M-n. Alternatively, you
  439. can summon the command history listbox by pressing F9 c h.
  440. Since version 4.1.15 all the input widgets have permanent history. You
  441. can summon the history listbox by pressing M-h.
  442. 6.3 How can I complete commands, file names, variable names and so on?
  443. Just press M-Tab. Press M-Tab again to get a listbox if there are
  444. multiple possible completions.
  445. 6.4 I am using ksh. Can I use functions defined in the .kshrc within MC?
  446. Sorry, MC only supports bash, tcsh and zsh functions. Ksh functions
  447. are not supported because ksh lacks the necessary hooks needed for
  448. subshell integration.
  449. Switch to bash or zsh. They are both quite compatible with ksh. Your
  450. ksh functions should work as such or after minimal changes.
  451. 6.5 Is there any way to include additional options or hot keys to MC?
  452. Yes, F2 invokes an user menu which fully configurable. You can add any
  453. shell commands to the user menu. See
  454. http://www.gnome.org/mc/manual-d.html#8 for more info.
  455. Another way to add functionality is the external panelize feature. See
  456. http://www.gnome.org/mc/manual-d.html#4 for more info.
  457. And finally, you can code any feature you want yourself. MC source
  458. code is free which means you can change it anyway you want. There are
  459. some limitations to make sure MC stays free. See GNU General Public
  460. License for details.
  461. 7 Virtual file systems
  462. Note! Virtual file systems are supported by Unix ports only. The
  463. Windows 95/NT and OS/2 ports do NOT support virtual file systems. This
  464. means you haven't got ftp, zip or tar support on Windows 95/NT and
  465. OS/2.
  466. This chapter describes the behaviour of the 4.1.x versions of the
  467. Midnight Commander. The behaviour of the 4.5.x versions is somewhat
  468. different. More on that when the 4.5.x versions get more stable.
  469. 7.1 How can I see the contents of a tar archive?
  470. If you use keyboard just move the selection bar on the tar file and
  471. press enter.
  472. If you use mouse just doubleclick on the tar file.
  473. If these procedures don't work, your .mc.ext file is faulty. Replace
  474. it with one from the MC source distribution.
  475. You can also enter a tar archive by typing "cd tar:filename.tar.gz"
  476. where filename.tar.gz is the name of the archive.
  477. The recognized suffixes for tar archives are .tar, .tar.gz and .tgz.
  478. If your tar archive uses different suffix you have to rename it.
  479. 7.2 How do I get out of a tar archive?
  480. Just press enter on the toplevel ".." file or chdir to a non-tar
  481. directory. Just typing "cd" with no parameters is enough (it will take
  482. you to your home directory).
  483. 7.3 How do I do anonymous ftp with MC?
  484. Just type "cd ftp://hostname" where hostname is the name of the host
  485. you want to connect. Alternatively, select FTP link from the Left or
  486. Right menu and type the name of the host you want to connect.
  487. 7.4 How do I do non-anonymous ftp with MC?
  488. Non-anonymous ftp works just like the anonymous ftp but you give the
  489. login name with the host name. For example, type "cd
  490. ftp://username@hostname".
  491. 7.5 How do I close an ftp connection?
  492. Just chdir to a non-ftp directory. Just typing "cd" with no parameters
  493. is enough (it will take you to your home directory).
  494. Internally Midnight Commander closes ftp connection only after a
  495. timeout. This isn't visible to the end user.
  496. 7.6 Why aren't the contents of ftp panel updated?
  497. Update is skipped because there would be a serious performance
  498. penalty. Constantly updating directory panels through a ftp connection
  499. would take too much time.
  500. You can use C-r to force an update.
  501. 7.7 [UPDATED] What kind of proxy server works with Midnight Commander?
  502. There are two kinds of ftp proxies: proxies for ftp clients and
  503. proxies for web browsers.
  504. Midnight Commander only supports ftp proxies which are meant for ftp
  505. clients. Common WWW proxies (like Squid) are not supported. A rule of
  506. thumb is that if a ftp proxy works with a web browser, it won't work
  507. with Midnight Commander.
  508. 8 Other common problems
  509. 8.1 How do I get the internal editor to work?
  510. The F4 key used to default to an external editor because that was what
  511. most people were used to. The newer versions use internal editor by
  512. default.
  513. To use the internal editor with an old version, select Configuration
  514. from the Options menu and check the 'use internal edit' option.
  515. Alternatively add the line
  516. use_internal_edit=1
  517. under the [Midnight-Commander] section in your .mc.ini file (which is
  518. in your home directory).
  519. To make the editor work all the time, go to the default/* section in
  520. the file lib/mc/mc.ext file and remove the line
  521. Edit=%var{EDITOR:vi} %f
  522. The internal editor will now be invoked for anything not specified
  523. elsewhere in the mc.ext file.
  524. Make sure that you edit the correct mc.ext file. The Midnight
  525. Commander first checks the existance of $HOME/.mc.ext. If this file is
  526. missing MC will use $prefix/lib/mc/mc.ext instead ($prefix can be
  527. changed with configure before compilation and it defaults to
  528. /usr/local).
  529. When you run `F9/Command/Extension file edit' for the very first time
  530. Midnight Commander copies the system-wide mc.ext from $prefix/lib/mc
  531. into your home directory because you need write access in order to
  532. change it.
  533. And please don't forget that "make install" overwrites
  534. $prefix/lib/mc/mc.ext.
  535. 8.2 [UPDATED] Why doesn't "mcedit newfile" work?
  536. This is a known bug.
  537. If the newfile doesn't exist, mcedit fails.
  538. Start mcedit with no parameters, this will create a blank file. Then
  539. save the file with whatever name you like.
  540. This bug has been fixed since 4.1.17.
  541. 8.3 Is there any way to 'bookmark' favourite ftp-fs links?
  542. Use the directory hotlist. Just press control-backslash. If your
  543. national keyboard layout doesn't have backslash key, just press the
  544. control key with the key which is the backslash key in the English
  545. keyboard layout.
  546. 8.4 When copying the directories lose their original date, uid and gid!
  547. This is a known bug. At moment only files preserve their original
  548. settings when copying, not directories.
  549. Uid and gid is fixed since 4.0.1. "Preserve UIDs/GIDs" in the copy
  550. dialog needs to be checked and you must be root.
  551. Date problem is fixed since 4.0.13.
  552. 8.5 Why I keep getting: "There is no disk in the drive. Please insert a disk
  553. into drive D:"?
  554. This is a known bug of the Windows 95/NT and OS/2 ports. MC looks its
  555. configuration files from the D:\MC directory and if the D: drive is a
  556. removable drive (like a CD ROM drive) and there is no disk in drive
  557. you get this message everytime you try to do anything.
  558. Since version 4.0.6 you can specify the actual location of the
  559. Midnight Commander configuration files with the MCHOME environment
  560. variable.
  561. 8.6 [UPDATED] When I start Midnight Commander, nothing happens!
  562. First, invoke MC without subshell support: "mc -u". If this helps
  563. check the shell you are using. Subshell support works best with bash
  564. although tcsh and zsh are also supported. You might want to upgrade
  565. your shell to a newer version. If you use something else than bash,
  566. tcsh or zsh, subshell support is disabled automatically.
  567. If disabling subshell doesn't help, try to reconfigure MC with
  568. "--with-included-slang" and "--with-termcap" options and recompile. If
  569. this helps, there is something wrong with your terminfo database or
  570. shared slang library. For better terminfo databases see chapter 4. For
  571. a better slang library, upgrade to a newer version or keep using the
  572. "--with-included-slang" option.
  573. This problem can also be caused by gpm as noted by Luis Espinoza:
  574. In regards to why midnight commander does nothing when invoked. I
  575. recently had the same problem. At the same time gpm was not loading
  576. properly with my patched kernel (now 2.0.33 from 2.0.30).
  577. Downloading version 1.13 of gpm, and got it working :-) MC still
  578. appeared locked.... However moving the mouse, brought MC to life.
  579. The mouse I am using is a Kensington Expert Mouse (Trackball).
  580. 8.7 When I try to view a file MC hangs!
  581. This is known bug. A quick fix is "chmod 666 /dev/tty". For a more
  582. complete fix, see http://www.gnome.org/mc/maillist/97-10/98.html.
  583. This bug is fixed since 4.1.6.
  584. 9 Development
  585. 9.1 Who has written Midnight Commander?
  586. Midnight Commander was started by Miguel de Icaza and he is the
  587. maintainer of the package. Other authors have joined the project
  588. later:
  589. * Mauricio Plaza (early releases)
  590. * Janne Kukonlehto (joined Sep 27 1994)
  591. * Radek Doulik (joined Oct 30 1994)
  592. * Fred Leeflang (joined Nov 2 1994)
  593. * Dugan Porter (joined Dec 1 1994)
  594. * Jakub Jelinek (joined Feb 8 1995)
  595. * Ching Hui (joined Jun 27 1995)
  596. * Andrej Borsenkow (joined Jul 1996)
  597. * Paul Sheer (joined Nov 1 1996)
  598. * Norbert Warmuth
  599. * Alex I. Tkachenko
  600. Alessandro Rubini has been specially helpful with debugging and
  601. enhancing of the mouse support. John Davis has made his S-Lang library
  602. available to us and answered many questions about it.
  603. The photographs of the authors are available as:
  604. http://www.gnome.org/mc/authstat.html
  605. Many people have contributed bug reports, feature suggestions and
  606. small code bits (alphabetical order):
  607. * Thomasz Cholewo
  608. * Juan Jose Ciarlante
  609. * Alexander Dong (OS/2 port, NT port updates)
  610. * Erwin van Eijk
  611. * Torben Fjerdingstad
  612. * Massimo Fontanelli
  613. * Juan Grigera (NT port)
  614. * Gerd Knorr
  615. * Sergey Ya. Korshunoff
  616. * Jean-Daniel Luiset
  617. * Wim Osterholt
  618. * Antonio Palama (old DOS port)
  619. * Thomas Pundt
  620. * Marcelo Roccasalva
  621. * Ilya Rybkin
  622. * Vadim Sinolits
  623. * Jon Stevens
  624. * Adam Tla/lka
  625. 9.2 Do I dare to use a development version?
  626. I am afraid you have to answer to this question yourself. Development
  627. versions seldom cause data loss but they have usually got many bugs.
  628. It's up to you to judge whether new features outweight the bugs.
  629. 9.3 How can I report a bug/request for a feature?
  630. You might first want to get the newest development version to see if
  631. the bug is fixed or the feature is added already.
  632. Send your report/request to mc-devel@roxanne.nuclecu.unam.mx or
  633. mc@roxanne.nuclecu.unam.mx. These mailing lists are the most certain
  634. way to contact the developers. Remember to mention if you are not on
  635. the mailing list to make sure that you will receive a copy of replies.
  636. Give as much details as possible. A too long message is a lot better
  637. than a too short message.
  638. For segmentation faults a stack backtrace is appreciated. You can
  639. produce stack backtrace as follows:
  640. * If segmentation fault produced a core file:
  641. 1. Load the core file by typing "gdb mc core" or "dbx mc core".
  642. 2. Type "where".
  643. 3. Cut and paste the results to your message.
  644. * If segmentation fault didn't produce a core file:
  645. 1. Load mc by typing "gdb mc" or "dbx mc".
  646. 2. Start mc by typing "run".
  647. 3. Try to reproduce the segmentation fault by doing whatever you
  648. did last time when the segmentation fault occurred.
  649. 4. Type "where".
  650. 5. Cut and paste the results to your message.
  651. 6. For the future you might want to check out what is the
  652. command in your shell to allow producing of the core files.
  653. Usually it is "limit coredumpsize unlimited" or "ulimit
  654. coredumpsize" or "ulimit -c unlimited".
  655. 9.4 How can I join the development?
  656. To join the development just code the feature you want to add and send
  657. your patch for inclusion. Email address is mc-devel@nuclecu.unam.mx.
  658. Before you start coding check the latest development version. It might
  659. be that your feature has already been implemented.
  660. Note that the authors of the Midnight Commander have given all their
  661. rights on the program to the Free Software Foundation. You will have
  662. to do the same if you contribute non-trivial patches. Otherwise we
  663. have to reject your patches in order to avoid copyright problems.
  664. 10 More information
  665. 10.1 This document didn't answer my question. Where else can I look for an
  666. answer?
  667. Read messages from the Discussion (mailing list archive) or read the
  668. Manual.
  669. Upgrade to a newer version of Midnight Commander. Many problems are
  670. fixed in the new versions.
  671. If you still can't find an answer, post your question to the Midnight
  672. Commander mailing list. Its address is mc@nuclecu.unam.mx.
  673. 10.2 What mailing lists are there for Midnight Commander?
  674. Following mailing lists discuss about Midnight Commander:
  675. mc
  676. General discussion of the Midnight Commander
  677. mc-digest
  678. The mc list, in digest format
  679. mc-announce
  680. Major announcements about the Commander
  681. mc-patches
  682. The latest Commander patches
  683. mc-devel
  684. Technical development discussion
  685. mc-chat
  686. Non-MC related chatting by the developers (contact Miguel to
  687. subscribe)
  688. To subscribe, send e-mail to majordomo@roxanne.nuclecu.unam.mx with
  689. the following line in the body of the message:
  690. subscribe <list-name> [optional-address]
  691. Replace <list-name> with the name of the list you want to subscribe
  692. and [optional-address] with your email address.
  693. 10.3 Where should I look on the World Wide Web for MC stuff?
  694. There is a WWW page for Midnight Commander. The URL is:
  695. http://www.gnome.org/mc/
  696. The WWW page features MC screen shots, photographs of the authors,
  697. mailing list archive and a few other things.
  698. 10.4 Are the mailing lists archived anywhere?
  699. The mc and mc-devel lists are archived on the World Wide Web page (see
  700. the previous question). Other lists are not currently archived though
  701. Miguel keeps a private archive. Contact him if you want copies of past
  702. messages.
  703. 11 Administrivia
  704. 11.1 Authorship
  705. Questions and Answers is written by Janne Kukonlehto. Parts of it
  706. originate from Ian Jackson, Miguel de Icaza, Dugan Porter, Norbert
  707. Warmuth and Paul Sheer.
  708. 11.2 [UPDATED] File formats
  709. This document is available in HTML, postscript and PDF formats at
  710. http://www.gnome.org/mc/answers.html.
  711. This document is available in ASCII format in the Midnight Commander
  712. source package.
  713. 11.3 Feedback is invited
  714. Send your comments about this document to janne@gnome.org
  715. Send your comments about the Midnight Commander to mc@nuclecu.unam.mx
  716. 11.4 Disclaimer and copyright
  717. Note that this document is provided as is. The information in it is
  718. not warranted to be correct; you use it at your own risk.
  719. You can use Questions and Answers according to GNU Public License (see
  720. the COPYING file in the Midnight Commander source distribution).
  721. Questions and Answers is not public domain.
  722. __________________________________________________________________
  723. This document is maintained by Janne Kukonlehto <janne@gnome.org>.