unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Need an enabler for a bad habit.
Date: Wed, 01 Nov 2006 17:45:57 +0100	[thread overview]
Message-ID: <85ac3b869m.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.19.1162399165.2155.help-gnu-emacs@gnu.org

William Case <billlinux@rogers.com> writes:

> On Wed, 2006-01-11 at 16:05 +0100, Mathias Dahl wrote:
>
>> So, what you want is to be able to click in the echo area (the area
>> below the mode line) to get the "M-x prompt" (without needing to type
>> M-x), is it?
>
> 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.
>
> If you open a virtual terminal and type a couple of shell commands, you
> can see what I mean.
>
> I want to reconfirm, I am not advocating that others may want this
> or that it is something emacs should automatically do.  In fact, it
> is a waste of time and clicks and/or keystrokes.  However,
> intuitively, as in a command line on a terminal, I like to see that
> I have moved on to the next command by seeing the cursor at the
> beginning of a cleared command line (the command-to-be, so to
> speak), that I have a second or two to think about what exactly I am
> going to type next; and what I type next will be a command of some
> sort.
>
> It is a habit that comes from 30 years of being a computer user.

I suggest you stay with ed or ex.  A vim-based ex might come close to
your expectations of what an editor is supposed to do.

Most other people nowadays have gotten used to visual rather than
command-line centric editors.

If that is different with you, there is no point in picking an editor
that works with different user interface principles.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2006-11-01 16:45 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 [this message]
2006-11-01 17:03           ` Mathias Dahl
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=85ac3b869m.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    /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).