Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Based on the manual and a look at the C code, I believe the answer is "no".</p> <p><kbd>M-:</kbd> <code>(info "(elisp) Echo Area Customization")</code> <kbd>RET</kbd> says:</p> <blockquote> <p>The variable `max-mini-window-height', which specifies the maximum height for resizing minibuffer windows, also applies to the echo area (which is really a special use of the minibuffer window; *note Minibuffer Misc::).</p> </blockquote> <p>The <code>Minibuffer Misc</code> link doesn't discuss that specific point further, but if the echo area explicitly uses the minibuffer window then you'll not be able to separate them.</p> <p><strong>Edit:</strong> </p> <p>For confirmation, if you look at the source for the C function <code>message3_nolog()</code> in <code>xdisp.c</code>, it obtains the frame for the selected frame's minibuffer, selects that, and then passes through to <code>echo_area_display()</code> which uses the currently-selected frame's minibuffer window as the echo area window.</p> <p>(Emacs 24.0.95)</p> <p>So the "mini window" used for the minibuffer and echo area is indeed one and the same, just as the manual states.</p> <p>The only possibility I can think of is to try to find a way of automatically <em>copying</em> echo area messages to some other window, but as this is all happening in C code, in functions not exposed to elisp, I suspect that's not possible either.</p> <p><strong>Edit 2:</strong></p> <blockquote> <p>Would it theoretically require rewriting C source code and recompiling Emacs?</p> </blockquote> <p>If you need genuine separation, then yes, I believe that is the case.</p> <p>If the copying approach was sufficient, you <em>might</em> be able to manage that purely in elisp by advising all of the functions which can result in messages being written to the echo area. You could start reading here to see what that might entail:</p> <p><kbd>M-:</kbd> <code>(info "(elisp) The Echo Area")</code> <kbd>RET</kbd></p> <p>(but if you are really desperate to implement this, I would suggest your time would be better spent working in C and providing a patch which would allow such a separation to be made, because I'm a little doubtful all that advice would be robust in the long term.)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload