On Tue, 26 Sep 2006, [EMAIL PROTECTED] wrote:
On Mon, 25 Sep 2006, [EMAIL PROTECTED] wrote:
Where is the dead symlink located?
In the same directory as the file being edited.
If one user opens a file with mcedit for editing and another user
does the same with mcedit should he get a
Hi Stefan,
You might want to check the mailing list for developers. I've sent you an
answer on March 22 and an updated 'dar' plugin (amongst others) on April 3.
Since I don't use 'dar' personally I'm not sure whether the functionality is
what you are looking for. Please let me know whether the
Several months ago I suggested that the MC documentation include some
information to help users solve terminal emulation problems. Since then
I have managed to solve some of my particular problems and discovered a
few things. Granted, my knowledge is still mostly gaps, but I'll offer
this for
On Wed, 27 Sep 2006, Anton Monroe wrote:
3) You could try compiling MC with a different screen library. You
have a choice of using the Slang library that comes with MC, or the
version of Slang that is (probably) already on your computer, or the
version of Ncurses that is (probably)
hi Guus,
yes, the 'dar' extfs plugin works fine! That's exactly what I was
looking for. Good work, many thanks.
I noticed it's very fast to open (browse) a big dar archive - much
faster than opening an equivalent '.tar.gz'. When restoring a directory
with many files it's a bit slow, maybe
I suggest adding to NASM/TASM macros in the master copy:
keyword whole %ifndef brightred
keyword whole %elifdef brightred
keyword whole %if brightred
Those that hack asmutils might like adding this to their copy:
# asmutils system.inc macros:
keyword whole CODESEG brightblue
URL:
http://savannah.gnu.org/bugs/?17874
Summary: Crashing inside liblow.c
Project: GNU Midnight Commander
Submitted by: fojtik
Submitted on: Wednesday 09/27/2006 at 19:43
Category: None
Severity: 3 -
Follow-up Comment #1, bug #17874 (project mc):
Acconding to further analysis, I have found a fix inside liblow.c
I absolutelly don't know why mc passes here NULL. May be that new glibc is
more sensitive to NULL than old one. (mc -d is also workaround, but this
don't kill mouse.)
/* do we really
