Starting Emacs from the command line with a file name doesn't open the file after setting initial-buffer-choice
lckarssen opened this issue · comments
Lennart C. Karssen commented
If I set
(setq initial-buffer-choice (lambda () (get-buffer "*dashboard*")))
as mentioned in the README file and run emacs path/to/some/file
from a shell, Emacs won't open that file (as it used to). I guess this is normal behaviour, but it I think it is worth to mention it as it may impact people's workflow.
Rakan Al-Huneiti commented
Terencio Agozzino commented
@lckarssen, a temporary solution has been provided here: #115
Ben Finney commented
This would be relatively straightforward to address, if we can interrogate Emacs for "what filenames and elisp functions, if any, were specified on the command line?" and get a simple answer. If empty, create the Dashboard buffer; otherwise, don't.
Does such a simple interrogation exist for Emacs?