all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* shell: link output
@ 2010-05-02 19:38 Thomas S. Dye
  2010-05-02 23:14 ` Dan Davison
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas S. Dye @ 2010-05-02 19:38 UTC (permalink / raw)
  To: emacs org-mode mailing list

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: shell: link output
  2010-05-02 19:38 shell: link output Thomas S. Dye
@ 2010-05-02 23:14 ` Dan Davison
  2010-05-02 23:54   ` Thomas S. Dye
  2010-05-03 23:45   ` Uday S Reddy
  0 siblings, 2 replies; 6+ messages in thread
From: Dan Davison @ 2010-05-02 23:14 UTC (permalink / raw)
  To: Thomas S. Dye; +Cc: emacs org-mode mailing list

"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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: shell: link output
  2010-05-02 23:14 ` Dan Davison
@ 2010-05-02 23:54   ` Thomas S. Dye
  2010-05-03 23:45   ` Uday S Reddy
  1 sibling, 0 replies; 6+ messages in thread
From: Thomas S. Dye @ 2010-05-02 23:54 UTC (permalink / raw)
  To: Dan Davison; +Cc: emacs org-mode mailing list


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Re: shell: link output
  2010-05-03 23:45   ` Uday S Reddy
@ 2010-05-03 22:15     ` Dan Davison
  2010-05-04  1:48       ` Uday S Reddy
  0 siblings, 1 reply; 6+ messages in thread
From: Dan Davison @ 2010-05-03 22:15 UTC (permalink / raw)
  To: Uday S Reddy; +Cc: emacs-orgmode

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: shell: link output
  2010-05-02 23:14 ` Dan Davison
  2010-05-02 23:54   ` Thomas S. Dye
@ 2010-05-03 23:45   ` Uday S Reddy
  2010-05-03 22:15     ` Dan Davison
  1 sibling, 1 reply; 6+ messages in thread
From: Uday S Reddy @ 2010-05-03 23:45 UTC (permalink / raw)
  To: emacs-orgmode

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: shell: link output
  2010-05-03 22:15     ` Dan Davison
@ 2010-05-04  1:48       ` Uday S Reddy
  0 siblings, 0 replies; 6+ messages in thread
From: Uday S Reddy @ 2010-05-04  1:48 UTC (permalink / raw)
  To: emacs-orgmode

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-05-03 23:49 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-02 19:38 shell: link output Thomas S. Dye
2010-05-02 23:14 ` Dan Davison
2010-05-02 23:54   ` Thomas S. Dye
2010-05-03 23:45   ` Uday S Reddy
2010-05-03 22:15     ` Dan Davison
2010-05-04  1:48       ` Uday S Reddy

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.