I am starting up emacs and I cannot see aynthing in the minibuffer or display window until it starts up. Is there a reason for this?
Is there a reason for this?
Yes, because it is busy starting emacs. However, it logs the most important messages in a buffer called
*Messages* and in the operating systems log or event viewer -- depending on your operating system.
As others have commented above, after emacs has finishing starting up, look into the
*Messages* buffer or the system's log for any clues to what could be ailing. Post those messages here to help you narrow down the cause.
Lastly, look into starting emacs with --debug command line option to get more verbose error messages logged to both the screen (during startup) and to the
I believe the answer given by @EmacsUser is right.
To better understand what's happening: Emacs has been around for a long time. Back in the day, I/O (input/output) with terminals was very slow. Because Emacs is incredibly powerful, it was enhanced so that output to the screen would wait for internal processing to complete. That's why your screen "freezes" when you execute that macro you just defined with an argument of 12345 -- Emacs is busy working on your buffer(s). When it's done, Emacs will refresh the portions of your sreen that need refreshing.
When Emacs starts up, it typically has a lot of things to do. Unless one of those things blocks, screen updates are essentially ignored (i.e. they're very low priority), so you won't see what's happening behind the scenes until Emacs is done processing.