⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 faq

📁 ReactOS是一些高手根据Windows XP的内核编写出的类XP。内核实现机理和API函数调用几乎相同。甚至可以兼容XP的程序。喜欢研究系统内核的人可以看一看。
💻
📖 第 1 页 / 共 3 页
字号:
   tcsh:
   
     setenv TERM vt100
     
   or if you use sh, bash, ksh or zsh:
   
     export TERM=vt100
     
   If this doesn't help you can recompile MC to use termcap instead of
   terminfo:
   
     ./configure --with-termcap
     make
     
  4.2 [UPDATED] Why don't line drawing characters work?
  
   Since version 4.0.13 there's the commandline option -a to force use of
   +, |, - for line drawing (only available when compiled with SLang).
   Use this -a option if any of the suggestions below doesn't help.
   
   In general, there are three subcases:
     * Lines are shown as ASCII characters like this

      +---------+
      |         |
      +---------+
   This also happens when you use the -a option. Other than that possible
       reason is 1, 2 or 3 (see below).
     * Lines are shown as lower case characters like this

      lqqqqqqqqqk
      x         x
      mqqqqqqqqqj
   Possible reason is 2 or 3 (see below).
     * Lines are shown as blanks or missing characters. Possible reason
       is 3 or 4 (see below).
       
   The reason for the problem is one of following:
    1. Your curses library might not support line drawing characters.
       Slang, Ncurses and System V curses do support them, BSD curses
       doesn't. MC uses Slang by default so this is not usually a
       problem.
    2. Your terminal might not support line drawing characters. Vt100
       compatible terminals, rxvt, xterm and color_xterm do support them.
    3. Your terminfo or termcap database might have missing or incorrect
       definations for line drawing characters. Set the acsc variable in
       the terminfo database like this:
       acsc=a\376k\277l\332m\300j\331n\305w\302v\301u\264t\303q\304x\263h
       \2600\333
       Don't forget issue 'tic' command. This supposes you are using pc
       character set. The octal values might be different for other
       character sets. If you are using termcap instead of terminfo, you
       should modify above solution appropriately.
    4. Your terminal font might not support line drawing characters. Try
       changing the font.
       
   Here is Miguel's answer to Torben on this subject.
   
   Torben:
   
     When I load consolefonts/iso01.f16, I get perfectly right national
     characters, but the line drawing characters in mc get wrong. Is it
     a mc problem, or is it a problem with the font? (I guess it is).
     
     Is there a trick?
     
   Miguel:
   
     First of all, we should determine whether the font has line drawing
     characters or not.
     
     If it has line drawing characters, then a new terminfo entry should
     be written for this specific case. Let's call this linux-iso01. The
     acsc variable should be modified to reflect which characters are
     used to do the line drawing.
     
     If it does not have line drawing characters, then we should get rid
     of the switch to acsc sequences and make the acsc sequence be just
     a mapping to the ugly +, -, |, - characters.
     
     You can get your terminfo definition by running the infocmp
     program, making the proper changes and running the tic program to
     compile your new terminfo database.
     
  4.3 Can one use latin-1 characters without losing the lines?
  
   Yes, you need a correct font and a correct termcap/terminfo database.
   
   For font, if you use xterm try "xterm -fn fixed".
   
   For termcap/terminfo database, change the acsc capability in the
   database.
   
  4.4 I have problems with entering/viewing national characters!
  
   Upgrade to version 4.0.12 or newer.
   
   From the Options - Display Bits dialog select Full 8 bits or ISO
   8859-1. In addition, select 8 bit input from the same dialog.
   
  4.5 How can I get colors?
  
   Invoke mc like this (without quotes): "mc -c".
   
   If you get colors, be happy.
   
   If your terminal stays black and white, your terminal doesn't support
   color. You might want to upgrade to a terminal which compatible with
   the ANSI color sequences.
   
   If your terminal goes compelety black, see the next question.
   
   More detailed answer:
   
   First, check that your terminal supports color. Color_xterm, rxvt and
   Linux console do support, most other terminals don't. You can test
   color support with following simple C program:

    #include <stdio.h>

    int main (void){
        printf ("\033[32m Hello world! \033[m\n");
        return 0;
    }

   Compile and run it. If you see "Hello world!" text in green your
   terminal supports color, otherwise not (however, for color_xterm see
   also the next question).
   
   Second, check that you are using Ncurses or the Slang library (type
   "mc -V" to find out), in addition some System V curses implementations
   do support color, most don't.
   
   With Slang library you can force color support by setting the
   environment variable COLORTERM to any value.
   
   Third, if you use ncurses library, check that your terminfo database
   supports color. If not you should install one of the enhanced terminfo
   databases included in the Midnight Commander source distribution.
   
   Fourth, you might want to set the TERM environment variable so that
   you use the correct terminfo database or termcap entry.
   
   If you use color_xterm (or rxvt) the correct value might be
   xterm-color, xtermc or simply xterm.
   
   If you use Linux console the correct value for TERM is linux or
   console.
   
  4.6 My color_xterm goes completely (or partially) black!
  
   Some color_xterm terminals define all colors as black instead of the
   standard ANSI colors. This makes them go completely black when you try
   to use Midnight Commander with colors.
   
   You will have to override the defaults. Create a file "color.defaults"
   which has the following contents:

    color_xterm*color0:           Black
    color_xterm*color1:           Red
    color_xterm*color2:           Green
    color_xterm*color3:           Yellow
    color_xterm*color4:           Blue
    color_xterm*color5:           Magenta
    color_xterm*color6:           Cyan
    color_xterm*color7:           White
    color_xterm*background:       White
    color_xterm*foreground:       Black

   (replace color_xterm with the name of your color_xterm, color_xterm
   mentions its name in its title bar)
   
   Now type:

    xrdb -merge color.defaults

   Alternatively you can add the suggested contents of the color.defaults
   file to your .Xdefaults or .Xresources file (or what ever the name of
   your X configuration file is). Or you can replace your non-ANSI
   color_xterm with an ANSI color_xterm.
   
  4.7 Where can I get color_xterm?
  
   Try ftp.x.org: /contrib/utilities/colour_xterm.tar.gz.
   
   Alternatively, rxvt is a better choice, see
   http://mc.blackdown.org/cgi-mc/download/rxvt/.html
   
  4.8 I got colors working with MC but the other programs don't work at all
  anymore!
  
   Midnight Commander uses terminfo database (if available) but many
   other programs use termcap database. If you set the TERM environment
   variable to a value which has no corresponding entry in termcap
   database those programs stop working. You should add the new value of
   TERM to the termcap database.
   
   Example: If you have set TERM to xterm-color locate from /etc/termcap
   the line which starts:

    xterm|vs100|xterm terminal emulator

   Change it to start:

    xterm|xterm-color|vs100|xterm terminal emulator

  4.9 Why are there both terminfo and termcap? Wouldn't one database be enough?
  
   You might want to read the Unix-haters handbook at
   http://www.digital.de/people/jmh/Unix_Haters/unix-haters.html. It
   lists many more reasons why Unix sucks.
   
   You can configure which terminal database you want to use with the
   "--with-termcap" and "--with-terminfo" flags of configure. If you
   don't specify them, the configure script will try to use terminfo if
   available otherwise it will use termcap.
   
