I must agree with samjones. Different actions on Ctlr+C and Ctrl+Ins are very confused and I never remember what is what.
It could be configurable or works logically like this (Ctrl+C and Ctrl+Ins are the same):
Empty command line and no files on panel selected: copy file or folder under cursor
Empty command line and files or folders are selected: copy selected files or folders
Not empty command line and no files selected: copy command line
Not empty command line and files or folders selected: copy command line (not empty command line should be prefer before selected files)
Anything selected or not on panels, not empty command line and a selection exists in command line: copy the selection in command line
Simple, logic and there's no need to differ between Ctrl+C and Ctrl+Ins.
In eastern europe, it is normal to use ctrl-ins, not ctrl-c
In north america, it is normal to use ctrl-c, and not ctrl-ins
It is understandable that ctrl-c was dropped by accident, since a lot of FAR users don't use it.
But for us americanskis, the builds without ctrl-c are not useable at all.
samjones wrote:It is understandable that ctrl-c was dropped by accident, since a lot of FAR users don't use it.
It wasn't.
The change had been actively discussed in the Russian-language part of the forum and even re-implemented once.
Rather than moan time after time, you are encouraged to create macros for whatever key bindings you like.
OK, HaRT, I have created macro, it's a solution. After all, I think that Ctrl-C is now totally useless and confused (why should I copy selected files on panel if command line is not empty?). I never use Ctrl-Ins, always Ctrl-C and in FAR it is always suffering. I never new what I actually copy.
Both of the shortcuts could be configurable somewhere in setup options, while default option should be that Ctrl-C is the same as Ctrl-Ins - I don't know about other program that makes differences between this shortcuts. I remember Photoshop in some older version ignored Ctrl+Ins shortcut and left only Ctrl+C - but very quickly they had to return it back.
The shortcuts are configurable and the configuration mechanism is macros. And if there were a macro on Ctrl+C by default to invoke Ctrl+Ins, then the instructions on how to copy files to clipboard would be even more confusing — “it’s on Ctrl+C but by default there is a macro there that copies selected text so you’ll have to remove that first”.
The default keybindings in FAR are not there to please the majority of users. They are to make all existing features possible. From that, each user makes their own FAR, tailored to that particular user.
Actually I think that different action of this two similar hotkeys - bad idea.
But I doubt we can change anything now, since this idea was implemented by Far Team leader - t-rex.
John Doe wrote:Actually I think that different action of this two similar hotkeys - bad idea.
But I doubt we can change anything now, since this idea was implemented by Far Team leather - t-rex.
If t-rex is the "leather" - so, who are the "bones" I wonder?
Copy the names of selected files to the clipboard Ctrl-Ins
(if the command line is empty)
Copy the files to clipboard Ctrl-C
(ignore command line state)
Copy the names of selected files to the clipboard Ctrl-Shift-Ins
(ignore command line state)
Copy full names of selected files to the clipboard Alt-Shift-Ins
(ignore command line state)
Copy network (UNC) names of selected files to the Ctrl-Alt-Ins
clipboard (ignore command line state)
Also you can create trivial keyboard macro to reassign Ctrl-Ins (or Ctrl-Shift-Ins) action to Ctrl-C.