all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: gearheart <yoyavova@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: Programatically suppress "Async Shell command" buffer
Date: Tue, 7 Jul 2009 11:32:46 +0200	[thread overview]
Message-ID: <2702DED8-7711-42E2-949C-440239CAFB09@Web.DE> (raw)
In-Reply-To: <24355670.post@talk.nabble.com>


Am 06.07.2009 um 15:43 schrieb gearheart:

> When async shell-command is run, i get empty buffer that takes like  
> half of
> the screen.


Half of the frame in which shell-command was run is standard  
behaviour (could be an option exists to set size as for example for  
the *compilation* buffer, compilation-window-height). If your shell  
command does return nothing or white space, then the temporary *Shell  
Command Output* buffer will look empty (in the fringe you can have  
exact indicators). If your shell command, say, a simple ls, should  
return readable output and you get an empty *Shell Command Output*  
buffer, then something is faulty. Then try the same by launching GNU  
Emacs as 'emacs -Q' without any customisation.

--
Greetings

   Pete

People say that if you play Microsoft CD's backwards, you hear  
satanic things, but that's nothing, because if you play them  
forwards, they install MS Windows.





  reply	other threads:[~2009-07-07  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 13:43 Programatically suppress "Async Shell command" buffer gearheart
2009-07-07  9:32 ` Peter Dyballa [this message]
2009-07-07 18:00   ` gearheart
     [not found]   ` <mailman.2021.1247001256.2239.help-gnu-emacs@gnu.org>
2009-07-10  2:17     ` dnquark
2009-07-10  3:30       ` dnquark
2009-07-10 10:48         ` Peter Dyballa
2009-07-10 11:01           ` Leo Alekseyev
2009-07-10 10:43       ` Peter Dyballa
2009-07-10 11:02 ` Johan Bockgård

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=2702DED8-7711-42E2-949C-440239CAFB09@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=Help-gnu-emacs@gnu.org \
    --cc=yoyavova@gmail.com \
    /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.