zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: trouble with debugging binary
Date: Fri, 21 Nov 2014 20:45:45 -0800	[thread overview]
Message-ID: <141121204545.ZM11623@torch.brasslantern.com> (raw)
In-Reply-To: <546F7646.7080108@eastlink.ca>

On Nov 21,  9:28am, Ray Andrews wrote:
} Subject: trouble with debugging binary
}
} On 11/20/2014 10:23 PM, Bart Schaefer wrote:
} >
} > Where were they before you deleted them?
} All in
} /usr/share/zsh/functions
} /usr/share/zsh/functions/Completions
} 
} I'll restore  them. No doubt they do something important,
} but I'm not noticing their absence right now.

No, actually, they're entirely unimportant; they're just the compiled
(into zsh's internal word code) versions of the functions that share
their base name.  In some cases it can be faster to load a pre-compiled
function file, so zsh has the "zcompile" builtin for creating them.
But the chances you'd notice the difference from them not being there,
are small.

} Is there some sort of global map of everything that zsh adds to
} one's system? These *.zwc files, I had no idea they were there
} and I have no idea what they do.

As I said, they're NOT something that zsh added to the system.  It must
be that the package for your OS's stock zsh binary included them.

} I just rebuild without  " --enable-zsh-debug " and all is well.

Sadly, rebuilding without --enable-zsh-debug is sort of like removing
the batteries from your smoke detector.  There may still be a fire, but
you just aren't hearing about it any more.


  reply	other threads:[~2014-11-22  4:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 21:36 PATCH: key bindings, fixes, docs, tests for vi stuff Oliver Kiddle
2014-11-18  8:04 ` Jun T.
2014-11-19  8:48   ` Oliver Kiddle
2014-11-19 15:35     ` Ray Andrews
2014-11-21  0:01   ` Oliver Kiddle
2014-11-21  0:49     ` Bart Schaefer
2014-11-21  1:10       ` Ray Andrews
2014-11-21  5:53         ` Bart Schaefer
2014-11-21 10:35       ` Oliver Kiddle
2014-11-22  6:59         ` Bart Schaefer
2014-12-12 16:47           ` Oliver Kiddle
2014-11-21  1:15     ` Ray Andrews
2014-11-21  2:20       ` Mikael Magnusson
2014-11-21  2:38         ` Ray Andrews
2014-11-21  6:23           ` Bart Schaefer
2014-11-21 17:28             ` trouble with debugging binary Ray Andrews
2014-11-22  4:45               ` Bart Schaefer [this message]
2014-11-22  5:27                 ` Ray Andrews
2014-11-22  5:43                 ` Bart Schaefer
2014-11-22 16:49                   ` Ray Andrews
2014-11-22 22:35                     ` Bart Schaefer
2014-11-23  7:58                     ` Lawrence Velázquez
2014-11-23 16:22                       ` Ray Andrews
2014-11-23 18:12                         ` Mikael Magnusson
2014-11-23 18:42                           ` Ray Andrews
2014-11-23 19:01                             ` Mikael Magnusson
2014-11-23 22:30                               ` Ray Andrews
2014-11-21 15:20     ` PATCH: key bindings, fixes, docs, tests for vi stuff 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=141121204545.ZM11623@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).