Re: Programatically suppress "Async Shell command" buffer

[dnquark <dnquark@gmail.com>]

To add: I can redirect the command output to /dev/dull, but the
problem is that I cannot run the command in a dired buffer since it is
read-only.  Is there a way to specify that the command produces no
output so that it could be possible to run in a read-only buffer,e.g.
dired?

On Jul 9, 10:17 pm, dnquark <dnqu...@gmail.com> wrote:
> I was just trying to figure out how to get this to work; this helped
> but there still is a problem: once the asyncshellcommand terminates,
> whatever output it produces (I think it's on stderr) which would
> normally go to the dedicated output buffer gets inserted into my
> current buffer.  How do I suppress all output from the command?..
>
> On Jul 7, 2:00 pm, gearheart <yoyav...@gmail.com> wrote:
>
> > Peter Dyballa wrote:
>
> > > Am 06.07.2009 um 15:43 schrieb gearheart:
>
> > >> When asyncshell-commandis run, i get empty buffer that takes like  
> > >> half of
> > >> the screen.
>
> > > Half of the frame in whichshell-commandwas run is standard  
> > > behaviour (could be an option exists to set size as for example for  
> > > the *compilation* buffer, compilation-window-height). If yourshell 
> > >commanddoes return nothing or white space, then the temporary *Shell 
> > >CommandOutput* buffer will look empty (in the fringe you can have  
> > > exact indicators). If yourshellcommand, say, a simple ls, should  
> > > return readableoutputand you get an empty *ShellCommandOutput*  
> > > buffer, then something is faulty. Then try the same by launching GNU  
> > > Emacs as 'emacs -Q' without any customisation.
>
> > oops, my bad.
> > to call asyncshellcommandwithout a buffer you need to run:
> > (shell-command"something&" (universal-argument))
> > --
> > View this message in context:http://www.nabble.com/Programatically-suppress-%22Async-Shell-command...
> > Sent from the Emacs - Help mailing list archive at Nabble.com.