--log-file parameter didn't create log file

[kenorb]

Description

I'm running Atom with --log-file parameter, but the log file isn't created. Tested on macOS Sierra.

Steps to Reproduce

$ /Applications/Atom.app/Contents/MacOS/Atom --help | grep log
  -l, --log-file             Log all output to file.  [string]
$ /Applications/Atom.app/Contents/MacOS/Atom -l ~/.atom/atom.log
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
$ ls -la ~/.atom/
# The log file is not there.

Reproduces how often: All the time.

Versions

$ atom --version
Atom    : 1.18.0
Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0
$ apm --version
apm  1.18.1
npm  3.10.10
node 6.9.5 x64
python 2.7.10
git 2.13.3

[rsese]

Reproduced with Atom 1.18.0 on macOS 10.12.6 and Atom 1.17.2 on Ubuntu 16.04.

[lee-dohm]

We should probably just remove this option.

[freeman42x]

It is still not working on current version of Atom.

[sadick254]

--log-file option seem only to used in the context of running tests. This use case doesn't provide much benefits to a developer debugging.

atom/spec/jasmine-test-runner.coffee

Line 142 in e3fa317

buildTerminalReporter = (logFile, resolveWithExitCode) ->

Moving forward in my opinion we should deprecate the --log-file option since having a log file could be achieved by redirecting the output to a file.

# Unix based systems
atom --dev --foreground --wait > debug.log

# Windows 
atom --dev --foreground --wait >> debug.log

[sadick254]

Since the log-file option has been there for a long time. I think it would be better to clarify its usage other than deprecating it.