From: Jens Persson <jens.persson.1833@student.uu.se>
Subject: Re: Scroll down *Schell Command Output* buffer when output arrives
Date: Tue, 25 Feb 2003 12:59:55 +0100 [thread overview]
Message-ID: <3E5B5ABB.5030707@student.uu.se> (raw)
In-Reply-To: wc3y945r5wh.fsf@gamma.cis.ohio-state.edu
Ok, thanks! Guess I should have thought of that ... But is it impossible
to (if you just wanted to do it that way for some reason) make the Shell
Command Output buffer scroll down automatically every time it gets new
output?
Benjamin Rutt wrote:
> Jens Persson <jens.persson.1833@student.uu.se> writes:
>
>
>>The ouput of these shell-command calls goes into the *Shell Command
>>Output* buffer, and now I only want it to automatically scroll down
>>every time new output arrives to it so that the last lines of the
>>output is visable, how can i do this? Is there some hook that i can
>>add a "end-of-buffer" to or something?
>>
>
> Why not run them under `compile', which will do the scrolling for you
> automatically.
>
> e.g.
>
> (defun csound-compile-curr-osc-sco ()
> (interactive)
> (compile (concat "csound -A -d -o test.aif "
> (file-name-sans-extension (buffer-name)) ".orc "
> (file-name-sans-extension (buffer-name)) ".sco")))
>
> (global-set-key [f8] 'csound-compile-curr-osc-sco)
>
next prev parent reply other threads:[~2003-02-25 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 15:45 Scroll down *Schell Command Output* buffer when output arrives Jens Persson
2003-02-24 16:37 ` Benjamin Rutt
2003-02-25 11:59 ` Jens Persson [this message]
2003-03-05 16:14 ` Robert Figura
2003-03-04 22:28 ` Kevin Rodgers
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E5B5ABB.5030707@student.uu.se \
--to=jens.persson.1833@student.uu.se \
/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.
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).