The 'file' utility determine the file type differently:
till file-5.16 - Java Jar file data (zip)
since file-5.17 - Java archive data (JAR)
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
mountlist: don't use libmount to decide on dummy/remote.
Don't use the libmount routines to determine whether a file system is
dummy or remote, as they're not currently compatible. For example the
remoteness is determined on file system type (for which the list seems
incomplete), rather than simply checking for a ':' in the device name.
Also libmount currently determines that 'tmpfs' is a dummy file system
even though it has associated storage.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
mountlist: use /proc/self/mountinfo when available
Use libmount to propagate device IDs provided by Linux in
/proc/self/mountinfo. This will give more accurate output when using df
in chroot'ed environments as the device IDs are not determined by stat()
which may be inaccurate within the chroot.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
Don't remove the destination file if it was retrieved incompletely
but it was already exist and appended during copy/move operation.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
* 3247_status_msg_update_rate:
(status_msg_init): repaint screen forced to remove previous finished dialog.
Reduce update rate in the "Directory scanning" dialog.
status_msg_t: reimplement delay usage.
(mc_time_elapsed): add new function to detect elapsed time intervals.
Ticket #3247: refactoring of status_msg engine.
As a result, directory scannig is faster than before.
The author of idea and initial patch is Egmont Koblinger.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
mc fails to build when using musl as the libc provider. This is due to
the CTRL() macro not being defined in <termios.h>. We could include
<sys/ttydefaults.h> explicitly but it's easier just to ensure CTRL is
defined.
This patch taken from the Sabotage Linux distro which fixes this. This
patch has also been tested and works with the OpenEmbedded build
system.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
* 3245_viwer_goto_line:
mcviewer: remove "(decimal)" from "Line number (decimal)" label.
Ticket #3245: mcviewer: make goto line 1-based instead of 0-based.
export PS1=$'\[\e[38:5:214m\]orange$\[\e[0m\]'
mc
Expected: "orange$" prompt shows up in black under the panels.
Actual: some additional garbage.
The 256-color and true-color escape sequences should allow either ';' or
':' inside as separator, actually, ':' is the more correct according to
ECMA-48. Some terminal emulators (e.g. xterm, gnome-terminal) support
this.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
* 3189_cleanup:
Ticket #3258: fix incorrect percentage in mcview hex mode.
Ticket #3244: add viewbold and viewselected missing from some skins.
Ticket #3242: mcviewer: remove an unused variables and needless loops.
Ticket #3240: fix recognition of UnRAR version.
Ticket #3239: fix incorrect enconding name for manual pages.
A few typofixes.
Massive use of MC_PTR_FREE macro.
Add declaration of g_error_new_valist().
Don't use 'register' keyword.
(sftpfs_open_socket): remove useless condition.
(panel_operate_generate_prompt): ret rid of extra argument.
Ticket #3189: code cleanup before 4.8.13 release.
The percent in the upper right corner normally corresponds to the
cursor. Except when the bottom of the file is displayed, then it's
100%.
If the file is taller than the window, you can walk downwards to its
end and the percent is always correct. Then walk back a screenful and
it stays at 100%, and suddenly jumps back by a lot when the file starts
scrolling.
If the file is shorter than the window, it's always at 100%.
mcview_calc_percent() is supposed to calculate the percentage at offset
p, yet it executes a special branch when "dpy_end == filesize".
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
Change "black" and "white" to "rgb000" and "rgb555" when it's rendered
in bold, because the legacy 16 colors change their actual color in
addition to going bold in most of the terminals which is undesired.
Second, there was some unintended difference between the two gray skins
in the file type colors.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>