zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Frederick Eaton <frederik@ofb.net>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] insert-last-word gets stuck at comments
Date: Mon, 26 Jul 2021 15:50:17 -0700	[thread overview]
Message-ID: <CAH+w=7Yr-zEQ2SFSWV3TqRp4WkkGXC=LbReBMka88=bb2U7z1w@mail.gmail.com> (raw)
In-Reply-To: <20210726070654.v33wzoiwpqibwlas@localhost>

On Mon, Jul 26, 2021 at 12:07 AM Frederick Eaton <frederik@ofb.net> wrote:
>
> This may be a somewhat minor bug, but I think that when
> interactive_comments is set, the 'insert-last-word' widget gets stuck
> on lines that are fully commented:

I'm able to reproduce this.  A fully-commented line has an event
number but contains no words; e.g., it's also an "error" to attempt to
refer to event number 3 e.g. with !3 in the example:

>      $ zsh -f -i
>      % setopt interactive_comments
>      % echo hi #comment
>      hi
>      % # blah blah
>      % echo bye #comment
>      bye
>      % echo foo
>      foo
>      % echo <Esc>.<Esc>.<Esc>.

At this point:

% !3
zsh: no such word in event

Even though !2 and !4 work as expected.  So insert-last-word gets as
far as event 3 and then gets the no-such-word error, which interrupts
it.

A workaround is to enable smart-insert-last-word.


  reply	other threads:[~2021-07-26 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26  7:06 Frederick Eaton
2021-07-26 22:50 ` Bart Schaefer [this message]
2021-07-27  5:52   ` Frederick Eaton
2021-07-27 20:19     ` Bart Schaefer
2021-07-28  1:36       ` Bart Schaefer
2021-07-28  9:06         ` Peter Stephenson
2021-07-28 15:40           ` Bart Schaefer
2021-07-29  8:14             ` Peter Stephenson

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='CAH+w=7Yr-zEQ2SFSWV3TqRp4WkkGXC=LbReBMka88=bb2U7z1w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=frederik@ofb.net \
    --cc=zsh-workers@zsh.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. 
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).