zsh-workers
 help / color / mirror / code / Atom feed
From: Ollie Ford <me@ojford.com>
To: zsh-workers@zsh.org
Subject: BUG: `ls\<enter><enter>` seg fault
Date: Thu, 12 Nov 2015 23:39:36 +0000	[thread overview]
Message-ID: <CAMVOL1O+Tgcbr6x6KOW=PKJzzSgaBKUNKw1wyvxN3jf7z7JVCw@mail.gmail.com> (raw)

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

I am not a subscriber.

In zsh --version:
zsh 5.0.8 (x86_64-apple-darwin15.0)

Iff there is an alias set on ls, then entering `ls\` followed by twice the
return key (i.e. the line break was accidental; the user just meant `ls`)
causes a segmentation fault.

In terminal, this looks likes like a Ctrl-d logout:
(`alias ls=ls -GFh` in zshrc)
% ls\
>
[Process completed]

In a fresh zsh -f we see why:
% alias ls=ls
% ls\
>
zsh: segmentation fault  zsh -f

Regards,
Ollie

             reply	other threads:[~2015-11-12 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 23:39 Ollie Ford [this message]
2015-11-13  1:11 ` Bart Schaefer

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='CAMVOL1O+Tgcbr6x6KOW=PKJzzSgaBKUNKw1wyvxN3jf7z7JVCw@mail.gmail.com' \
    --to=me@ojford.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).