all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: how to set shell output always to *Shell Command Output*
Date: Thu, 16 Sep 2010 07:13:52 -0700 (PDT)	[thread overview]
Message-ID: <ba36eb81-a041-4de0-b639-944fd23ade18@g6g2000pro.googlegroups.com> (raw)
In-Reply-To: eadeb989-3378-46c5-b552-82e89f4f3841@z34g2000pro.googlegroups.com

On Sep 16, 5:57 am, TheFlyingDutchman <zzbba...@aol.com> wrote:
> On Sep 12, 11:17 pm, Xah Lee <xah...@gmail.com> wrote:
>
> > when running a shell command, if the output is small, it shows in the
> > “*Messages*” buffer.
>
> > is there a way to always have the output in the “*Shell Command
> > Output*” buffer?
>
> > thanks.
>
> >  Xah
>
> Setting the symbol resize-mini-windows to nil seems to send output
> that is more than one line to *Shell Command Output* and 1 line outout
> to the mini buffer window.

humm... doesn't seems a satisfying solution. Just read the doc:

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.

so the output is always in “*Shell Command Output*”, the trick is to
always switch to it, and with the default behavior of spliting window
to show it. Seems hard to do that...

anyway, not really important. Thanks and thanks mp.

 Xah


  reply	other threads:[~2010-09-16 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  6:17 how to set shell output always to *Shell Command Output* Xah Lee
2010-09-16 12:57 ` TheFlyingDutchman
2010-09-16 14:13   ` Xah Lee [this message]
2010-09-17 18:56     ` TheFlyingDutchman
2010-09-17 19:25       ` Xah Lee
2010-09-19  8:56         ` TheFlyingDutchman
2010-09-16 13:00 ` TheFlyingDutchman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ba36eb81-a041-4de0-b639-944fd23ade18@g6g2000pro.googlegroups.com \
    --to=xahlee@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.