From: Dan Davison <davison@stats.ox.ac.uk>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: shell: link output
Date: Sun, 02 May 2010 19:14:45 -0400 [thread overview]
Message-ID: <87wrvlc2vu.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <38DA8AC4-BD61-48BE-8384-540F369BF00A@tsdye.com> (Thomas S. Dye's message of "Sun, 2 May 2010 09:38:38 -1000")
"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
next prev parent reply other threads:[~2010-05-02 23:14 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 [this message]
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
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrvlc2vu.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).