From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug report: zsh crashes when expanding long command from history.
Date: Wed, 21 Oct 2015 15:16:00 -0700 [thread overview]
Message-ID: <151021151600.ZM5429@torch.brasslantern.com> (raw)
In-Reply-To: <CAH+w=7amJUgg1Sh72nZcHA8SighELehr5ctbizXfeuW+jXA2pw@mail.gmail.com>
On Oct 21, 3:04pm, Bart Schaefer wrote:
}
} I suppose this might still break on a single word more than 64k
} characters long, but it'll break by returning the substring of the
} command line rather than by crashing.
That should say "wrong substring".
} (This diff might get garbled, I'm not using my regular email client.)
Yep, it did. Sorry.
prev parent reply other threads:[~2015-10-21 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 10:47 Dorian Haglund
2015-10-20 17:30 ` Bart Schaefer
2015-10-21 22:04 ` Bart Schaefer
2015-10-21 22:16 ` Bart Schaefer [this message]
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=151021151600.ZM5429@torch.brasslantern.com \
--to=schaefer@brasslantern.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).