zsh-workers
 help / color / mirror / code / Atom feed
From: Nir Friedman <quicknir@gmail.com>
To: zsh-workers@zsh.org
Subject: Bug Report: Interactive Mode Glitches
Date: Fri, 23 Oct 2015 12:15:50 -0400	[thread overview]
Message-ID: <CA+cBnHDFZPK4d3hRYGZ_5o=1mep3D5iq67Ppsy1N91B9Pqd9vw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

I relatively often see bugs in zsh's interactive mode. I can't duplicate
them frequently, but the trigger is nearly always either: 1) hitting
backspace when already in interactive mode and incremental matching is
happening, or 2) hitting Ctrl-C in an attempt to exit from interactive mode.

Here are some relevant settings:

zstyle ':completion:*' menu select=0 interactive
zstyle ':completion:*' insert-unambiguous true

#
# Options
#

setopt COMPLETE_IN_WORD    # Complete from both ends of a word.
setopt ALWAYS_TO_END       # Move cursor to the end of a completed word.
setopt PATH_DIRS           # Perform path search even on command names with
slashes.
setopt AUTO_MENU           # Show completion menu on a successive tab press.
unsetopt AUTO_LIST           # Automatically list choices on ambiguous
completion. Changed by NF
setopt AUTO_PARAM_SLASH    # If completed parameter is a directory, add a
trailing slash.
unsetopt MENU_COMPLETE     # Do not autoselect the first completion entry.
unsetopt FLOW_CONTROL      # Disable start/stop characters in shell editor.

LISTMAX=0

I'm happy to try to provide more information, if someone can tell me how
(perhaps run zsh with some kind of debug flag, and look in there the next
time a crash happens?).

Cheers,

Nir

             reply	other threads:[~2015-10-23 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 16:15 Nir Friedman [this message]
2015-10-24 20:37 ` Daniel Shahaf
2015-10-24 20:45   ` Nir Friedman
2015-10-24 20:56     ` Daniel Shahaf
2015-10-24 21:04       ` Nir Friedman
2015-12-02  6:02         ` Nir Friedman
2015-12-02  8:39           ` Bart Schaefer
2015-12-02  9:24           ` Peter Stephenson
2015-10-25 16:07     ` Jun T.

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='CA+cBnHDFZPK4d3hRYGZ_5o=1mep3D5iq67Ppsy1N91B9Pqd9vw@mail.gmail.com' \
    --to=quicknir@gmail.com \
    --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).