From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uday S Reddy Subject: Re: shell: link output Date: Tue, 04 May 2010 00:45:26 +0100 Message-ID: References: <38DA8AC4-BD61-48BE-8384-540F369BF00A@tsdye.com> <87wrvlc2vu.fsf@stats.ox.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O93Sc-0003PR-St for emacs-orgmode@gnu.org; Mon, 03 May 2010 17:45:55 -0400 Received: from [140.186.70.92] (port=34992 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O93Sb-0003Om-G1 for emacs-orgmode@gnu.org; Mon, 03 May 2010 17:45:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O93SZ-0000Ya-Lu for emacs-orgmode@gnu.org; Mon, 03 May 2010 17:45:53 -0400 Received: from lo.gmane.org ([80.91.229.12]:33591) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O93SZ-0000YW-E0 for emacs-orgmode@gnu.org; Mon, 03 May 2010 17:45:51 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1O93ST-0000xG-6N for emacs-orgmode@gnu.org; Mon, 03 May 2010 23:45:45 +0200 Received: from cpc10-harb6-0-0-cust112.perr.cable.virginmedia.com ([92.232.137.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 May 2010 23:45:45 +0200 Received: from u.s.reddy by cpc10-harb6-0-0-cust112.perr.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 May 2010 23:45:45 +0200 In-Reply-To: <87wrvlc2vu.fsf@stats.ox.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On 5/3/2010 12:14 AM, Dan Davison wrote: > > It displays the output in the minibuffer, right? I'm not sure there's a > very easy solution. Documented behaviour of `shell-command' is that > > ,---- > | 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 it seems rather hard-wired to me (i.e. you'd have to write your own > function or use defadvice). I think `shell-command' displays the *Shell Command Output* buffer only when it is called interactively. When it is called programatically, I think they expect the calling program to display the *Shell Command Output* buffer separately. Org mode is not doing so. Cheers, Uday