zsh-users
 help / color / mirror / code / Atom feed
From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: phil@fifi.org
Cc: zsh-users@sunsite.dk
Subject: Re: ESC-Question
Date: Mon, 14 Mar 2005 17:58:27 +0100 (CET)	[thread overview]
Message-ID: <20050314.175827.41633885.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <871xaiu0w7.fsf@ceramic.fifi.org>

From: Philippe Troin <phil@fifi.org>
Subject: Re: ESC-Question
Date: 13 Mar 2005 23:44:56 -0800

Hi Phil !

 Thanks a lot for the hint...gives me a whole lotta more of space (new
 lines) for nice zshish code ! :)
 
 Sometimes (often!) just the simple things are makeing life so much
 easier ! ;O)))))))

 Keep zshing!
 Meino

 PS: Just cause I am a little curious... :)
     Under Emacs each keycode is bound to a named function like
	 forward-search-regexp and such...what is the corresponding
	 function in zsh? insert-line ? Or what is its name ?

> Meino Christian Cramer <Meino.Cramer@gmx.de> writes:
> 
> >  Suppose I am builing up a short """""script""""" on the commandline:
> >  A simple loop over filenames for example.
> > 
> >  After first run of the script I want to add another line to that
> >  script.
> > 
> >  Scrolling back in history gives me the whole script nicely printed in
> >  several lines (NOT on a loooooong one-liner! What a nice zshish
> >  feature!).
> > 
> >  With EMACS-related keys I easily can step through the lines...BUT how
> >  can I open a NEW line? My workaround is a way really hurtung an
> >  EMACS-freak like me (at this point of the text of my mail there is a
> >  BIG HUGH SMILEY!):
> > 
> >  I hit ALT-x (execute) and enter the command 
> > 
> >    vi-open-line-above (...-below)
> >
> >  because the simple <RETURN> at the and of the line will execute the
> >  script again....
> > 
> >  Is there a Emacs-keybinding or Emacs-related command to open a line ?
> 
>   C-v C-j
> 
> Or substitute whichever character is your tty's lnext char (as can
> been seen from stty -a).
> 
> Alternately, M-Enter always creates a new line without submitting the
> input for processing.
> 
> Phil.
> 


  reply	other threads:[~2005-03-14 16:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 18:42 Ex-bash script for optimisation Meino Christian Cramer
2005-03-11  5:14 ` Bart Schaefer
2005-03-11 18:37   ` TAB-expansion problems Meino Christian Cramer
2005-03-12  9:15     ` Tim Kruse
2005-03-13  4:50     ` Bart Schaefer
2005-03-13  8:54       ` Meino Christian Cramer
2005-03-13 17:21         ` Bart Schaefer
2005-03-14  4:37           ` ESC-Question Meino Christian Cramer
2005-03-14  7:44             ` ESC-Question Philippe Troin
2005-03-14 16:58               ` Meino Christian Cramer [this message]
2005-03-14 17:09                 ` ESC-Question Peter Stephenson
2005-03-14 17:22                   ` ESC-Question Meino Christian Cramer
2005-03-14 18:18                   ` ESC-Question Philippe Troin
2005-03-14 10:01             ` ESC-Question Sami Samhuri

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=20050314.175827.41633885.Meino.Cramer@gmx.de \
    --to=meino.cramer@gmx.de \
    --cc=phil@fifi.org \
    --cc=zsh-users@sunsite.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).