1. General questions
1.1. Why does Far not develop the way I want?
slightly edited quote from one of the developers: Skirda wrote: Far Manager is an open and free project. Nobody gets paid for it. Participation is completely voluntary. Reward - honor and glory (only an indication in the CONTRIBUTORS file).
Everyone helps in any way they can, depending on the availability of personal time, interest and knowledge. Nobody here owes anything to anyone. Screams, snot and sobs in the vest will not help.
There are standard mechanisms for presenting Wishlist and indicating bugs - the Mantis bug tracker (but snot is not considered there either, everything is just on business).
There is this forum where all sorts of technical aspects are discussed (however, due to what was said earlier, this does not guarantee implementation).
If you know how and know, send a patch to Mantis (but due to your ignorance or lack of knowledge about the inner workings of Far, the patch may not pass, which will be indicated on the bugtracker).
If you don’t like all this, then there are many file managers on the web that can fully satisfy your needs.
1.2. I found a bug and want it fixed, what should I do?
Behavior when problems are detected.
1.3. How to correctly and quickly take a screenshot of the Far window?
Use Alt-Ins combination. Use the arrow keys or the mouse to select the desired fragment. After that, press Enter - the fragment will be copied to the clipboard.
1.4. It is difficult to find the necessary information in the built-in Far help, how to make the search easier?
- First of all, read the help section How to use the help.
- The search system (F7) allows you to find a given substring, but the search result is presented as a list of sections, which is not always convenient.
- To find the exact location of the occurrence, you can open the help file in the editor and search there: edit:%farhome%\farrus.hlf.
(For convenience, this command can be placed on a custom menu.)
Once you have found the desired string, you can open the desired Help topic by pressing F1. This function requires the HlfViewer plugin, which is included in the Far distribution.
First of all, it depends on the architecture of the OS used:
- Only FAR x86 can work on 32-bit version of Windows.
- If Windows is 64-bit, then both versions work.
FAR x64 is preferable, but in some cases it makes sense to use FAR x86 (for example, if you have to use a plugin that exists only for the x86 architecture).
There is no fundamental difference.
Far develops gradually, and at some point the next "nightly" assembly is declared "stable".
As a rule, in the so-called. A "stable" build is less likely to encounter, for example, a recently introduced bug.
But sometimes in "stable" there may be more problems, because. "night" ones are updated much more often and bugs are fixed quite quickly.
Follow the changes, read the forum.
2. How to upgrade to Far 3
2.1. Where to download Far 3?
You can always get the latest version of Far 3 on the official website.
(Older builds of Far 3 are also available for now).
2.2. What's new in Far 3 compared to Far 2?
- Significant changes in the API to increase the capabilities of plugins.
Far 2 plugins are not directly supported, but there is an unofficial solution, see 3.3.
- In the list of plug-ins (F11) you can view information about the selected plug-in (F3).
- All settings are now stored in the SQLite database, making Far 3 fully portable. See also 6.2.
- Settings can be imported and exported via XML files. See 6.5.
- Built-in configuration editor (far:config, see 6.1), providing quick access to all headlight settings, including those that are not configured anywhere else (former "TechInfo", see 4.5).
- Settings are not lost if the Far window is closed with a “cross” in the upper right corner.
- The built-in viewer has been almost completely rewritten: full support for UTF-8, a new dump mode for viewing binary files, and many related changes.
- Optimization of the editor for working with large files.
- Ability to use not the standard 16 colors of the console palette, but any RGB colors plus additional font attributes (bold / italic / underlined).
Requires ConEmu or Windows 10 console emulator to work.
The new Windows 10 console is supported starting from build 5288, enabled in the options: Interface settings / Use Virtual Terminal for rendering.
- In each of the "Links to folders" you can now make several links (Commands -> Links to folders).
- It is now possible to use any number of custom panel view modes (besides the standard 10). More
- The macro language is now based on the Lua language (luajit), and through the LuaFAR library, almost all plugin features are available to macros.
Macros are stored as macro files.
- User ("custom") sorting modes in panels using luajit.
- Highlighting files that have more than one hard link (hardlink).
- Improved information panel (Ctrl-L).
- Improved quick view panel (Ctrl-Q).
- Search function for built-in F1 help. See 1.4.
- Instead of the so-called. "C0-columns" can now be an arbitrary number of content-columns (discussion).
- Customization of language files without editing the generated "native" .lng files (discussion).
- Built-in associations extend to the command line ( discussion ).
- Dialogues can be non-modal (discussion).
More details can be found in the history of changes.
The main changes are as follows:
- Support for the Unicode standard, which manifests itself in the normal processing of files with any characters in the names, as well as Unicode support in the editor.
Using UTF-16 allows you to represent 65,536 individual characters, which is enough to fully represent the Basic Multilingual Plane.
The use of surrogate pairs (writing a character in two words) would allow 1,112,064 characters to be represented, but surrogate pairs are not supported in the spotlight.
In practice, this means that symbols from additional planes will not be displayed correctly (as 2 separate symbols).
Forum: viewtopic.php?p=79006#p79006, viewtopic.php?p=116295#p116295
- Native support for dynamic loading/unloading of plugins.
- Far (and many plugins) supports paths of any length (but the NTFS file system has a path length limit of 32000 characters).
- Now Far does not block the current folder (the exception is the presence of old plugins developed for Far 1.7).
- Auto-completion in dialog input lines and command line.
- UAC support: if there are not enough rights to perform the operation, then a request for administrator privileges is issued.
(Far 3 also introduced the ability to elevate privileges when launched from panels - Ctrl-Alt-Enter)
- Ability to select the desired plugin in the case when several of them can process the same file.
- Significantly expanded macro language.
- Incremental filtering of any menus and lists (both drop-down and normal), the mode is activated by Ctrl-Alt-F.
(In Far 3 you can use RAlt.)
- Support for the so-called. "C0 plugins".
Code: Select allt-rex 06/12/2010 07:14:06 PM +0200 - build 1588
- Experimental, informal and crooked to look at, play around and think about:
support for custom columns (C0) populated by plugins in non-plugin file panels
Now in the panel you can see specific information about the files on the panel in the "C0" column, for example, the exe / dll version, mp3 tags, html and pdf headers, zip archive comments, file status in svn, and more.
- An option in the interface settings that improves the display in ClearType mode (due to a console bug without this option, artifacts may appear - vertical stripes that are clearly visible on the copy progress indicators, etc.)
- Optimized the work of various stories (saving works much faster).
- Large screen buffer mode (for viewing long output of console programs). See 7.4.
- Auto-update disk menu and hotplug list when adding/removing USB, CD/DVD, etc.
- Auto-update environment variables when changing them in the OS settings.
Macros are no longer stored in the registry, but in macro files.
You won't be able to transfer them automatically, but the Macro2Lua converter simplifies the task.
Help with porting macros can be found on the forum.
2.5. How to transfer settings from Far 2 to Far 3?
To transfer colors, associations, coloring / sorting groups, folder links, panel modes, you can use an almost automatic converter:
- Download all files of the far2x3 converter and extract them to any folder.
- Exit Far 3 and run the convert_all.cmd file.
- Copy all received .xml files to the folder with Far 3 and run the command from this folder: Code: Select allfor %i in (far3_.xml) do far.exe /import %i Help on using the converter can be found on the forum.
- Run Far 2, enter the menu (F2).
- Press Alt-F4 to launch the menu editor.
- Select the entire file, copy it to the clipboard.
- Run Far 3, enter the menu (F2).
- Press Alt-F4 to launch the menu editor.
- Paste text from clipboard, save file.
Use Ftp2Netbox.lua script
Help on migrating to Far 3 can be found here.
3. Plugins in Far 3
3.1. Where to download plugins?
- The official repository of plugins - plugging.
- Not all authors upload fresh versions for plugging yet, so it makes sense to search here on the forum.
- Macros and lua scripts have all the features of plugins, see the forum.
Far 1.7 plugins are supported and most work fine (discussion).
They still store their settings in the registry, in the HKCU\Software\Far Manager\Plugins branch (unlike native Far 3 plugins that use SQLite databases).
3.3. Do plugins from Far 2 work in Far 3?
Far 2 plugins are not directly supported.
If the plugin you need does not have a version for Far 3, then you can try to connect it using an unofficial wrapper (forum support).
3.4. I installed the plugin, but it didn't show up in FAR. How to install plugins correctly?
- Check if the versions of Far and the plug-in being installed match.
The plugin documentation should indicate that it is developed for FAR 3.
In addition, FAR 1.7 plugins are supported (the Plugins manager settings / [x] OEM plugins support option must be enabled).
Pay special attention to the fact that FAR and the plugin are designed for the same processor architecture:
FAR x64 requires x64 plugins, FAR x86 requires x86 plugins.
- If the plugin documentation does not specify special installation requirements, then create a folder with an arbitrary name in %FARHOME%\Plugins, unpack the plugin distribution package there and restart FAR.
(In addition to %FARHOME%\Plugins, you can use %FARPROFILE%\Plugins.)
- As a rule, a plugin adds a corresponding item to the plugin menu, plugin settings menu or disk menu, but this is optional, see the plugin documentation.
- If the plugin has built-in help, then it can be accessed by pressing Shift-F1 in the list of plugins (or F1, Shift-F2 and select it there).
- It is also useful to explore the plugin's customization options, if the plugin provides for it. Plugin configuration menu can be called by Alt-Shift-F9.
- If, despite the execution of the previous points, the plugin could not be installed, then contact the forum for help.
Search for a theme for your plugin; if it doesn't exist, create a new one.
4. Problems after switching to Far 3
4.1. Can't copy file name, Ctrl-C combination doesn't work, why?
The Ctrl-C combination is designed to work with the command line. To copy file names, use the Ctrl-Ins combination (and other combinations, see the built-in Help). Discussion.
4.2. Can't create RAR archive. Where is the MultiArc plugin?
MultiArc is not included in the distribution package, replaced by the ArcLite plugin.
If necessary, MultiArc can be downloaded separately.
Warning: MultiArc does not support Unicode in filenames.
4.3. Why does the right mouse button bring up the context menu instead of marking files?
By default, when you click on a file in the RightClick or Shift-RightClick panels, the EMenu plugin is called (other combinations, such as Ctrl-RightClick, will be marked as before).
To return the old behavior, you need to use the Options / Panel Settings / [x] Right click selects files setting.
4.4. Where did setting the path to personal plugins go?
This setting no longer exists.
Personal plugins are searched in the profile folder %FARPROFILE%\Plugins. See 6.2.
4.5. Where to look for parameters from the former TechInfo.txt? Still on the register?
There are no hidden settings in Far anymore.
Some of the settings have been moved to the interface, some have been removed, the rest are available through the configuration editor (see 6.1).
A description of the options can be found in the help (Shift-F1 on the option name in the configuration editor, or see the general list in the help file index).
Some parameters are not yet described.
Note: the TechInfo.txt file is still present in the distribution, the information remaining there needs to be moved to other sections of the documentation.
5. Features of the operating system
5.1. Frames of panels and dialogs are displayed as bugs, how can I fix this?
Select the correct font in the console properties, for example, Lucida Console or Consolas.
5.2. Instead of some characters (for example, the Ukrainian letter "??"), question marks are displayed, what should I do?
Select the correct font in the console properties, for example, Lucida Console or Consolas.
5.3. File sizes are displayed as "hexadecimal numbers" (eg 20a484a123), what should I do?
- Select the correct font in the console properties, for example, Lucida Console or Consolas.
- Make changes to the regional settings of the OS (default separators are taken from the OS).
- Change the Interface.FormatNumberSeparators parameter available through the configuration editor (see 6.1). Help can be accessed by pressing Shift-F1.
After the change, you need to save the settings (Shift-F9) and restart Far.
The file system (NTFS) allows these names, but most programs do not.
To protect against accidental creation of files/folders with such names, you can use the Fix Incorrect Names plugin or a macro with similar functionality.
If, when trying to delete (using F8) files/folders with such names, Far gives an error, then use the Shift-Del combination or disable the Delete to Recycle Bin option (Options / System settings / [ ] Delete to Recycle Bin).
Attention: if the option [x] Delete to Trash is enabled, if you try to delete a file with a dot at the end, then Windows will try to delete a file of the same name without a dot (if it exists).
5.5. How to switch to full screen mode (Alt-Enter) in Windows Vista/7/8 (or x64 versions of Windows XP/2003)?
This is not possible due to a limitation of the operating system.
But when using ConEmu, you can enable full-screen emulation by Alt-Enter.
Note: in Windows 10, the ability to switch to full screen mode was returned (does not work if "Use legacy console" is enabled).
5.6. When running Far as administrator, network drives are not displayed. What to do?
More about the problem: https://support.microsoft.com/kb/937624/, http://technet.microsoft.com/library/ee844140
The easiest solution is to run the following command from the command line: Code: Select allREG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLinkedConnections /t REG_DWORD /d 1
You need to run it as an administrator, for this the key combination Ctrl-Alt-Enter is used.
5.7. With the active Russian layout, the RAlt key does not work (neither separately nor in combinations). What to do?
The problem is related to the kb2970228 update (Windows 7), which introduces the
₽symbol into the system.
Solution: Uninstall the specified update, or fix and install the keymap using MSKLC.
5.8. What other Windows settings affect Far?
The following is an excerpt from TechInfo.txt. The information was not checked in modern operating systems and on current versions of Far.TechInfo.txt wrote:Code: Select all
II. Windows: settings affecting Far Manager.
This section describes additional technical details, anyway affecting the operation of Far Manager.
Code: Select all
2.0.(TechInfo #57) When Far starts, deletes an empty registry branch [HKEY_CLASSES_ROOT\Directory\shellex\CopyHookHandlers] If this branch is empty, then when folders are deleted to the trash, Far crashes. 2.1.(TechInfo #58) [HKEY_CURRENT_USER\Control Panel\Desktop] "AutoEndTasks":REG_DWORD System: Automatically Close Hung Applications This option is used to automatically close without any warnings of all hung programs. Can be one of the following values: 0 - the option is disabled. 1 - allow automatic closing of applications. The default value is 0 (disabled). Changing the key value to "1" fixes the problem when closing the built-in modal editor (for example, called on the file inside the archive) Far with the standard "Close" button of the Far console window. Read more: http://www.winguides.com/registry/display.php/199/ 2.2.(TechInfo #59) [HKEY_CURRENT_USER\Software\Microsoft\Command Processor] "DisableUNCCheck":REG_DWORD (applies to NT4/2k/XP/2003/Vista/2008 and cmd.exe only) CMD.EXE does not support UNC paths by default. If far try execute a shell command if the current path is UNC, then the following information is displayed in the console: "The specified path was used when running CMD.EXE as the current folders. CMD.EXE does not support UNC paths. System is selected by default. Windows folder. Command syntax error." CMD.EXE was launched with '\\server\share' as the current directory. UNC paths are not supported. Directory selected by default Windows. "CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory." (output information may differ in NT4/W2k/XP/2003/Vista/2008) The "DisableUNCCheck" parameter solves this problem. Meaning parameter can be one of the following: 0 - display a warning message and set the current path equal to the Windows system folder. 1 - do not display a warning message and try to set the current path equal to UNC path. The default setting on Windows is 0. Recommended value 1. Read more: http://www.winguides.com/registry/display.php/1247/ or in Microsoft article - Q156276
5.9. What are the features of the new Windows 10 console?
Links to discussions:
- Windows 10 Console Host bugs
- In Windows 10 1709 (FCU), console scrolling using hotkeys fell off
- Problems of the new Windows 10 console
- Changed background color in standard color scheme
- Lived up? (New experimental console features in Windows "Threshold")
6. Settings and configuration
6.1. How to use the built-in configuration editor (far:config)?
The configuration editor is launched from the command line using the far:config command.
DrKnS wrote:far:config is primarily a tool for changing settings that are not available through the normal interface.
The fact that the options available through the normal interface are displayed there is nothing more than a side effect.
Some values ??are used only to initialize other values, there is no point in changing them.
Some of the options can only be configured here (former "TechInfo", see 4.5), but most of the settings are available in other places: through the options menu (F9/Options/…), or in some "internal" service dialog, or by hot key.
Configuration editor help - F1, help for individual parameters - Shift-F1 (may lead to the description of the dialog in which the parameter is configured, among others).
At the moment, help is not displayed for all parameters (and for some the wrong section is displayed, this is a known issue).
Changing some parameters does not take effect immediately, but the next time you start Far, so after any changes it is recommended to exit the configuration editor, save changes (Shift-F9) and restart Far.
Read more on the forum.
6.2. Where does Far store settings and macros?
In FAR 3, all settings are stored in SQLite databases, which are *.db files located in the profile folder. The subfolders of the profile also contain the plugin settings databases PluginsData\ and the user menu (FarMenu.ini).
Macros are located in the Macros\scripts\ subfolder (for details, see %FARHOME%\Encyclopedia\macroapi_manual.ru.chm).
The Plugins\ profile subfolder is used to install personal plugins.
By default, the profile is located in the Windows user's system profile: %APPDATA%\Far Manager.
You can place the profile in any other convenient place. To specify the location of the profile, there are such ways:
- command line switch: -s <profilepath> [<localprofilepath>]
— Far.exe.ini file: missing by default, you need to copy Far.exe.example.ini and edit it.
For example, to use a profile in the Far folder, it is enough to set the UseSystemProfiles=0 parameter (for other parameters, see the comments on Far.exe.example.ini).
See also 6.3.
These are Windows environment (environment) variables.
For example, APPDATA, LOCALAPPDATA, mentioned in Far.exe.example.ini, are system variables that determine the standard placement of various data for all applications in the user's Windows profile.
Variables FARHOME, FARPROFILE, FARLOCALPROFILE (and some others) are assigned by Far on startup.
- FARHOME - the path to the folder where far.exe is located.
— FARPROFILE, FARLOCALPROFILE — path to folders containing Far settings (profile).
Thus, you can find out the path to the folder where the currently used profile is located by executing the set FARPROFILE command from the FAR command line, and you can go to this folder with the chdir %FARPROFILE% command.
See also 6.2.
In Far, only some settings are saved immediately, the rest are saved only after forced saving by Shift-F9.
You can activate the [x] Auto save setup parameter (off by default), in this case the settings will be saved automatically, but not immediately after application, but at the moment you exit Far.
In addition, if several copies of Far are running with the same profile, and the settings have been changed in several, it is difficult to predict the result.
A special case is importing settings from a file (for more details, see 6.5): it is recommended to do this by exiting all running Far instances (at least all running with the current profile).
6.5. How to export Far settings and plugins? How to import settings correctly?
The export/import mechanism via XML files (*.farconfig) allows you to conveniently share settings and keep a backup copy of your own settings in a relatively readable form.
Both functions are performed from the command line by running far.exe with the appropriate parameters:
- far.exe /export <out.farconfig> - export Far settings and plugins (those that store settings in SQLite databases).
If there are unsaved settings, then it makes sense to save them first.
The resulting out.farconfig can be edited, leaving only the necessary part of the settings (for example, if you need a separate coloring scheme, or only file associations, or some plugin settings, etc.)
- far.exe /import <in.farconfig> - import Far settings and plugins.
Before executing, be sure to exit Far (from all running instances working with the current profile).
You can also specify the path to the profile in the command line, if you are not supposed to work with the current profile, see the help on command line switches (Far.exe -?).
Macros contains useful keyboard shortcuts.
Colors contains custom color schemes.
Shell contains add-ons to integrate FAR with the Windows shell.
SetUp contains sets of options for quick setup.
XLat contains Xlat tables for transliteration.
To install any of the *.farconfig files available there, you need to exit Far and run the command: Far.exe /import filename.farconfig.
To install any of the *.lua files available there, just copy them to the %FARPROFILE%\Macros\scripts folder (or any of its subfolders) and reload the macros with the lm:load command (or restart Far).
All *.farconfig and *.lua files attached to Faro are provided with descriptions. For the convenience of working with them, switch to the Long Descriptions panel mode (LCtrl-7).
7.1. How to save file without BOM?
By default, the headlight editor creates unicode BOM files.
Some applications may not work with such files.
You can save the file without the BOM by pressing Shift-F2 in the editor and deselecting the Add Signature (BOM) checkbox.
To always create files without BOM, you can set the special parameter Editor.AddUnicodeBOM = false, available through the configuration editor (see 6.1).
In addition, with the help of plugins and macros, you can flexibly configure which types of files to use BOM and which not, more details on the forum.
7.2. Why does the encoding auto-detection in the editor/viewer sometimes work incorrectly?
If the file does not contain a BOM, then statistical methods are used to determine the encoding.
For small files, the detection error is large, and sometimes unexpected encodings can be erroneously detected.
In this case, you can switch the encoding manually (see 7.3).
In addition, it is possible to limit the detection to a given set of encodings using the Codepages.NoAutoDetectCP parameter available through the configuration editor (see 6.1).
Detailed help can be obtained by placing the cursor on the desired option and pressing Shift-F1.
7.3. How to change the text encoding in the editor?
The answer to this question is not so simple - due to the uncertainty in the terminology (see the forum) and some internal limitations of Far.
Without touching the technical details, you can answer like this: - If the text in the editor is displayed correctly, then you can select a different encoding when saving using the Shift-F2 combination.
- If the text in the editor is displayed incorrectly, then you can change the encoding using the combinations F8 (switching OEM / ANSI) or Shift-F8 (full set of encodings).
- Sometimes it is not possible to change the encoding in the editor using F8/Shift-F8.
In this case, the required encoding can be specified when opening the file using the Shift-F4 combination.
In this case, you must specify the file name; to insert the name of the current file from the active panel, it is convenient to use the Shift-Enter combination.
One of two ways:
- The mode is activated if Far is launched with the /w key: far.exe /w.
- To use this mode permanently, it is necessary to change the parameter: System.WindowMode = true, available through the configuration editor (see 6.1). Be sure to save changes (Shift-F9) and restart Far.
After WindowMode is activated, you can set the desired screen buffer size in the console properties or using third-party utilities or plugins.
This combination may be occupied by a third-party application or macro. First of all, try to fix the problem, guided by the recommendations on the link from paragraph 1.2.
It is worth reading the following discussions: viewtopic.php?f=20&t=7741, viewtopic.php?f=9&t=9132.
Further help can be found here.
7.6. How can I get the year value in dates to be displayed with four digits?
It is necessary to increase the width of the corresponding column by 2 characters in the panel mode settings.
7.xx. I did not find my problem in this FAQ, what should I do?
Follow the recommendations in the link from paragraph 1.2, which describes in detail the behavior when problems are detected.
Suggestions and additions are accepted!