From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: E Sabof Newsgroups: gmane.emacs.help Subject: Re: Help with async-shell-command Date: Wed, 05 Feb 2014 01:37:15 +0000 Message-ID: <87a9e6tk50.fsf@gmail.com> References: <87k3da1m04.fsf@enterprise.sectorq.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1391565794 14981 80.91.229.3 (5 Feb 2014 02:03:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Feb 2014 02:03:14 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Pete Ley Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Feb 05 03:03:20 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WArpf-0002c8-Tx for geh-help-gnu-emacs@m.gmane.org; Wed, 05 Feb 2014 03:03:20 +0100 Original-Received: from localhost ([::1]:57059 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WArpf-0006QX-Ie for geh-help-gnu-emacs@m.gmane.org; Tue, 04 Feb 2014 21:03:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WArQd-0003Ni-Jm for help-gnu-emacs@gnu.org; Tue, 04 Feb 2014 20:37:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WArQV-0001IJ-5B for help-gnu-emacs@gnu.org; Tue, 04 Feb 2014 20:37:27 -0500 Original-Received: from mail-we0-x22b.google.com ([2a00:1450:400c:c03::22b]:59098) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WArQU-0001IB-Us for help-gnu-emacs@gnu.org; Tue, 04 Feb 2014 20:37:19 -0500 Original-Received: by mail-we0-f171.google.com with SMTP id u56so4969748wes.16 for ; Tue, 04 Feb 2014 17:37:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version:content-type; bh=gZRUyhb8gCvrGfXOqQaGEHCq3qfhmik4LYCbyo/52s4=; b=Ln0a/yXpZQdJL2XNcGVLiB7whBZg702s8U+Rv4YQO9E67zdfeyWAlI3UJpKMzK525g WXkvBu5UxlAggtWXXcUvZvZNsklX6S8cpAKDbNNpH4qwdmtN5QLDuOcg+orfo9xPT5fR aMCLUKmkyVW8nhW9GN+kab0lYsQ0WDD+Mi45//w//uCZQwnXcUDt5QW9hqjsTu0oqMxp TX4VibJbWut81NQVA+1YVFYv3xl+hPJDzv3w+5M76C1UFzJxBtRRjhOCvNnl6nxgc5SS UYWz/0+5QC2eAdvvuWgahq8me3pVcNvFQr3/R+mZpULPbQic9Ihj7a1bUcdiqDvxabyL Ew4A== X-Received: by 10.180.79.7 with SMTP id f7mr447220wix.20.1391564237563; Tue, 04 Feb 2014 17:37:17 -0800 (PST) Original-Received: from ubuntu ([2.125.179.120]) by mx.google.com with ESMTPSA id n3sm40972694wix.10.2014.02.04.17.37.16 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 04 Feb 2014 17:37:17 -0800 (PST) User-agent: mu4e 0.9.9.6pre2; emacs 24.3.1 In-reply-to: <87k3da1m04.fsf@enterprise.sectorq.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c03::22b X-Mailman-Approved-At: Tue, 04 Feb 2014 21:03:09 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:95916 Archived-At: This is the usual way of preserving layout: (save-window-excursion (async-shell-command)) Evgeni peteley11235@gmail.com writes: > Hey, > > Is there a way to call async-shell-command so that it doesn't open an > output buffer? I'm trying to write a sync routine that'll get called > pretty often and I'd like to use async-shell-command, but it always > opens an annoying *Async Shell Command* buffer, even when there is no > output. > > So far, I've sort of solved the problem by writing a wrapper function > that calls it and (delete-windows-on "*Async Shell Command*") afterward, > but this has the side effect of closing a window I was using if the > window wasn't split for the purpose of the buffer. > > Is there a way I can 1) call a shell command asychronously 2) without > showing *Async Shell Command* and 3) without messing up my window setup? > > Thanks > Pete