5 Graphical user interface

  5.1 Xview and Tk editions?
  
   Get the newest development version, give the "--with-xview" or
   "--with-tk" option to the configure and otherwise compile as usual.
   See Download.
   
   Xview and Tk editions are work in progress, they are not as robust as
   the text mode edition.
   
6 Command line problems

  6.1 How do I stay in the last directory when I exit Midnight Commander?
  
   See the description of the -P option in the Options section of the
   manual.
   
  6.2 How can I access command line history?
  
   You can browse previous commands with M-p and M-n. Alternatively, you
   can summon the command history listbox by pressing F9 c h.
   
  6.3 How can I complete commands, file names, variable names and so on?
  
   Just press M-Tab. Press M-Tab again to get a listbox if there are
   multiple possible completions.
   
  6.4 [NEW] I am using ksh. Can I use functions defined in the .kshrc within
  MC?
  
   Sorry, MC only supports bash, tcsh and zsh functions. Ksh functions
   are not supported because ksh lacks the necessary hooks needed for
   subshell integration.
   
   Switch to bash or zsh. They are both quite compatible with ksh. Your
   ksh functions should work as such or after minimal changes.
   
  6.5 [NEW] Is there any way to include additional options or hot keys to MC?
  
   Yes, F2 invokes an user menu which fully configurable. You can add any
   shell commands to the user menu. See
   http://mc.blackdown.org/mc/manual-d.html#8 for more info.
   
   Another way to add functionality is the external panelize feature. See
   http://mc.blackdown.org/mc/manual-d.html#4 for more info.
   
   And finally, you can code any feature you want yourself. MC source
   code is free which means you can change it anyway you want. There are
   some limitations to make sure MC stays free. See GNU General Public
   License for details.
   
7 Virtual file systems

   Note! Virtual file systems are supported by Unix ports only. The
   Windows 95/NT and OS/2 ports do NOT support virtual file systems. This
   means you haven't got ftp, zip or tar support on Windows 95/NT and
   OS/2.
   
  7.1 How can I see the contents of a tar archive?
  
   If you use keyboard just move the selection bar on the tar file and
   press enter.
   
   If you use mouse just doubleclick on the tar file.
   
   If these procedures don't work, your .mc.ext file is faulty. Replace
   it with one from the MC source distribution.
   
   You can also enter a tar archive by typing "cd tar:filename.tar.gz"
   where filename.tar.gz is the name of the archive.
   
   The recognized suffixes for tar archives are .tar, .tar.gz and .tgz.
   If your tar archive uses different suffix you have to rename it.
   
  7.2 How do I get out of a tar archive?
  
   Just press enter on the toplevel ".." file or chdir to a non-tar
   directory. Just typing "cd" with no parameters is enough (it will take
   you to your home directory).
   
  7.3 How do I do anonymous ftp with MC?
  
   Just type "cd ftp://hostname" where hostname is the name of the host
   you want to connect. Alternatively, select FTP link from the Left or
   Right menu and type the name of the host you want to connect.
   
  7.4 How do I do non-anonymous ftp with MC?
  
   Non-anonymous ftp works just like the anonymous ftp but you give the
   login name with the host name. For example, type "cd
   ftp://username@hostname".
   
  7.5 How do I close an ftp connection?
  

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -