Closed Maximus5 closed 4 years ago
When Far executes "set" internally, ConEmu do not get control over command start/end,
because there are not commands at all.
So, if you want to see them in "View Console Output" you have to set up them in Far
to be called via CMD.EXE
Reported by ConEmu.Maximus5
on 2015-04-26 21:51:28
… in which case you won't be able to affect FAR environment variables with these commands,
'cause they'll be modifying a child process instead.
Yep they're not spawning a child console process. But any chance maybe to capture the
output from FAR process console itself?
Reported by baltic@hypersw.net
on 2015-04-26 23:19:02
> you won't be able to affect FAR environment variables with these commands
Not exactly true - http://conemu.github.io/en/ConEmuEnvironment.html#Export_variables
Yep, it's not so handy but powerful. I'm using this for setting up build environment.
More. Do you really need to view output of "set aaa=bbb"? I doubt. And there are different
ways to pass "set aaa" to cmd.exe (macros, or just "cmd /c set ...").
> But any chance maybe to capture the output from FAR process console itself?
Don't want to implement hacks unless Far team provide API for that.
Look, issue is not closed yet, there are chances.
Reported by ConEmu.Maximus5
on 2015-04-26 23:27:17
At last. Why do you want to see "View Console Output"? To get handy view of "SET" command?
There is a really easy way via Macro.
Macro {
area="Shell";
key="AltF4";
description="Execute CmdLine and redirect output to Editor";
flags="NotEmptyCommandLine";
action = function()
Keys("CtrlHome") print("edit:<") Keys("Enter")
end;
}
Reported by ConEmu.Maximus5
on 2015-04-26 23:28:58
Reported by ConEmu.Maximus5
on 2015-04-26 23:29:07
Originally reported on Google Code with ID 1971
Reported by
baltic@hypersw.net
on 2015-04-26 01:57:55