mcedit.1.in 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670
  1. .TH MCEDIT 1 "%DATE_OF_MAN_PAGE%" "MC Version %DISTR_VERSION%" "GNU Midnight Commander"
  2. .SH NAME
  3. mcedit \- Internal file editor of GNU Midnight Commander.
  4. .SH USAGE
  5. .B mcedit
  6. [\-bcCdfhstVx?] [+lineno] [file1] [file2] ...
  7. .PP
  8. .B mcedit
  9. [\-bcCdfhstVx?] file1:lineno[:] file2:lineno[:] ...
  10. .SH DESCRIPTION
  11. .LP
  12. mcedit is a link to
  13. .BR mc ,
  14. the main GNU Midnight Commander executable. Executing GNU Midnight Commander
  15. under this name requests staring the internal editor and opening files
  16. specified on the command line. The editor is based on the terminal version of
  17. .B cooledit
  18. \- standalone editor for X Window System.
  19. .SH OPTIONS
  20. .TP
  21. .I "+lineno"
  22. Go to the line specified by number (do not put a space between the
  23. .I "+"
  24. sign and the number). Several line numbers are allowed but the last one will be
  25. actual and it will be applied to the first file only.
  26. .TP
  27. .I "\-b"
  28. Force black and white display.
  29. .TP
  30. .I "\-c"
  31. Force ANSI color mode on terminals that don't seem to have color
  32. support.
  33. .TP
  34. .I "\-C <keyword>=<fgcolor>,<bgcolor>,<attributes>:<keyword>= ..."
  35. Specify a different color set. See the
  36. .B Colors
  37. section in mc(1) for more information.
  38. .TP
  39. .I "\-d"
  40. Disable mouse support.
  41. .TP
  42. .I "\-f"
  43. Display the compiled\-in search path for GNU Midnight Commander data
  44. files.
  45. .TP
  46. .I "\-t"
  47. Force using termcap database instead of terminfo. This option is only
  48. applicable if GNU Midnight Commander was compiled with S\-Lang library
  49. with terminfo support.
  50. .TP
  51. .I "\-V"
  52. Display the version of the program.
  53. .TP
  54. .I "\-x"
  55. Force xterm mode. Used when running on xterm\-capable terminals (two
  56. screen modes, and able to send mouse escape sequences).
  57. .SH FEATURES
  58. The internal file editor is a full\-featured windowed editor. It can
  59. edit several files at the same time. Maximim size of each file is 64
  60. megabytes. It is possible to edit binary files. The features it presently
  61. supports are: block copy, move, delete, cut, paste; key for key undo;
  62. pull\-down menus; file insertion; macro commands; regular expression
  63. search and replace; shift\-arrow text highlighting (if supported by
  64. the terminal); insert\-overwrite toggle; autoindent; tunable tab size;
  65. syntax highlighting for various file types; and an option to pipe text
  66. blocks through shell commands like indent and ispell.
  67. .PP
  68. Each file is opened in its own window in full\-screen mode. Window control
  69. in mcedit is similar to the window control in other multi\-window program:
  70. double click on window title maximizes the window to full\-screen or restores
  71. window size and position; left\-click on window title and mouse drag moves
  72. the window in editor area; left\-click on low\-right frame corner and mouse drag
  73. resizes the window. These actions can be made using "Window" menu.
  74. .SH KEYS
  75. The editor is easy to use and can be used without learning. The
  76. pull\-down menu is invoked by pressing F9. You can learn other keys from
  77. the menu and from the button bar labels.
  78. .PP
  79. In addition to that, Shift combined with arrows does text highlighting
  80. (if supported by the terminal):
  81. .B Ctrl\-Ins
  82. copies to the file
  83. .BR ~/.cache/mc/mcedit/mcedit.clip ,
  84. .B Shift\-Ins
  85. pastes from
  86. .BR ~/.cache/mc/mcedit/mcedit.clip ,
  87. .B Shift\-Del
  88. cuts to
  89. .BR ~/.cache/mc/mcedit/mcedit.clip ,
  90. and
  91. .B Ctrl\-Del
  92. deletes highlighted text. Mouse highlighting also works on some
  93. terminals. To use the standard mouse support provided by your terminal,
  94. hold the Shift key. Please note that the mouse support in the terminal
  95. doesn't share the clipboard with
  96. .BR mcedit .
  97. .PP
  98. The completion key (usually
  99. .B "Meta\-Tab"
  100. or
  101. .BR "Escape Tab" )
  102. completes the word under the cursor using the words used in the file.
  103. .SH MACRO
  104. .PP
  105. To define a macro, press
  106. .B Ctrl\-R
  107. and then type out the keys you want to be executed. Press
  108. .B Ctrl\-R
  109. again when finished. The macro can be assigned to any key by pressing that key.
  110. The macro is executed when you press the assigned key.
  111. .PP
  112. The macro commands are stored in section
  113. .B [editor]
  114. it the file
  115. .BR ~/.local/share/mc/mc.macros .
  116. .PP
  117. External scripts (filters) can be assigned into the any hotkey by edit
  118. .B mc.macros
  119. like following:
  120. .PP
  121. .nf
  122. [editor]
  123. ctrl\-W=ExecuteScript:25;
  124. .fi
  125. .PP
  126. This means that ctrl\-W hotkey initiates the
  127. .I ExecuteScript(25)
  128. action, then editor handler translates this into execution of
  129. .B ~/.local/share/mc/mcedit/macros.d/macro.25.sh
  130. shell script.
  131. .PP
  132. External scripts are stored in
  133. .B ~/.local/share/mc/mcedit/macros.d/
  134. directory and must be named as
  135. .B macro.XXXX.sh
  136. where
  137. .B XXXX
  138. is the number from 0 to 9999.
  139. See
  140. .B Menu File Edit
  141. for more detail about format of the script.
  142. .PP
  143. Following macro definition and directives can be used:
  144. .TP
  145. .I #silent
  146. If this directive is set, then script starts without interactive subshell.
  147. .TP
  148. .I %c
  149. The cursor column position number.
  150. .TP
  151. .I %i
  152. The indent of blank space, equal the cursor column.
  153. .TP
  154. .I %y
  155. The syntax type of current file.
  156. .TP
  157. .I %b
  158. The block file name.
  159. .TP
  160. .I %f
  161. The current file name.
  162. .TP
  163. .I %n
  164. Only the current file name without extension.
  165. .TP
  166. .I %x
  167. The extension of current file name.
  168. .TP
  169. .I %d
  170. The current directory name.
  171. .TP
  172. .I %F
  173. The current file in the unselected panel.
  174. .TP
  175. .I %D
  176. The directory name of the unselected panel.
  177. .TP
  178. .I %t
  179. The currently tagged files.
  180. .TP
  181. .I %T
  182. The tagged files in the unselected panel.
  183. .TP
  184. .I %u
  185. and
  186. .I %U
  187. Similar to the
  188. .I %t
  189. and
  190. .I %T
  191. macros, but in addition the files are untagged. You can use this macro
  192. only once per menu file entry or extension file entry, because next time
  193. there will be no tagged files.
  194. .TP
  195. .I %s
  196. and
  197. .I %S
  198. The selected files: The tagged files if there are any. Otherwise the
  199. current file.
  200. .PP
  201. Feel free to edit this files, if you need.
  202. Here is a sample external script:
  203. .PP
  204. .nf
  205. l comment selection
  206. TMPFILE=`mktemp ${MC_TMPDIR:\-/tmp}/up.XXXXXX` || exit 1
  207. echo #if 0 > $TMPFILE
  208. cat %b >> $TMPFILE
  209. echo #endif >> $TMPFILE
  210. cat $TMPFILE > %b
  211. rm \-f $TMPFILE
  212. .fi
  213. .PP
  214. If some keys don't work, you can use
  215. .B Learn Keys
  216. in the
  217. .B Options
  218. menu.
  219. .SH CODE NAVIGATION
  220. .B mcedit
  221. can be used to navigation through code with tags files created by etags
  222. or ctags commands. If there is no file TAGS code navigation would not work.
  223. In example, in case of exuberant\-ctags for C language command will be:
  224. .PP
  225. ctags \-e \-\-language\-force=C \-R ./
  226. .PP
  227. .B Meta\-Enter
  228. show list box to select item under cursor (cusor should stand at end of
  229. word).
  230. .PP
  231. .B Meta\-Minus
  232. where minus is symbol "\-" go to previous function in navigation list (like a browser
  233. Back).
  234. .PP
  235. .B Meta\-Equal
  236. where equal is symbol "=" go to next function in navigation list (like a browser
  237. Forward).
  238. .PP
  239. .SH SYNTAX HIGHLIGHTING
  240. .B mcedit
  241. supports syntax highlighting. This means that keywords and contexts
  242. (like C comments, string constants, etc) are highlighted in different
  243. colors. The following section explains the format of the file
  244. .BR ~/.config/mc/mcedit/Syntax .
  245. If this file is missing, system\-wide
  246. .B %prefix%/share/mc/syntax/Syntax
  247. is used.
  248. The file
  249. .B ~/.config/mc/mcedit/Syntax
  250. is rescanned on opening of a any new editor file. The file contains
  251. rules for highlighting, each of which is given on a separate line, and
  252. define which keywords will be highlighted to what color.
  253. .PP
  254. The file is divided into sections, each beginning with a line with the
  255. .B file
  256. command. The sections are normally put into separate files using the
  257. .B include
  258. command.
  259. .PP
  260. The
  261. .B file
  262. command has three arguments. The first argument is a regular expression
  263. that is applied to the file name to determine if the following section
  264. applies to the file. The second argument is the description of the file
  265. type. It is used in
  266. .BR cooledit ;
  267. future versions of
  268. .B mcedit
  269. may use it as well. The third optional argument is a regular expression
  270. to match the first line of text of the file. The rules in the following
  271. section apply if either the file name or the first line of text matches.
  272. .PP
  273. A section ends with the start of another section. Each section is
  274. divided into contexts, and each context contains rules. A context is a
  275. scope within the text that a particular set of rules belongs to. For
  276. instance, the text within a C style comment (i.e. between
  277. .B /*
  278. and
  279. .BR */ )
  280. has its own color. This is a context, although it has no further rules
  281. inside it because there is probably nothing that we want highlighted
  282. within a C comment.
  283. .PP
  284. A trivial C programming section might look like this:
  285. .PP
  286. .nf
  287. file .\\*\\\\.c C\\sProgram\\sFile (#include|/\\\\\\*)
  288. wholechars abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ_
  289. # default colors
  290. define comment brown
  291. context default
  292. keyword whole if yellow
  293. keyword whole else yellow
  294. keyword whole for yellow
  295. keyword whole while yellow
  296. keyword whole do yellow
  297. keyword whole switch yellow
  298. keyword whole case yellow
  299. keyword whole static yellow
  300. keyword whole extern yellow
  301. keyword { brightcyan
  302. keyword } brightcyan
  303. keyword '*' green
  304. # C comments
  305. context /\\* \\*/ comment
  306. # C preprocessor directives
  307. context linestart # \\n red
  308. keyword \\\\\\n brightred
  309. # C string constants
  310. context " " green
  311. keyword %d brightgreen
  312. keyword %s brightgreen
  313. keyword %c brightgreen
  314. keyword \\\\" brightgreen
  315. .fi
  316. .PP
  317. Each context starts with a line of the form:
  318. .PP
  319. .B context
  320. .RB [ exclusive ]
  321. .RB [ whole | wholeright | wholeleft ]
  322. .RB [ linestart ]
  323. .I delim
  324. .RB [ linestart ]
  325. .I delim
  326. .RI [ foreground ]
  327. .RI [ background ]
  328. .RI [ attributes ]
  329. .PP
  330. The first context is an exception. It must start with the command
  331. .PP
  332. .B context default
  333. .RI [ foreground ]
  334. .RI [ background ]
  335. .RI [ attributes ]
  336. .PP
  337. otherwise
  338. .B mcedit
  339. will report an error. The
  340. .B linestart
  341. option specifies that
  342. .I delim
  343. must start at the beginning of a line. The
  344. .B whole
  345. option tells that
  346. .I delim
  347. must be a whole word. To specify that a word must begin on the word
  348. boundary only on the left side, you can use the
  349. .B wholeleft
  350. option, and similarly a word that must end on the word boundary is specified by
  351. .BR wholeright .
  352. .PP
  353. The set of characters that constitute a whole word can be changed at any
  354. point in the file with the
  355. .B wholechars
  356. command. The left and right set of characters can be set separately
  357. with
  358. .PP
  359. .B wholechars
  360. .RB [ left | right ]
  361. .I characters
  362. .PP
  363. The
  364. .B exclusive
  365. option causes the text between the delimiters to be highlighted, but not
  366. the delimiters themselves.
  367. .PP
  368. Each rule is a line of the form:
  369. .PP
  370. .B keyword
  371. .RB [ whole | wholeright | wholeleft ]
  372. .RB [ linestart ]
  373. .I string foreground
  374. .RI [ background ]
  375. .RI [ attributes ]
  376. .PP
  377. Context or keyword strings are interpreted, so that you can include tabs
  378. and spaces with the sequences \\t and \\s. Newlines and backslashes are
  379. specified with \\n and \\\\ respectively. Since whitespace is used as a
  380. separator, it may not be used as is. Also, \\* must be used to specify
  381. an asterisk. The * itself is a wildcard that matches any length of
  382. characters. For example,
  383. .PP
  384. .nf
  385. keyword '*' green
  386. .fi
  387. .PP
  388. colors all C single character constants green. You also could use
  389. .PP
  390. .nf
  391. keyword "*" green
  392. .fi
  393. .PP
  394. to color string constants, but the matched string would not be allowed
  395. to span across multiple newlines. The wildcard may be used within
  396. context delimiters as well, but you cannot have a wildcard as the last
  397. or first character.
  398. .PP
  399. Important to note is the line
  400. .PP
  401. .nf
  402. keyword \\\\\\n brightgreen
  403. .fi
  404. .PP
  405. This line defines a keyword containing the backslash and newline
  406. characters. Since the keywords are matched before the context
  407. delimiters, this keyword prevents the context from ending at the end of
  408. the lines that end in a backslash, thus allowing C preprocessor
  409. directive to continue across multiple lines.
  410. .PP
  411. The possible colors are: black, gray, red, brightred, green,
  412. brightgreen, brown, yellow, blue, brightblue, magenta, brightmagenta,
  413. cyan, brightcyan, lightgray and white. The special keyword "default" means
  414. the terminal's default. Another special keyword "base" means mc's main
  415. colors, it is useful as a placeholder if you want to specify attributes
  416. without modifying the background color. When 256 colors are available,
  417. they can be specified either as color16 to color255, or as rgb000 to rgb555
  418. and gray0 to gray23.
  419. .PP
  420. If the syntax file is shared with
  421. .BR cooledit ,
  422. it is possible to specify different colors for
  423. .B mcedit
  424. and
  425. .B cooledit
  426. by separating them with a slash, e.g.
  427. .PP
  428. .nf
  429. keyword #include red/Orange
  430. .fi
  431. .PP
  432. .B mcedit
  433. uses the color before the slash. See cooledit(1) for supported
  434. .B cooledit
  435. colors.
  436. .PP
  437. Attributes can be any of bold, underline, reverse and blink, appended by a
  438. plus sign if more than one are desired.
  439. .PP
  440. Comments may be put on a separate line starting with the hash sign (#).
  441. .PP
  442. If you are describing case insensitive language you need to use
  443. .B caseinsensitive
  444. directive. It should be specified at the beginning of syntax file.
  445. .PP
  446. Because of the simplicity of the implementation, there are a few
  447. intricacies that will not be dealt with correctly but these are a minor
  448. irritation. On the whole, a broad spectrum of quite complicated
  449. situations are handled with these simple rules. It is a good idea to
  450. take a look at the syntax file to see some of the nifty tricks you can
  451. do with a little imagination. If you cannot get by with the rules I
  452. have coded, and you think you have a rule that would be useful, please
  453. email me with your request. However, do not ask for regular expression
  454. support, because this is flatly impossible.
  455. .PP
  456. A useful hint is to work with as much as possible with the things you
  457. can do rather than try to do things that this implementation cannot deal
  458. with. Also remember that the aim of syntax highlighting is to make
  459. programming less prone to error, not to make code look pretty.
  460. .PP
  461. The syntax highlighting can be toggled using Ctrl\-s shortcut.
  462. .SH COLORS
  463. The default colors may be changed by appending to the
  464. .B MC_COLOR_TABLE
  465. environment variable. Foreground and background colors pairs may be
  466. specified for example with:
  467. .PP
  468. .nf
  469. MC_COLOR_TABLE="$MC_COLOR_TABLE:\\
  470. editnormal=lightgray,black:\\
  471. editbold=yellow,black:\\
  472. editmarked=black,cyan"
  473. .fi
  474. .SH OPTIONS
  475. Most options can now be set from the editors options dialog box. See
  476. the
  477. .B Options
  478. menu. The following options are defined in
  479. .B ~/.config/mc/ini
  480. and have obvious counterparts in the dialog box. You can modify them to
  481. change the editor behavior, by editing the file. Unless specified, a 1
  482. sets the option to on, and a 0 sets it to off, as is usual.
  483. .TP
  484. .I use_internal_edit
  485. This option is ignored when invoking
  486. .BR mcedit .
  487. .TP
  488. .I editor_tab_spacing
  489. Interpret the tab character as being of this length.
  490. Default is 8. You should avoid using
  491. other than 8 since most other editors and text viewers
  492. assume a tab spacing of 8. Use
  493. .B editor_fake_half_tabs
  494. to simulate a smaller tab spacing.
  495. .TP
  496. .I editor_fill_tabs_with_spaces
  497. Never insert a tab space. Rather insert spaces (ascii 20h) to fill to the
  498. desired tab size.
  499. .TP
  500. .I editor_return_does_auto_indent
  501. Pressing return will tab across to match the indentation
  502. of the first line above that has text on it.
  503. .TP
  504. .I editor_backspace_through_tabs
  505. Make a single backspace delete all the space to the left
  506. margin if there is no text between the cursor and the left
  507. margin.
  508. .TP
  509. .I editor_fake_half_tabs
  510. This will emulate a half tab for those who want to program
  511. with a tab spacing of 4, but do not want the tab size changed
  512. from 8 (so that the code will be formatted the same when displayed
  513. by other programs). When editing between text and the left
  514. margin, moving and tabbing will be as though a tab space were
  515. 4, while actually using spaces and normal tabs for an optimal fill.
  516. When editing anywhere else, a normal tab is inserted.
  517. .TP
  518. .I editor_option_save_mode
  519. Possible values 0, 1 and 2. The save mode (see the options menu also)
  520. allows you to change the method of saving a file. Quick save (0) saves
  521. the file by immediately, truncating the disk file to zero length (i.e.
  522. erasing it) and the writing the editor contents to the file. This
  523. method is fast, but dangerous, since a system error during a file save
  524. will leave the file only partially written, possibly rendering the data
  525. irretrievable. When saving, the safe save (1) option enables creation
  526. of a temporary file into which the file contents are first written. In
  527. the event of an problem, the original file is untouched. When the
  528. temporary file is successfully written, it is renamed to the name of the
  529. original file, thus replacing it. The safest method is create backups
  530. (2). Where a backup file is created before any changes are made. You
  531. can specify your own backup file extension in the dialog. Note that
  532. saving twice will replace your backup as well as your original file.
  533. .TP
  534. .I editor_word_wrap_line_length
  535. line length to wrap. 72 default.
  536. .TP
  537. .I editor_backup_extension
  538. symbol for add extension to name of backup files. Default "~".
  539. .TP
  540. .I editor_line_state
  541. show state line of editor now it show number of file line (in future it
  542. can show things like folding, breakpoints, etc.). M\-n toglle this option.
  543. .TP
  544. .I editor_visible_spaces
  545. Toggle show visible trailing spaces (TWS), if editor_visible_spaces=1 TWS
  546. showed as '.'
  547. .TP
  548. .I editor_visible_tabs
  549. Toggle show visible tabs, if editor_visible_tabs=1 tabs showed as '<\-\-\-\->'
  550. .TP
  551. .I editor_persistent_selections
  552. Do not remove block selection after moving the cursor.
  553. .TP
  554. .I editor_cursor_beyond_eol
  555. Allow moving cursor beyond the end of line.
  556. .TP
  557. .I editor_syntax_highlighting
  558. enable syntax highlighting.
  559. .TP
  560. .I editor_edit_confirm_save
  561. show confirm dialog on save.
  562. .TP
  563. .I editor_option_typewriter_wrap
  564. to be described
  565. .TP
  566. .I editor_option_auto_para_formatting
  567. to be described
  568. .TP
  569. .I editor_option_save_position
  570. save file position on exit.
  571. .TP
  572. .I source_codepage
  573. symbol representation of codepage name for file (i.e. CP1251, ~ \- default).
  574. .TP
  575. .I editor_group_undo
  576. do UNDO for several of the same type of action (inserting/overwriting,
  577. deleting, navigating, typing)
  578. .TP
  579. .I editor_wordcompletion_collect_entire_file
  580. Search autocomplete candidates in entire of file or just from
  581. begin of file to cursor position (0)
  582. .SH MISCELLANEOUS
  583. You can use scanf search and replace to search and replace a C format
  584. string. First take a look at the
  585. .B sscanf
  586. and
  587. .B sprintf
  588. man pages to see what a format string is and how it works. Here's an
  589. example: suppose that you want to replace all occurrences of an open
  590. bracket, three comma separated numbers, and a close bracket, with the
  591. word
  592. .IR apples ,
  593. the third number, the word
  594. .I oranges
  595. and then the second number. You would fill in the Replace dialog box as
  596. follows:
  597. .PP
  598. .nf
  599. .B Enter search string
  600. (%d,%d,%d)
  601. .B Enter replace string
  602. apples %d oranges %d
  603. .B Enter replacement argument order
  604. 3,2
  605. .fi
  606. .PP
  607. The last line specifies that the third and then the second number are to
  608. be used in place of the first and second.
  609. .PP
  610. It is advisable to use this feature with Prompt On Replace on, because a
  611. match is thought to be found whenever the number of arguments found
  612. matches the number given, which is not always a real match. Scanf also
  613. treats whitespace as being elastic. Note that the scanf format %[ is
  614. very useful for scanning strings, and whitespace.
  615. .PP
  616. The editor also displays non\-us characters (160+). When editing
  617. binary files, you should set
  618. .B display bits
  619. to 7 bits in the Midnight Commander options menu to keep the spacing
  620. clean.
  621. .SH FILES
  622. .I %prefix%/share/mc/mc.hlp
  623. .IP
  624. The help file for the program.
  625. .PP
  626. .I %prefix%/share/mc/mc.ini
  627. .IP
  628. The default system\-wide setup for GNU Midnight Commander, used only if
  629. the user's own ~/.config/mc/ini file is missing.
  630. .PP
  631. .I %prefix%/share/mc/mc.lib
  632. .IP
  633. Global settings for the Midnight Commander. Settings in this file
  634. affect all users, whether they have ~/.config/mc/ini or not.
  635. .PP
  636. .I %prefix%/share/mc/syntax/*
  637. .IP
  638. The default system\-wide syntax files for mcedit, used only if
  639. the corresponding user's own ~/.local/share/mc/mcedit/ file is missing.
  640. .PP
  641. .I ~/.config/mc/ini
  642. .IP
  643. User's own setup. If this file is present then the setup is loaded
  644. from here instead of the system\-wide setup file.
  645. .PP
  646. .I ~/.local/share/mc/mcedit/
  647. .IP
  648. User's own directory where block commands are processed and saved and
  649. user's own syntax files are located.
  650. .SH LICENSE
  651. This program is distributed under the terms of the GNU General Public
  652. License as published by the Free Software Foundation. See the built\-in
  653. help of the Midnight Commander for details on the License and the lack
  654. of warranty.
  655. .SH AVAILABILITY
  656. The latest version of this program can be found at
  657. http://midnight\-commander.org/.
  658. .SH SEE ALSO
  659. cooledit(1), mc(1), gpm(1), terminfo(1), scanf(3).
  660. .SH AUTHORS
  661. Paul Sheer (psheer@obsidian.co.za) is the original author of
  662. the Midnight Commander's internal editor.
  663. .SH BUGS
  664. Bugs should be reported to mc\-devel@gnome.org