zsh-users
 help / color / mirror / code / Atom feed
From: Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>
To: zsh-users@zsh.org
Subject: Re: segfault in mkundoent when completing
Date: Mon, 26 Oct 2015 09:18:50 +0200	[thread overview]
Message-ID: <87fv0ym71h.fsf@djcbsoftware.nl> (raw)
In-Reply-To: <151025180706.ZM30568@torch.brasslantern.com>


On Monday Oct 26 2015, Bart Schaefer wrote:

> On Oct 25,  9:15pm, Dirk-Jan C. Binnema wrote:
> }
> } It seems to happen in all directories; I suspect it's something specific
> } to my configuration (when not using my ~/.zshrc, there's no crash),
> } though I don't think there's anything special there (and it worked fine
> } for years before the mentioned commit).
>
> Whether it "worked fine for years before" or not, probably the only way
> anyone else will be able to track this down is if you first narrow down
> the setting(s) from your .zshrc that must be in place in order to trigger
> the error.

Hmmm, it seems some kind of interaction between a few different things;
but I was amble to reproduce it with this ~/.zshrc (using the external
highlighting package):

--8<---------------cut here---------------start------------->8---
setopt allexport
autoload -U compinit
compinit
source ~/Sources/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh
--8<---------------cut here---------------end--------------->8---

Kind regards,
Dirk.

-- 
Dirk-Jan C. Binnema                  Helsinki, Finland
e:djcb@djcbsoftware.nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C


       reply	other threads:[~2015-10-26  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874mhfe8ng.fsf@djcbsoftware.nl>
     [not found] ` <151025095136.ZM29675@torch.brasslantern.com>
     [not found]   ` <87y4eqahet.fsf@djcbsoftware.nl>
     [not found]     ` <151025180706.ZM30568@torch.brasslantern.com>
2015-10-26  7:18       ` Dirk-Jan C. Binnema [this message]
2015-10-26  9:49         ` 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=87fv0ym71h.fsf@djcbsoftware.nl \
    --to=djcb@djcbsoftware.nl \
    --cc=zsh-users@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).