shell: link output

shell: link output

[Thomas S. Dye]

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?

All the best,
Tom

Re: shell: link output

[Dan Davison]

"Thomas S. Dye" <tsd@tsdye.com> 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

>
> All the best,
> Tom
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: shell: link output

[Thomas S. Dye]

On May 2, 2010, at 1:14 PM, Dan Davison wrote:

> "Thomas S. Dye" <tsd@tsdye.com> 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

Re: Re: shell: link output

[Dan Davison]

Uday S Reddy <u.s.reddy@cs.bham.ac.uk> writes:

> 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.

Hi Uday,

Hmm, no, I think what I wrote was correct :) If the output is too long
to fit in the minibuffer, then shell-command does display the output
buffer, whether in interactive or non-interactive context (at least in
emacs 24 on linux).

Dan

>
> Cheers,
> Uday
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: shell: link output

[Uday S Reddy]

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

Re: shell: link output

[Uday S Reddy]

On 5/3/2010 11:15 PM, Dan Davison wrote:

>
> Hmm, no, I think what I wrote was correct :)

Indeed, you are!  I did something wrong in my test :-(

Cheers,
Uday