Page 1 of 1

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 08:21
by tarka0
1.Run long command, like:
ping -t somehost

2.Press Ctrl+C

Far application closes.
This problem appeared on some previous build, approx month ago.
--
Tomas

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 08:31
by Shmuel
Windows XP SP3, Far 3.0.4201 x86
It works properly:

Code: Select all

E:\BB\F\Today>ping -t www.microsoft.com

Pinging e10088.dscb.akamaiedge.net [23.44.247.174] with 32 bytes of data:

Reply from 23.44.247.174: bytes=32 time=17ms TTL=59
Reply from 23.44.247.174: bytes=32 time=17ms TTL=59
Reply from 23.44.247.174: bytes=32 time=17ms TTL=59

Ping statistics for 23.44.247.174:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 17ms, Average = 17ms
Control-C

E:\BB\F\Today>

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 11:23
by tarka0
I am running Windows 7, 64bit.
Have tried FAR 3.0.4201 64bit - it does not crash.

I have tried delete profile and eliminated old plugins
by running extracted
Far30b4201.x86.20141124.7z
from different directory. Does not help, crash.
Does far manager has some debug option to generate logs?

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 11:30
by Shmuel
I doubt that the problem is with Far Manager. It looks like the console window containing Far is closed.

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 13:34
by tarka0
Far 2.0.1807 x86 also behaves the same on my PC: Far window is closing after after "ping -t somehost" then Ctrl+C.
I have tried different windows user profile, problem the same, both FAR2 and Far3 x86 are closing after interrupting command with Ctrl+C.

You may be right. But how to solve this?

If I run in Far x86:

1. CMD /K
3. Type "Exit" + [Enter]
4. CMD closed, FAR is is running.

1. CMD /K
2. Press Ctrl + C
3. Type "Exit" + [Enter]
4. FAR window is closed

CMD /C ping -t somehost
Ctrl+C also closes FAR window.

Far 64bit or plain CMD console have now this problem.

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 13:59
by Shmuel
tarka0 wrote: Far 64bit or plain CMD console have now this problem.
If a plain CMD console also has this problem then Far is definitely not the cause.
Try to google it (my knowledge in this field is limited).

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 14:00
by tarka0
sorry for misstype:
"Far 64bit or plain CMD console have not this problem."

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 14:03
by Shmuel
Let's hope someone else has the idea what happens. I don't.

FAR 3.0.4201 x86

Posted: Mon 24 Nov, 2014 16:45
by Maximus5
Run cmd.exe first and than x86 far.exe. Try ping and CtrlC.