From: "Philip K." <philipk@posteo.net>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making ielm behave like a shell (getting to previous commands using the up-arrow key)
Date: Fri, 18 Dec 2020 11:20:58 +0100 [thread overview]
Message-ID: <87h7ojh0tx.fsf@posteo.net> (raw)
In-Reply-To: <87im90264s.fsf@fastmail.fm> (Joost Kremers's message of "Thu, 17 Dec 2020 09:22:34 +0100")
Joost Kremers <joostkremers@fastmail.fm> writes:
> On Thu, Dec 17 2020, Michael Heerdegen wrote:
>> steve-humphreys@gmx.com writes:
>>
>>> I have started using ielm and would be useful for it to behave like a
>>> terminal That is enabling history on ielm to view all the previous
>>> executed commands using the Up Arrow Key.
>>
>> You know that M-p does that?
>
> Also Ctrl-up. :-)
C-c C-p to jump back to the last prompt, that can be modified and
re-evaluated is aoso helpful.
>> FWIW, personally I'm quite happy that I can "walk around" with the arrow
>> keys in ielm buffers.
>
> Indeed.
--
Philip K.
prev parent reply other threads:[~2020-12-18 10:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 3:02 Making ielm behave like a shell (getting to previous commands using the up-arrow key) steve-humphreys
2020-12-17 3:34 ` Okam
2020-12-17 4:27 ` Michael Heerdegen
2020-12-17 4:44 ` steve-humphreys
2020-12-17 5:02 ` Michael Heerdegen
2020-12-17 5:17 ` steve-humphreys
2020-12-17 9:06 ` Jean Louis
2020-12-17 9:13 ` Jean Louis
2020-12-17 22:29 ` Michael Heerdegen
2020-12-18 5:05 ` Jean Louis
2020-12-18 9:01 ` Michael Heerdegen
2020-12-18 11:19 ` Jean Louis
2020-12-18 17:14 ` Drew Adams
2020-12-18 18:36 ` Jean Louis
2020-12-18 19:11 ` Drew Adams
2020-12-18 19:53 ` Jean Louis
2020-12-18 21:15 ` Drew Adams
2020-12-19 2:07 ` Michael Heerdegen
2020-12-19 2:51 ` Drew Adams
2020-12-18 11:28 ` Jean Louis
2020-12-19 1:55 ` Michael Heerdegen
2020-12-19 2:45 ` Drew Adams
2020-12-19 1:57 ` Michael Heerdegen
2020-12-17 8:22 ` Joost Kremers
2020-12-18 10:20 ` Philip K. [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
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=87h7ojh0tx.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).