xparq / farmanager

File and Archive Manager

Far Manager

https://www.farmanager.com

	AppVeyor	Travis	Azure
VS
GCC			TBD
Clang			TBD

Far Manager — what is it?

Far Manager is a program for managing files and archives in Windows operating systems. Far Manager works in text mode and provides a simple and intuitive interface for performing most of the necessary actions:

• viewing files and directories;
• editing, copying and renaming files;
• and many other actions.

Customize it

Far Manager has a multi-language, easily configurable interface. File system navigation is made easier through the use of color highlighting and sort groups.

Your task — your way

The functionality of Far Manager is greatly extended by external DLL modules — plugins (made possible by a special set of interfaces — the Plugins API). For example: archive support, FTP client, temporary panel and network browser are all implemented as plugins included in the standard distribution of Far.

Support forum

https://forum.farmanager.com/

Bug tracker

https://bugs.farmanager.com/

Developers mailing list (english)

https://groups.google.com/group/fardeven
[email protected]

Developers mailing list (russian)

https://groups.google.com/group/fardev
[email protected]

Commits mailing list

https://groups.google.com/group/farcommits
[email protected]

Source code

https://github.com/FarGroup/FarManager

farmanager's Issues

FAR implicitly appends startup dir to PATH

When you know your .cmd script is not supposed to run, or another version is running mysteriously, then it may take some wasted time to figure out that when in FAR, commands are not only searched for in the apparent current (panel) dir, but also in the original working dir at FAR's startup.

Can be quite handy, if you know about that, but if not -- and how could you, without scavenging the docs? because, unfortunately, it's not actually appended to the PATH, so you cannot see it, it's just the behavior, "as if"... --, it can be very confusing. (--> "Principle of Least Surprise".)

Editor: wrong file mode when updating existing file on Samba share

Noticed that the x bit got accidentally set by FAR in some cases, on my Samba share, i.e. when

a) breaking symlinks and replacing them with a copy in a regular file (see #2)
b) updating existing files (creating them seems OK).

Some testing showed that file mode is 674 vs. the normal 644 on initial create.

Again: e.g. NOTEPAD doesn't have this problem in the same dirs.

Editor: Saving files breaks symlinks on Samba shares

Seems to happen on my NAS, while at the same time NOTEPAD saves the file OK.
NOTE: this may depend on some config. option, too!

(Tested on both on NTFS and extfs volumes, and with relative (dir-local) and absolute ("wide") links, too.)

~10 seconds startup delay (e.g. on my Win7)?!

When there was a network drive as a saved panel dir, I understood.
But now they are just local SSD locations, with not many files, so nothing special.

Maybe it's Windows (and/or ConHost, DLL caching etc.) itself: just the window to appear takes half of the time, alone.
And then the cursor blinks in the corner of the blank black screen for the other half of it.
Closing and restarting FAR is then instantaneous.

FYI:

• Taskman says 2.7GB RAM is used ouf of 4.
• I already have several consoles open, 3-4 with FAR, too.
• And I have clink, too, with its default config, but launching a plain cmd window was instantaneous after that delayed "cold" start -- but so was FAR...
  -> Need to test launching a plain cmd first, before trying FAR!

Disable UTF-8 BOM by default

See relevant discussion: https://forum.farmanager.com/viewtopic.php?t=9658

There may already be an option for it in the profile, maybe, just not in the UI:

Add syntax highlighting (by default?) for the viewer, too.

Maybe it's there already. Maybe I just disabled it (but... I'd be surprised).

Well, not in the "Viewer Settings":

Add placeholder to the -title cmdline option

OK, I'm a bit late to the party: I forgot to turn on Issues before actually implementing this already... ;)