* 8 line identical minibuffer & *Shell Command Output*
@ 2003-06-17 9:18 Dan Jacobson
0 siblings, 0 replies; 2+ messages in thread
From: Dan Jacobson @ 2003-06-17 9:18 UTC (permalink / raw)
Really ugly:
$ emacs --no-site-file -q -eval '(and(shell-command "seq 9")(shell-command "seq 8"))'
One sees a 8 line high minibuffer totally wastefully repeating an 8
line *Shell Command Output* buffer. They occupy the bottom half of
the screen.
$ grep -i ^emacs .Xresources
Emacs*bitmapIcon: on
Emacs*font: fixed
Emacs.geometry: 95x35+-6+-6
Emacs*FontSet: -*-big5-0,-adobe-*-iso8859-1
GNU Emacs 21.2.2 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
2002-10-16 on raven, modified by Debian
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 8 line identical minibuffer & *Shell Command Output*
[not found] <mailman.8123.1055889164.21513.bug-gnu-emacs@gnu.org>
@ 2003-06-18 19:31 ` Kevin Rodgers
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Rodgers @ 2003-06-18 19:31 UTC (permalink / raw)
Dan Jacobson wrote:
> Really ugly:
> $ emacs --no-site-file -q -eval '(and(shell-command "seq 9")(shell-command "seq 8"))'
> One sees a 8 line high minibuffer totally wastefully repeating an 8
> line *Shell Command Output* buffer. They occupy the bottom half of
> the screen.
Uh, so what? (It's not the minibuffer, it's the echo area). Emacs has
behaved as documented:
| shell-command is an interactive compiled Lisp function in `simple'.
| (shell-command COMMAND &optional OUTPUT-BUFFER ERROR-BUFFER)
|
| Execute string COMMAND in inferior shell; display output, if any.
| With prefix argument, insert the COMMAND's output at point.
|
| If COMMAND ends in ampersand, execute it asynchronously.
| The output appears in the buffer `*Async Shell Command*'.
| That buffer is in shell mode.
|
| Otherwise, COMMAND is executed synchronously. The output appears in
| the buffer `*Shell Command Output*'. If the output is short enough to
| display in the echo area (which is determined by the variables
| `resize-mini-windows' and `max-mini-window-height'), it is shown
| there, but it is nonetheless available in buffer `*Shell Command
| Output*' even though that buffer is not automatically displayed. If
| there is no output, or if output is inserted in the current buffer,
| then `*Shell Command Output*' is deleted.
> $ grep -i ^emacs .Xresources
> Emacs*bitmapIcon: on
> Emacs*font: fixed
> Emacs.geometry: 95x35+-6+-6
> Emacs*FontSet: -*-big5-0,-adobe-*-iso8859-1
The default values of `resize-mini-windows' and `max-mini-window-height'
are `grow-only' and 0.25 respectively. 0.25 times 35 (the frame height)
is 8.75, which is larger than 8 (the number of lines in the minibuffer
window).
> GNU Emacs 21.2.2 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
> 2002-10-16 on raven, modified by Debian
On GNU Emacs 21.3.1 (i386-pc-solaris2.7, X toolkit), the *Shell Command Output*
buffer is not displayed.
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-06-18 19:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.8123.1055889164.21513.bug-gnu-emacs@gnu.org>
2003-06-18 19:31 ` 8 line identical minibuffer & *Shell Command Output* Kevin Rodgers
2003-06-17 9:18 Dan Jacobson
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).