unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: Need an enabler for a bad habit.
Date: Wed, 01 Nov 2006 18:03:38 +0100	[thread overview]
Message-ID: <u3b933xqt.fsf@gmail.com> (raw)
In-Reply-To: mailman.19.1162399165.2155.help-gnu-emacs@gnu.org

William Case <billlinux@rogers.com> writes:

> Essentially, yes.  But I have always thought what you have called
> the echo area was the mini-buffer in emacs and I don't even need the
> "M-x prompt".  I just want my cursor blinking in the very first
> field/column of the echo area.  I will type the command or
> accelerator keys that I need after the cursor is placed.  I would
> expect that the cursor would remain at the end of the command line
> until I push Enter.

It's interesting to learn how other wants to use this wonderful tool!

How about this then:

 $ emacs -Q
 C-x 2 ; split in two windows
 C-x 0 ; move to bottom window
 M-x eshell RET ; start eshell

Now, resize the window containing the eshell buffer so that it's only
a few lines high (three lines seems to be the minimum before the
windows is deleted).

Now you have something similar to what you want in that you can type
all commands, including their arguments. For example, at the eshell
prompt:

 $ find-file foo RET

Will open up the file foo, or create an empty buffer. Voila!

The only problem with this approach is that commands that display a
prompt when called interactively will not work like you expect. For
example, only typing `find-file' and RET will not work. It will
complain about missing arguments (because it is called
non-interactively behind the scenes).

Of course, eshell is also a complete shell, being able to call emacs
functions is just an extra feature that is really nice.

  parent reply	other threads:[~2006-11-01 17:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.472.1162314011.27805.help-gnu-emacs@gnu.org>
2006-10-31 17:34 ` Need an enabler for a bad habit Pascal Bourguignon
2006-11-01  9:33   ` Mathias Dahl
2006-11-01 11:25     ` William Case
     [not found]     ` <mailman.12.1162380544.2155.help-gnu-emacs@gnu.org>
2006-11-01 15:05       ` Mathias Dahl
2006-11-01 16:38         ` William Case
2006-11-01 17:55           ` Peter Dyballa
2006-11-01 20:17           ` Kevin Rodgers
2006-11-01 23:12             ` William Case
2006-11-02 18:54               ` Kevin Rodgers
2006-11-01 23:28             ` William Case
     [not found]         ` <mailman.19.1162399165.2155.help-gnu-emacs@gnu.org>
2006-11-01 16:45           ` David Kastrup
2006-11-01 17:03           ` Mathias Dahl [this message]
2006-11-03 17:59             ` Drew Adams
     [not found] <mailman.67.1162475959.2155.help-gnu-emacs@gnu.org>
2006-11-02 14:23 ` Mathias Dahl
2006-11-02 16:31   ` Drew Adams
2006-11-02 14:00 martin rudalics
     [not found] <mailman.51.1162452995.2155.help-gnu-emacs@gnu.org>
2006-11-02  9:42 ` Mathias Dahl
  -- strict thread matches above, loose matches on Subject: below --
2006-11-02  7:36 martin rudalics
2006-10-31 16:59 William Case
2006-11-03 19:30 ` William Case

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=u3b933xqt.fsf@gmail.com \
    --to=brakjoller@gmail.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.
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).