zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Things which need doing before 3.1.6
Date: Wed, 9 Jun 1999 09:50:00 +0200 (MET DST)	[thread overview]
Message-ID: <199906090750.JAA21038@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Sat, 05 Jun 1999 18:20:14 +0200


Peter Stephenson wrote:

>   Various issues to do with parameter and memory efficiency which I've
>     been meaning to post about but still haven't

I'd like to hear about those...

Anyway, may I mention the things on my todo list here? I don't want to 
say that these need to be addressed before the next release, though
(in most cases this should be clear).

We had some reports about SEGVs which I was never able to reproduce:

- Bart (5375): he had sourced compinit several times and then tried
  completion with a test-function. The completion was in quotes and
  this has changed a lot (and, of course, the other completion code
  has changed, too). I hope that the fact that we never heard about
  it again means that we don't have to worry any more.

- Geoff (5784, 5787): completion after ~/src/she<TAB> in command
  position. Bart couldn't reproduce it at that time, either. Again, we 
  didn't hear more about it.

Other things:

- The globbing/completion problem on NextStep reported by Timothy
  (6333). I still don't have access to a NextStep box so I can't
  investigate any further. The problem was that globbing didn't find
  some files.

- When compiling with dynamic loadable modules for Digital Unix 4.0 I
  still need to do:

  DLLD=gcc LDFLAGS=-g -rpath foo' ./configure ...

  where `foo' is the directory where the libzsh* lives.
  I've already asked (twice if I remember correctly) if this is due to 
  the installation on this system here or if this is a general problem
  with Digital Unix -- but got no replies.

- Bart suggested that we start thinking about cleaning up the new
  style completion stuff (the C part of it, like options to
  comp{add,gen} and the like), see 6159, 6163, 6178.
  There is also still the suggestion to support long options...

- Then there is my suggestions for a way to directly access the
  matches that were added (6117), which I haven't thought more about
  because I haven't missed it yet (and nobody else seems to miss this).

- We might want to add more examples for new completion, probably some 
  examples for zle widgets (to get people started). We might also
  think about modifying the old compctl-examples file to make use of
  the new options (using grouping, match specs where appropriate,
  things like that). I'm pretty sure that I won't do that, though,
  since I'm using only the new completion stuff nowadays.


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-06-09  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-09  7:50 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-06-05 16:20 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=199906090750.JAA21038@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).