Re: [Help-bash] use edit-and-execute-command instead the secondary prompt

[Greg Wooledge]

On Fri, May 12, 2017 at 04:10:09PM +0200, D630 wrote:
> On 17-05-12_15_37, Pierre Gaston wrote:
> > On Fri, May 12, 2017 at 3:28 PM, Eduardo Bustamante <address@hidden>
> > wrote:
> >
> > > On Fri, May 12, 2017 at 3:45 AM, D630 <address@hidden> wrote:
> > > > How about an option to force bash into invoking 
> > > > edit-and-execute-command,
> > > > when
> > > > bash wants to use the secondary prompt / needs a second line to complete
> > > the
> > > > command?
> > >
> > > Why would you need an option to force it? If you're using the emacs
> > > mode, just hit Ctrl-x Ctrl-e when you get the secondary prompt.
> > > That'll run the edit-and-execute-command function on the partial
> > > input.
> > >
> > >
> > I guess it would be a kind of  automagic feature, as soon as I need to
> > enter something that doesn't fit on one line, fire up my editor to help me.
> 
> Right. Something like:
> 
> $ foo | [ENTER]    # --> edit-and-execute-command is invoked

You mean *automatically*?

And then what?  What do you want to happen after that?  According to
Chet, today, invoking edit-and-execute-command (automatically or not)
when on the second line of a multi-line command will NOT allow you to
edit a multi-line command safely.  And apparently this is not going to
change, because it's "meant to work like that".

https://lists.gnu.org/archive/html/bug-bash/2017-05/msg00113.html

You need to hit ESC v (or whatever) while you are on the FIRST line,
apparently.