Re: Question about initial-buffer-choice

[Joel Reicher <joel.reicher@gmail.com>]

CToID <funk443@yahoo.com.tw> writes:

> So for example, if `initial-buffer-choice` is set to t, and I 
> try to open a file in Emacs using command-line, i. e. enter 
> `emacs foobar.js` in my terminal.  Then Emacs will start up, but 
> in addition to one window displaying the content of `foobar.js`, 
> there is also another window containing scratch buffer.
>
> I'm not sure if this is intended behaviour or not, but if Emacs 
> is started through command-line, with file arguments given, 
> shouldn't it only display the content of file(s), but not the 
> initial buffer?

I get behaviour similar to what I think you want by always using 
emacsclient to open files, and including --no-splash in the 
command for alternate editor.

You might be able to do a different customisation the same way so 
that it applies only when directly opening files when an emacs 
server is not already running.

Regards,

        - Joel