Uday S Reddy <u.s.re...@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 _______________________________________________ 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