* configure.in: Remove support for curses libraries other than
ncurses. * acinclude.m4: Likewise. * FAQ: Remove everything about UNIX curses. * INSTALL: Likewise.
Этот коммит содержится в:
родитель
a85dc7c5f9
Коммит
8176f16111
@ -1,5 +1,11 @@
|
||||
2001-08-24 Pavel Roskin <proski@gnu.org>
|
||||
|
||||
* configure.in: Remove support for curses libraries other than
|
||||
ncurses.
|
||||
* acinclude.m4: Likewise.
|
||||
* FAQ: Remove everything about UNIX curses.
|
||||
* INSTALL: Likewise.
|
||||
|
||||
* configure.in: Enable large file support by default.
|
||||
* NEWS: Mention it.
|
||||
* INSTALL: Document it. Minor fixes.
|
||||
|
346
FAQ
346
FAQ
@ -1,16 +1,16 @@
|
||||
Midnight Commander
|
||||
GNU Midnight Commander
|
||||
Questions and Answers
|
||||
|
||||
The newest version of this document is available at
|
||||
http://cvs.gnome.org/lxr/source/mc/FAQ?raw=1
|
||||
|
||||
|
||||
* 1 Getting started
|
||||
+ 1.1 What is Midnight Commander?
|
||||
+ 1.2 Does it run on my machine?
|
||||
+ 1.3 Does it work with my terminal?
|
||||
+ 1.4 What else do I need to run MC?
|
||||
+ 1.5 Is Midnight Commander Public Domain? Copyrighted?
|
||||
+ 1.6 Where can I get Midnight Commander?
|
||||
+ 1.5 Is GNU Midnight Commander Public Domain? Copyrighted?
|
||||
+ 1.6 Where can I get GNU Midnight Commander?
|
||||
+ 1.7 I don't have FTP access. Where can I get MC?
|
||||
* 2 Keyboard
|
||||
+ 2.1 What does documentation mean with the C-?, M-? and F?
|
||||
@ -82,7 +82,7 @@ Questions and Answers
|
||||
+ 11.1 Authorship
|
||||
+ 11.2 Feedback is invited
|
||||
+ 11.3 Disclaimer and copyright
|
||||
|
||||
|
||||
1 Getting started
|
||||
|
||||
1.1 What is Midnight Commander?
|
||||
@ -93,16 +93,16 @@ Questions and Answers
|
||||
system while making many frequent file operations more efficient and
|
||||
preserving the full power of the command prompt. You will wonder how
|
||||
you could ever live without it.
|
||||
|
||||
|
||||
For more thorough description take a look at the announcement of
|
||||
Midnight Commander 4.0.
|
||||
|
||||
|
||||
1.2 Does it run on my machine?
|
||||
|
||||
Yes, Midnight Commander can run on almost any machine, including Unix
|
||||
clones, Windows 95/NT and OS/2. Midnight Commander does not run on
|
||||
Macintosh.
|
||||
|
||||
|
||||
Midnight Commander uses GNU Autoconf which can automatically
|
||||
configure Midnight Commander for use on almost any (if not every)
|
||||
Unix clone. Following configurations have been tested:
|
||||
@ -126,19 +126,19 @@ Questions and Answers
|
||||
* i386-*-windows-nt-3.51, 4.0
|
||||
* i386-*-windows95
|
||||
* i386-*-os2
|
||||
|
||||
|
||||
Windows 95/NT port can be compiled with Microsoft Visual C++, Borland
|
||||
C++, RSX and Mingw32.
|
||||
|
||||
|
||||
1.3 Does it work with my terminal?
|
||||
|
||||
Yes, it does.
|
||||
|
||||
|
||||
Because Midnight Commander is a full screen program it doesn't run on
|
||||
dummy terminals but anything more advanced will do (like vt100). If
|
||||
your terminal works with vi, emacs, elm or pine it will work with
|
||||
Midnight Commander.
|
||||
|
||||
|
||||
1.4 What else do I need to run MC?
|
||||
|
||||
You need an Unix compatible operating system. Support for Windows 95/NT
|
||||
@ -147,59 +147,56 @@ Questions and Answers
|
||||
To compile any edition you need to have GLib installed. It's available
|
||||
at ftp://ftp.gtk.org/pub/gtk/. Only GLib versions 1.2.x will be
|
||||
currently detected.
|
||||
|
||||
|
||||
If you want to use mouse on the Linux console you need the gpm daemon
|
||||
from ftp://ftp.systemy.it/pub/develop/. You need nothing extra to use
|
||||
mouse on xterm.
|
||||
|
||||
|
||||
If you do not want to use the S-Lang library you could try using
|
||||
ncurses (we recommend only version 4.1 and above).
|
||||
|
||||
You can get it along with other curses libraries, too, but results may
|
||||
not be pretty or even usable.
|
||||
|
||||
1.5 Is Midnight Commander Public Domain? Copyrighted?
|
||||
1.5 Is GNU Midnight Commander Public Domain? Copyrighted?
|
||||
|
||||
Midnight Commander is under GNU Public License which basically means
|
||||
that you may freely copy, change and distribute it, but that you may
|
||||
not impose any restrictions on further distribution, and that you must
|
||||
make the source code available. This is not the same as Public Domain.
|
||||
make the source code available. This is not the same as Public Domain.
|
||||
For details, the GNU license is included in GNU Midnight Commander
|
||||
source distribution (the COPYING file).
|
||||
|
||||
Midnight Commander is nowadays officially a part of GNU project. All
|
||||
the authors of GNU Midnight Commander have given all their rights on
|
||||
the program to the Free Software Foundation.
|
||||
|
||||
1.6 Where can I get Midnight Commander?
|
||||
|
||||
Midnight Commander is now officially a part of the GNU project.
|
||||
All the authors of GNU Midnight Commander have given all their rights
|
||||
on the program to the Free Software Foundation.
|
||||
|
||||
1.6 Where can I get GNU Midnight Commander?
|
||||
|
||||
The main site is ftp://ftp.gnome.org/pub/GNOME/stable/sources/mc/
|
||||
|
||||
|
||||
1.7 I don't have FTP access. Where can I get MC?
|
||||
|
||||
Most GNU/Linux distributions include GNU Midnight Commander. For
|
||||
example, Debian, Mandrake, Red Hat, Slackware and SuSE.
|
||||
|
||||
|
||||
2 Keyboard
|
||||
|
||||
2.1 What does documentation mean with the C-?, M-? and F? keys?
|
||||
|
||||
Midnight Commander documentation uses emacs style names for keyboard
|
||||
keys.
|
||||
|
||||
GNU Midnight Commander documentation uses emacs style names for
|
||||
keyboard keys.
|
||||
|
||||
C stands for the Ctrl key. For example, C-f means that you should hold
|
||||
down the Ctrl key and press the f key.
|
||||
|
||||
|
||||
M stands for the Meta key. Your terminal might call it Alt or Compose
|
||||
instead of Meta. For example, M-f means that you should hold down the
|
||||
Meta/Alt/Compose key and press the f key. If your terminal doesn't
|
||||
have Meta, Alt or Compose or they don't work you can use Esc. For M-f
|
||||
press the Esc key and then press the f key.
|
||||
|
||||
|
||||
F? stands for a function key. If your terminal doesn't have function
|
||||
keys or they don't work you can use Esc. For example, for F3 press the
|
||||
Esc key and then press the 3 key.
|
||||
|
||||
|
||||
2.2 Why don't function keys (or some other key) work?
|
||||
|
||||
Your terminfo or termcap database has missing or incorrect definitions
|
||||
@ -208,39 +205,39 @@ Questions and Answers
|
||||
database" you should install one of the enhanced terminfo databases
|
||||
included in GNU Midnight Commander source distribution. For example,
|
||||
if you are using xterm type "tic xterm.ti".
|
||||
|
||||
|
||||
If the result is "using the S-Lang library with termcap database" you
|
||||
should fix your /etc/termcap database.
|
||||
|
||||
|
||||
Better termcap and terminfo databases are available here:
|
||||
|
||||
|
||||
http://www.tuxedo.org/~esr/terminfo/
|
||||
ftp://dickey.his.com/ncurses/
|
||||
|
||||
|
||||
You can select whether Midnight Commander will use terminfo or termcap
|
||||
database by giving --with-terminfo or --with-termcap option to the
|
||||
configure. Default is terminfo if found, otherwise termcap.
|
||||
|
||||
|
||||
If you don't have permissions to edit terminal databases you can use
|
||||
Learn keys feature of Midnight Commander instead. Press Esc 9 o k and
|
||||
follow instructions.
|
||||
|
||||
|
||||
If all else fails you can emulate function keys by first pressing the
|
||||
ESC key and then one of the number keys. For example, if you want to
|
||||
produce F9, press ESC, then 9. If you don't have a ESC key on your
|
||||
keyboard you can try alt-9 or meta-9.
|
||||
|
||||
|
||||
2.3 How do I use function keys F11 to F20?
|
||||
|
||||
These can mapped to function keys F1 to F10 with Shift held. e.g.
|
||||
function key F13 can be activated by pressing Shift-F3. You can define
|
||||
the keys this way in the Options menu. The convention for PC keyboards
|
||||
is that F11-20 always means Shift with F1-10
|
||||
|
||||
|
||||
Note! Windows 95/NT and OS/2 ports use F11 and F12 keys to change the
|
||||
current disk drive. In this case F11 and F12 mean the real F11 and F12
|
||||
keys, not shift-F1 and shift-F2.
|
||||
|
||||
|
||||
2.4 Why does the ESC key behave funny?
|
||||
|
||||
Midnight Commander uses the ESC key as a prefix for simulating the
|
||||
@ -255,45 +252,45 @@ Questions and Answers
|
||||
only if another key is pressed within 0.5 seconds. After 0.5 seconds
|
||||
the ESC key cancels. There is no way to make ESC cancel immediately
|
||||
(if we want to be able to use arrows keys and function keys).
|
||||
|
||||
|
||||
2.5 How can I add the plus sign (+) on the command line?
|
||||
|
||||
Press C-q first, then press the + sign.
|
||||
|
||||
|
||||
The plus key is the hotkey for the select files command. If you want
|
||||
to add a literal plus on to the command line you must quote it by
|
||||
pressing C-q first.
|
||||
|
||||
|
||||
Another common key which needs the C-q prefix is backslash "\".
|
||||
|
||||
|
||||
2.6 C-o doesn't work!
|
||||
|
||||
Maybe C-o is a stty control character on your terminal. See man stty
|
||||
for details on how to list and change stty control characters.
|
||||
|
||||
|
||||
2.7 What 'keys' are the "a1" and "c1" keys mentioned in the manual?
|
||||
|
||||
The "a1" key is the key which has the "a1" caption on it.
|
||||
|
||||
|
||||
The "c1" key is the key which has the "c1" caption on it.
|
||||
|
||||
|
||||
If you have to ask what these two keys are your keyboard hasn't
|
||||
probably got them. Actually, I have never seen a keyboard which has
|
||||
got them.
|
||||
|
||||
|
||||
3 Mouse
|
||||
|
||||
3.1 How do I enable mouse support?
|
||||
|
||||
Invoke mc like this (without quotes): "mc -x". If this doesn't work
|
||||
upgrade to a terminal which compatible with the Xterm mouse sequences.
|
||||
|
||||
|
||||
Alternatively, on Linux console you can use gpm.
|
||||
|
||||
|
||||
3.2 How do I cut and paste text with mouse?
|
||||
|
||||
Hold down shift key while using mouse to cut and paste.
|
||||
|
||||
|
||||
3.3 How do I get the extension dependent pop-up menu to pop up?
|
||||
|
||||
It was developed for the GNOME edition. The text-mode edition doesn't
|
||||
@ -306,28 +303,28 @@ Questions and Answers
|
||||
|
||||
This means that your terminfo databases do not contain the correct
|
||||
definitions for your terminal.
|
||||
|
||||
|
||||
You could try using a different terminal setting. If you use csh or
|
||||
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 Why don't line drawing characters work?
|
||||
|
||||
Since version 4.0.13 there's the command line option -a to force use of
|
||||
+, |, - for line drawing (only available when compiled with S-Lang).
|
||||
Use this -a option if any of the suggestions below doesn't help.
|
||||
|
||||
|
||||
In general, there are three cases:
|
||||
* Lines are shown as ASCII characters like this
|
||||
|
||||
@ -336,26 +333,24 @@ Questions and Answers
|
||||
+---------+
|
||||
|
||||
This also happens when you use the -a option. Other than that
|
||||
possible reason is 1, 2 or 3 (see below).
|
||||
possible reason is 1 or 2 (see below).
|
||||
|
||||
* Lines are shown as lower case characters like this
|
||||
|
||||
lqqqqqqqqqk
|
||||
x x
|
||||
mqqqqqqqqqj
|
||||
|
||||
Possible reason is 2 or 3 (see below).
|
||||
Possible reason is 1 or 2 (see below).
|
||||
|
||||
* Lines are shown as blanks or missing characters. Possible reason
|
||||
is 3 or 4 (see below).
|
||||
|
||||
is 2 or 3 (see below).
|
||||
|
||||
The reason for the problem is one of following:
|
||||
|
||||
1. Your curses library might not support line drawing characters.
|
||||
S-Lang, ncurses and SystemV curses do support them, BSD curses
|
||||
doesn't. MC uses S-Lang by default so this is not usually a
|
||||
problem.
|
||||
2. Your terminal might not support line drawing characters. Vt100
|
||||
1. 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
|
||||
2. Your terminfo or termcap database might have missing or incorrect
|
||||
definitions 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
|
||||
@ -364,70 +359,70 @@ Questions and Answers
|
||||
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
|
||||
3. 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 completely 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:
|
||||
|
||||
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>
|
||||
|
||||
@ -439,33 +434,32 @@ Questions and Answers
|
||||
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 S-Lang library (type
|
||||
"mc -V" to find out), in addition some SystemV curses implementations
|
||||
do support color, most don't.
|
||||
|
||||
|
||||
Check whether you are using Ncurses or the S-Lang library (type
|
||||
"mc -V" to find out).
|
||||
|
||||
With S-Lang 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
|
||||
|
||||
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 GNU 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.
|
||||
|
||||
|
||||
You might want to set the TERM environment variable so that you are
|
||||
using 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:
|
||||
|
||||
@ -482,7 +476,7 @@ Questions and Answers
|
||||
|
||||
(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
|
||||
@ -491,7 +485,7 @@ Questions and Answers
|
||||
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 xterm or rxvt?
|
||||
|
||||
xterm is included with the X Window System, so you probably already
|
||||
@ -510,7 +504,7 @@ anymore!
|
||||
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:
|
||||
|
||||
@ -526,132 +520,132 @@ enough?
|
||||
You might want to read the Unix-Haters Handbook at
|
||||
http://catalog.com/hopkins/unix-haters/handbook.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, Tk and Gnome editions?
|
||||
|
||||
Xview and Tk and GNOME editions have been removed from the sources.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
Since version 4.1.15 all the input widgets have permanent history. You
|
||||
can summon the history listbox by pressing M-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 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 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 the mc(1) man page for more
|
||||
info.
|
||||
|
||||
|
||||
Another way to add functionality is the external panelize feature.
|
||||
See the mc(1) man page 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.
|
||||
|
||||
|
||||
This chapter describes the behavior of the 4.1.x versions of the
|
||||
Midnight Commander. The behavior of the 4.5.x versions is somewhat
|
||||
different. More on that when the 4.5.x versions get more stable.
|
||||
|
||||
|
||||
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 double-click 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?
|
||||
|
||||
Just chdir to a non-ftp directory. Just typing "cd" with no parameters
|
||||
is enough (it will take you to your home directory).
|
||||
|
||||
|
||||
Internally Midnight Commander closes ftp connection only after a
|
||||
timeout. This isn't visible to the end user.
|
||||
|
||||
|
||||
7.6 Why aren't the contents of ftp panel updated?
|
||||
|
||||
Update is skipped because there would be a serious performance
|
||||
penalty. Constantly updating directory panels through a ftp connection
|
||||
would take too much time.
|
||||
|
||||
|
||||
You can use C-r to force an update.
|
||||
|
||||
|
||||
7.7 What kind of proxy server works with Midnight Commander?
|
||||
|
||||
There are two kinds of ftp proxies: proxies for ftp clients and
|
||||
proxies for web browsers.
|
||||
|
||||
|
||||
Midnight Commander only supports ftp proxies which are meant for ftp
|
||||
clients. Common WWW proxies (like Squid) are not supported. A rule of
|
||||
thumb is that if a ftp proxy works with a web browser, it won't work
|
||||
with Midnight Commander.
|
||||
|
||||
|
||||
8 Other common problems
|
||||
|
||||
8.1 How do I get the internal editor to work?
|
||||
@ -659,16 +653,16 @@ enough?
|
||||
The F4 key used to default to an external editor because that was what
|
||||
most people were used to. The newer versions use internal editor by
|
||||
default.
|
||||
|
||||
|
||||
To use the internal editor with an old version, select Configuration
|
||||
from the Options menu and check the 'use internal edit' option.
|
||||
|
||||
|
||||
Alternatively add the line
|
||||
use_internal_edit=1
|
||||
|
||||
under the [Midnight-Commander] section in your .mc.ini file (which is
|
||||
in your home directory).
|
||||
|
||||
|
||||
To make the editor work all the time, go to the default/* section in
|
||||
the file lib/mc/mc.ext file and remove the line
|
||||
|
||||
@ -676,28 +670,28 @@ enough?
|
||||
|
||||
The internal editor will now be invoked for anything not specified
|
||||
elsewhere in the mc.ext file.
|
||||
|
||||
|
||||
Make sure that you edit the correct mc.ext file. The Midnight
|
||||
Commander first checks the existence of $HOME/.mc.ext. If this file is
|
||||
missing MC will use $prefix/lib/mc/mc.ext instead ($prefix can be
|
||||
changed with configure before compilation and it defaults to
|
||||
/usr/local).
|
||||
|
||||
|
||||
When you run `F9/Command/Extension file edit' for the very first time
|
||||
Midnight Commander copies the system-wide mc.ext from $prefix/lib/mc
|
||||
into your home directory because you need write access in order to
|
||||
change it.
|
||||
|
||||
|
||||
And please don't forget that "make install" overwrites
|
||||
$prefix/lib/mc/mc.ext.
|
||||
|
||||
|
||||
8.2 Is there any way to 'bookmark' favorite ftp-fs links?
|
||||
|
||||
Use the directory hotlist. Just press control-backslash. If your
|
||||
national keyboard layout doesn't have backslash key, just press the
|
||||
control key with the key which is the backslash key in the English
|
||||
keyboard layout.
|
||||
|
||||
|
||||
8.3 Why I keep getting: "There is no disk in the drive. Please insert a disk
|
||||
into drive D:"?
|
||||
|
||||
@ -705,11 +699,11 @@ into drive D:"?
|
||||
configuration files from the D:\MC directory and if the D: drive is a
|
||||
removable drive (like a CD ROM drive) and there is no disk in drive
|
||||
you get this message every time you try to do anything.
|
||||
|
||||
|
||||
Since version 4.0.6 you can specify the actual location of the
|
||||
Midnight Commander configuration files with the MCHOME environment
|
||||
variable.
|
||||
|
||||
|
||||
8.4 When I start Midnight Commander, nothing happens!
|
||||
|
||||
First, invoke MC without subshell support: "mc -u". If this helps
|
||||
@ -717,16 +711,16 @@ into drive D:"?
|
||||
although tcsh and zsh are also supported. You might want to upgrade
|
||||
your shell to a newer version. If you use something else than bash,
|
||||
tcsh or zsh, subshell support is disabled automatically.
|
||||
|
||||
|
||||
If disabling subshell doesn't help, try to reconfigure MC with
|
||||
"--with-included-slang" and "--with-termcap" options and recompile.
|
||||
If this helps, there is something wrong with your terminfo database
|
||||
or shared S-Lang library. For better terminfo databases see chapter
|
||||
4. For a better S-Lang library, upgrade to a newer version or keep
|
||||
using the "--with-included-slang" option.
|
||||
|
||||
|
||||
This problem can also be caused by gpm as noted by Luis Espinoza:
|
||||
|
||||
|
||||
In regards to why Midnight Commander does nothing when invoked. I
|
||||
recently had the same problem. At the same time gpm was not loading
|
||||
properly with my patched kernel (now 2.0.33 from 2.0.30).
|
||||
@ -752,11 +746,11 @@ into drive D:"?
|
||||
* Paul Sheer (joined Nov 1 1996)
|
||||
* Norbert Warmuth
|
||||
* Alex I. Tkachenko
|
||||
|
||||
|
||||
Alessandro Rubini has been specially helpful with debugging and
|
||||
enhancing of the mouse support. John E. Davis has made his S-Lang
|
||||
library available to us and answered many questions about it.
|
||||
|
||||
|
||||
Many people have contributed bug reports, feature suggestions and
|
||||
small code bits (alphabetical order):
|
||||
* Thomasz Cholewo
|
||||
@ -777,26 +771,26 @@ into drive D:"?
|
||||
* Vadim Sinolits
|
||||
* Jon Stevens
|
||||
* Adam Tla/lka
|
||||
|
||||
|
||||
9.2 Do I dare to use a development version?
|
||||
|
||||
I am afraid you have to answer to this question yourself. Development
|
||||
versions seldom cause data loss but they have usually got many bugs.
|
||||
It's up to you to judge whether new features outweigh the bugs.
|
||||
|
||||
|
||||
9.3 How can I report a bug/request for a feature?
|
||||
|
||||
You might first want to get the newest development version to see if
|
||||
the bug is fixed or the feature is added already.
|
||||
|
||||
|
||||
Send your report/request to mc-devel@gnome.org or mc@gnome.org. These
|
||||
mailing lists are the most certain way to contact the
|
||||
developers. Remember to mention if you are not on the mailing list
|
||||
to make sure that you will receive a copy of replies.
|
||||
|
||||
|
||||
Give as much details as possible. A too long message is a lot better
|
||||
than a too short message.
|
||||
|
||||
|
||||
For segmentation faults a stack backtrace is appreciated. You can
|
||||
produce stack backtrace as follows:
|
||||
* If segmentation fault produced a core file:
|
||||
@ -814,19 +808,19 @@ into drive D:"?
|
||||
command in your shell to allow producing of the core files.
|
||||
Usually it is "limit coredumpsize unlimited" or "ulimit
|
||||
coredumpsize" or "ulimit -c unlimited".
|
||||
|
||||
|
||||
9.4 How can I join the development?
|
||||
|
||||
To join the development just code the feature you want to add and send
|
||||
your patch for inclusion. Email address is mc-devel@gnome.org.
|
||||
Before you start coding check the latest development version. It might
|
||||
be that your feature has already been implemented.
|
||||
|
||||
|
||||
Note that the authors of GNU Midnight Commander have given all their
|
||||
rights on the program to the Free Software Foundation. You will have
|
||||
to do the same if you contribute non-trivial patches. Otherwise we
|
||||
have to reject your patches in order to avoid copyright problems.
|
||||
|
||||
|
||||
10 More information
|
||||
|
||||
10.1 This document didn't answer my question. Where else can I look for an
|
||||
@ -834,38 +828,38 @@ answer?
|
||||
|
||||
Read messages from the Discussion (mailing list archive) or read the
|
||||
Manual.
|
||||
|
||||
|
||||
Upgrade to a newer version of Midnight Commander. Many problems are
|
||||
fixed in the new versions.
|
||||
|
||||
|
||||
If you still can't find an answer, post your question to the Midnight
|
||||
Commander mailing list. Its address is mc@gnome.org.
|
||||
|
||||
|
||||
10.2 What mailing lists are there for Midnight Commander?
|
||||
|
||||
Following mailing lists discuss about Midnight Commander:
|
||||
|
||||
|
||||
mc@gnome.org
|
||||
General discussion of GNU Midnight Commander
|
||||
To subscribe visit
|
||||
http://mail.gnome.org/mailman/listinfo/mc/
|
||||
|
||||
|
||||
mc-devel@gnome.org
|
||||
Technical development discussion
|
||||
To subscribe visit
|
||||
http://mail.gnome.org/mailman/listinfo/mc-devel/
|
||||
|
||||
|
||||
10.3 Where should I look on the World Wide Web for MC stuff?
|
||||
|
||||
There is a WWW page for Midnight Commander. The URL is:
|
||||
|
||||
|
||||
http://www.gnome.org/mc/
|
||||
|
||||
|
||||
10.4 Are the mailing lists archived anywhere?
|
||||
|
||||
The mc and mc-devel lists are archived on the World Wide Web. There are
|
||||
links to the archives on the mailing list pages (see 10.2).
|
||||
|
||||
|
||||
11 Legal issues
|
||||
|
||||
11.1 Authorship
|
||||
@ -873,17 +867,17 @@ answer?
|
||||
Questions and Answers was written by Janne Kukonlehto. Parts of it
|
||||
originate from Ian Jackson, Miguel de Icaza, Dugan Porter, Norbert
|
||||
Warmuth and Paul Sheer.
|
||||
|
||||
|
||||
11.2 Feedback is invited
|
||||
|
||||
Send your comments about this document and GNU Midnight Commander to
|
||||
mc@gnome.org
|
||||
|
||||
|
||||
11.3 Disclaimer and copyright
|
||||
|
||||
Note that this document is provided as is. The information in it is
|
||||
not warranted to be correct; you use it at your own risk.
|
||||
|
||||
|
||||
You can use Questions and Answers according to GNU Public License (see
|
||||
the COPYING file in GNU Midnight Commander source distribution).
|
||||
Questions and Answers is not public domain.
|
||||
|
36
INSTALL
36
INSTALL
@ -172,9 +172,6 @@ better than everything else),
|
||||
example, if you have installed ncurses under /gnu/lib and
|
||||
/gnu/include, you specify: --with-ncurses=/gnu
|
||||
|
||||
Support for traditional UNIX curses (not ncurses) is obsolete and will be
|
||||
removed.
|
||||
|
||||
Run `configure --help' to see the full list of options.
|
||||
|
||||
On systems that require unusual options for compilation or linking
|
||||
@ -343,18 +340,11 @@ Midnight Commander. The included library is very stable and has been
|
||||
used for years without problems. You shouldn't expect any problems
|
||||
porting S-Lang to your platform.
|
||||
|
||||
Another possibility is to download and install ncurses on your OS. The
|
||||
Midnight Commander can use ncurses as well as the display engine. However,
|
||||
you may encounter minor differences, for instance, you will be unable to
|
||||
force the color mode by giving the "-c" switch to GNU Midnight Commander.
|
||||
|
||||
As the last resort, you may try to use the curses library supplied with
|
||||
your OS. Beware that some systems, e.g. SystemV Release 4, include the
|
||||
curses library with bugs critical to GNU Midnight Commander. You may try
|
||||
to recompile all your source code with the symbol BUGGY_CURSES defined,
|
||||
i.e.
|
||||
|
||||
make clean; make CFLAGS="-g -O -DBUGGY_CURSES"
|
||||
Another possibility is to download and install ncurses on your OS.
|
||||
GNU Midnight Commander can use ncurses as well as the display engine.
|
||||
However, you may encounter minor differences, for instance, you will
|
||||
be unable to force the color mode by giving the "-c" switch to GNU
|
||||
Midnight Commander.
|
||||
|
||||
|
||||
Obtaining the missing pieces of GNU Midnight Commander
|
||||
@ -402,19 +392,3 @@ And the GNU Compiler Collection may be obtained from the following sites:
|
||||
ftp://gcc.gnu.org/pub/gcc/releases/
|
||||
ftp://ftp.gnu.org/gnu/gcc/
|
||||
http://gcc.gnu.org/mirrors.html
|
||||
|
||||
Unsupported, deprecated and possibly broken options to configure:
|
||||
-----------------------------------------------------------------
|
||||
`--with-vcurses[=directory]'
|
||||
Use this flag to force GNU Midnight Commander to use a SystemV
|
||||
type curses, the optional directory specifies where the compiler
|
||||
should look for the include files.
|
||||
|
||||
`--with-sunos-curses'
|
||||
You use this flag on SunOS machines if you want to force using
|
||||
SunOS 4.x curses.
|
||||
|
||||
`--with-bsd-curses'
|
||||
If you don't want to use ncurses and are using an Ultrix box, you
|
||||
can use this switch. Be aware that ncurses is a better option
|
||||
than the curses included in Ultrix.
|
||||
|
32
acinclude.m4
32
acinclude.m4
@ -613,38 +613,6 @@ fi
|
||||
rm -f conftest*]
|
||||
)
|
||||
|
||||
AC_DEFUN([AC_USE_SUNOS_CURSES], [
|
||||
search_ncurses=false
|
||||
screen_manager="SunOS 4.x /usr/5include curses"
|
||||
AC_MSG_RESULT([Using SunOS 4.x /usr/5include curses])
|
||||
AC_DEFINE(USE_SUNOS_CURSES)
|
||||
AC_DEFINE(NO_COLOR_CURSES)
|
||||
AC_DEFINE(USE_SYSV_CURSES)
|
||||
CPPFLAGS="$CPPFLAGS -I/usr/5include"
|
||||
XCURSES="xcurses.o /usr/5lib/libcurses.a /usr/5lib/libtermcap.a"
|
||||
AC_MSG_RESULT([Please note that some screen refreshs may fail])
|
||||
AC_MSG_WARN([Reconsider using Slang])
|
||||
])
|
||||
|
||||
AC_DEFUN([AC_USE_OSF1_CURSES], [
|
||||
AC_MSG_RESULT([Using OSF1 curses])
|
||||
search_ncurses=false
|
||||
screen_manager="OSF1 curses"
|
||||
AC_DEFINE(NO_COLOR_CURSES)
|
||||
AC_DEFINE(USE_SYSV_CURSES)
|
||||
XCURSES="xcurses.o"
|
||||
LIBS="$LIBS -lcurses"
|
||||
])
|
||||
|
||||
AC_DEFUN([AC_USE_SYSV_CURSES], [
|
||||
AC_MSG_RESULT([Using SysV curses])
|
||||
AC_DEFINE(USE_SYSV_CURSES)
|
||||
XCURSES=""
|
||||
search_ncurses=false
|
||||
screen_manager="SysV/curses"
|
||||
LIBS="$LIBS -lcurses"
|
||||
])
|
||||
|
||||
AC_DEFUN([AC_USE_TERMINFO], [
|
||||
AC_DEFINE(SLANG_TERMINFO)
|
||||
AC_MSG_RESULT([Using SLang screen manager/terminfo])
|
||||
|
76
configure.in
76
configure.in
@ -308,51 +308,6 @@ search_ncurses=false
|
||||
XCURSES=""
|
||||
AC_SUBST(XCURSES)
|
||||
|
||||
dnl AC_ARG_WITH(bsd-curses,
|
||||
dnl [--with-bsd-curses Used to compile with bsd curses, not very fancy],
|
||||
dnl [search_ncurses=false
|
||||
dnl screen_manager="Ultrix/cursesX"
|
||||
dnl case $host_os in
|
||||
dnl ultrix*)
|
||||
dnl THIS_CURSES=cursesX
|
||||
dnl ;;
|
||||
dnl *)
|
||||
dnl THIS_CURSES=curses
|
||||
dnl ;;
|
||||
dnl esac
|
||||
dnl
|
||||
dnl LIBS="$LIBS -l$THIS_CURSES -ltermcap"
|
||||
dnl AC_DEFINE(USE_BSD_CURSES)
|
||||
dnl XCURSES="xcurses.o"
|
||||
dnl AC_MSG_RESULT([Please note that some screen refreshs may fail])
|
||||
dnl AC_MSG_WARN([Use of the bsdcurses extension has some])
|
||||
dnl AC_MSG_WARN([display/input problems.])
|
||||
dnl AC_MSG_WARN([Reconsider using xcurses])
|
||||
dnl])
|
||||
|
||||
AC_ARG_WITH(sunos-curses,
|
||||
[--with-sunos-curses Used to force SunOS 4.x curses],[
|
||||
if test x$withval = xyes; then
|
||||
AC_USE_SUNOS_CURSES
|
||||
fi
|
||||
])
|
||||
|
||||
AC_ARG_WITH(osf1-curses,
|
||||
[--with-osf1-curses Used to force OSF/1 curses],[
|
||||
if test x$withval = xyes; then
|
||||
AC_USE_OSF1_CURSES
|
||||
fi
|
||||
])
|
||||
|
||||
AC_ARG_WITH(vcurses,
|
||||
[--with-vcurses[=incdir] Used to force SysV curses],
|
||||
[if test x$withval = xyes; then :
|
||||
else
|
||||
CPPFLAGS="$CPPFLAGS -I$withval"
|
||||
fi
|
||||
AC_USE_SYSV_CURSES
|
||||
])
|
||||
|
||||
mouse_lib="xterm only"
|
||||
LGPM=""
|
||||
case $host_os in
|
||||
@ -714,38 +669,9 @@ then
|
||||
|
||||
AC_NCURSES(/usr/include/ncurses, curses.h, -lncurses, -I/usr/include/ncurses -DRENAMED_NCURSES, "renamed ncurses on /usr/include/ncurses")
|
||||
|
||||
dnl
|
||||
dnl We couldn't find ncurses, try SysV curses
|
||||
dnl
|
||||
if $search_ncurses
|
||||
then
|
||||
AC_EGREP_HEADER(init_color, /usr/include/curses.h,
|
||||
AC_USE_SYSV_CURSES)
|
||||
AC_EGREP_CPP(USE_NCURSES,[
|
||||
#include <curses.h>
|
||||
#ifdef __NCURSES_H
|
||||
#undef USE_NCURSES
|
||||
USE_NCURSES
|
||||
#endif
|
||||
],[
|
||||
CPPFLAGS="$CPPFLAGS -DRENAMED_NCURSES"
|
||||
AC_DEFINE(USE_NCURSES)
|
||||
search_ncurses=false
|
||||
screen_manager="ncurses installed as curses"
|
||||
])
|
||||
fi
|
||||
|
||||
dnl
|
||||
dnl Try SunOS 4.x /usr/5{lib,include} ncurses
|
||||
dnl The flags USE_SUNOS_CURSES, USE_BSD_CURSES and BUGGY_CURSES
|
||||
dnl should be replaced by a more fine grained selection routine
|
||||
dnl
|
||||
if $search_ncurses
|
||||
then
|
||||
if test -f /usr/5include/curses.h
|
||||
then
|
||||
AC_USE_SUNOS_CURSES
|
||||
fi
|
||||
:
|
||||
else
|
||||
# check for ncurses version, to properly ifdef mouse-fix
|
||||
AC_MSG_CHECKING([for ncurses version])
|
||||
|
Загрузка…
x
Ссылка в новой задаче
Block a user