From: Dan Davison <davison@stats.ox.ac.uk>
To: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: shell: link output
Date: Mon, 03 May 2010 18:15:25 -0400 [thread overview]
Message-ID: <874oio639e.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <hrng60$76a$1@dough.gmane.org> (Uday S. Reddy's message of "Tue, 04 May 2010 00:45:26 +0100")
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
next prev parent reply other threads:[~2010-05-03 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2010-05-04 1:48 ` Uday S Reddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874oio639e.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=u.s.reddy@cs.bham.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.