bug#44794: 28.0.50; Frame creation broken with (tool-bar-mode -1)

[David Fussner]

Thanks for the tip -- it says "GNU Emacs at newfont" when it first
comes up, then prepends the buffer name to that later.

On Sun, 22 Nov 2020 at 19:16, Stefan Kangas <stefan@marxist.se> wrote:
>
> David Fussner <dfussner@googlemail.com> writes:
>
> > Forgive my incompetence, but my idea for how to do that appears to be
> > faulty -- what would be the simplest way to detect which branch the
> > code takes?
>
> Maybe one of these could work:
>
> 1. One way which doesn't involve any coding, but might require you to be
> fast, is to type "emacs --no-desktop" to just use your normal init file.
> If your init file takes sufficiently long to load, you can glean if the
> default title says either "GNU Emacs at foo" or just "GNU Emacs" before
> it has time to change.  (If it's too fast, maybe you could add a
> (sleep-for 10) to the beginning of your init file.)
>
> 2. If that is impractical for some reason, you could just add a call to
> exit() to each of them in turn and see when it doesn't start.
>
> 3. Or, less intrusively, I think you can just add to one branch:
>
>     Fmessage ("one");
>
> And to the other:
>
>     Fmessage ("two");
>
> Then check the "*Messages*" buffer for which one gave you any output.