all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@deadspam.com>
Subject: breakthrough: I was asked something in a *compilation* window
Date: 22 Jun 2002 08:14:53 +0800	[thread overview]
Message-ID: <87n0torwxu.fsf_-_@jidanni.org> (raw)
In-Reply-To: jk1yb07vna.fsf@glug.org

Amazing breakthrough in the realm of commands to provide the user: a
way for him to talk back when a *compilation* comes to a screeching
halt an asks the user a question thru the impenetrable one way glass...

Sure you lisp programmers do this all the time but us "M-x blabla"
users haven't had a tool...

>>>>> "T" == Thien-Thi Nguyen <ttn@glug.org> writes:

T> i bind ":" to the following:

T> (defun compilation-send-line (line)
T>   (interactive "sLine: ")
T>   (process-send-string (buffer-name) (concat line "\n")))

T> when prompted, i type something like `: y RET'.

This seems to be an amazing breakthrough.   With a little polish this
should be an immediate candidate for  inclusion into the next emacs
[and M-x compile documentation.]

notes on usage: one should do
(setq compilation-scroll-output t)

By the way, emacs bug: in a *compilation* window do C-h m, gee, sure
looks puny these days.  Where's all the special bindings?
Also the user will never learn about e.g. compilation-scroll-output
from there or C-h f compile.
-- 
http://jidanni.org/ Taiwan(04)25854780

      parent reply	other threads:[~2002-06-22  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 21:58 I was asked something in a *compilation* window Dan Jacobson
2002-06-21  8:09 ` Kai Großjohann
2002-06-21 16:58   ` Kevin Rodgers
2002-06-23 23:19     ` Francesco Potorti`
2002-06-25 15:50       ` Kevin Rodgers
2002-06-26 22:24         ` Richard Stallman
     [not found] ` <jk1yb07vna.fsf@glug.org>
2002-06-22  0:14   ` Dan Jacobson [this message]

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=87n0torwxu.fsf_-_@jidanni.org \
    --to=jidanni@deadspam.com \
    --cc=Kindly_Remove_This_jidanni@ms46.hinet.net \
    /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.