unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Major usability issue
Date: Tue, 03 Sep 2002 12:22:54 +0200	[thread overview]
Message-ID: <vafelcbid8h.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: mailman.1030996683.19870.help-gnu-emacs@gnu.org

Bruce Korb <bkorb@pacbell.net> writes:

> For years I have captured the output of a shell command and inserted
> it into my document.  The latest distributions of Linux now carry a
> version of emacs that makes doing that non-obvious.  I'm sure it is
> doable, but it is really important to just be able to ALT-| then
> type a command and be able to use a mouse click to capture the text.
> I haven't read emacs lisp macros yet in order to reverse-engineer
> what has been done; but I shouldn't have to either.  :-(

Well, what is the obvious thing that you do and what happens when you
do it?  From your description it's not clear to me what you're doing.

Maybe you just need to switch to the *Shell Command Output* buffer
and copy the text from there?  This buffer is not shown by default,
when the output of the shell command is short.

See the document on shell-command-on-region to see how to change it:

/----
| If the command generates output, the output may be displayed
| in the echo area or in a buffer.
| If the output is short enough to display in the echo area
| (determined by the variable `max-mini-window-height' if
| `resize-mini-windows' is non-nil), it is shown there.  Otherwise
| it is displayed in the buffer `*Shell Command Output*'.  The output
| is available in that buffer in both cases.
\----

Does this help?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

  parent reply	other threads:[~2002-09-03 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1030996683.19870.help-gnu-emacs@gnu.org>
2002-09-02 20:04 ` inserting output of shell-command (was: Major usability issue) lawrence mitchell
2002-09-02 20:33   ` Lute Kamstra
2002-09-03 10:22 ` Kai Großjohann [this message]
2002-09-03 20:52   ` Major usability issue Bruce Korb
     [not found]   ` <mailman.1031086444.5149.help-gnu-emacs@gnu.org>
2002-09-03 21:12     ` Barry Margolin
2002-09-03 22:46       ` Bruce Korb
2002-09-04  1:58       ` Miles Bader
2002-09-03 22:11     ` Kai Großjohann
2002-09-03 13:36 ` Peter Boettcher
2002-09-02 20:01 Bruce Korb

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=vafelcbid8h.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).