Re: [PATCH] switch to file buffer from command line args regardless of `initial-buffer-choice'

[Rasmus <rasmus@gmx.us>]

Hi,

Samer Masterson <samer@samertm.com> writes:

> The behavior with my patch: If Emacs is given one file arg, it's opened
> alongside `initial-buffer-choice'. If Emacs is given two or more file
> args, then it will display `initial-buffer-choice' and *Buffer List*,
> which is consistent with the current behavior when
> `initial-buffer-choice' is nil and Emacs is given more files than it can
> display.
>
> I've separated the command line processing logic for files from the
> buffer switching logic. This makes it much more clear what the final
> state of the windows will be. Also, whether the buffer list gets displayed is
> based on how many buffers are shown, not how many file args there are.

How do I get the name of the current buffer with this new behavior?

It broke batch export in org-mode cf. bug #21095.

To be specific,

   emacs --no-init-file --batch --file /tmp/foo --eval="(message \"%s\n\" (buffer-file-name))"

Used to return "/tmp/foo" before this patch.  Now it returns nil.

All I want is to run one function on one file.

Rasmus

-- 
. . . The proofs are technical in nature and provides no real understanding