From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: shell: link output Date: Sun, 2 May 2010 13:54:36 -1000 Message-ID: <35E8EF08-3BD2-49B2-A62D-98EDBEC0B767@tsdye.com> References: <38DA8AC4-BD61-48BE-8384-540F369BF00A@tsdye.com> <87wrvlc2vu.fsf@stats.ox.ac.uk> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O8izm-0005eq-SX for emacs-orgmode@gnu.org; Sun, 02 May 2010 19:54:46 -0400 Received: from [140.186.70.92] (port=45125 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O8izk-0005ea-LV for emacs-orgmode@gnu.org; Sun, 02 May 2010 19:54:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O8izi-00081n-7O for emacs-orgmode@gnu.org; Sun, 02 May 2010 19:54:44 -0400 Received: from oproxy2-pub.bluehost.com ([66.147.249.254]:58274 helo=outbound-mail-360.bluehost.com) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1O8izh-00081S-VS for emacs-orgmode@gnu.org; Sun, 02 May 2010 19:54:42 -0400 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: Dan Davison Cc: emacs org-mode mailing list On May 2, 2010, at 1:14 PM, Dan Davison wrote: > "Thomas S. Dye" writes: > >> Aloha all, >> >> A link like this in my Org-mode buffer: >> >> [[shell:$PATH]] >> >> sends output to a buffer called *Shell Command Output*, which on my >> system, at least, remains buried. I'd like to display the buffer >> when >> the user clicks the link, ideally in another window of the same >> frame. How can I do this? > > Hi Tom, > > 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 you meant [[shell:echo $PATH]], so that the output is on > stdout > not stderr, but I don't think that alters conclusions. > > Dan Thanks for the help Dan. That's what I needed to know. All the best, Tom