zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues (update)
Date: Mon, 1 May 2000 05:21:27 +0000	[thread overview]
Message-ID: <1000501052127.ZM8590@candle.brasslantern.com> (raw)
In-Reply-To: <1000412061457.ZM11808@candle.brasslantern.com>

What I believe to be the status on these issues.  New ones:

11036		read -q
11030		_message
11023		_complete_help and matcher-list
11022		print -s (during completion)
11018		_find

Yeah, I know, it's not fair to list things that came up over the weekend.
Too bad, I want to collect them together somewhere.  (I suppose I could
file them as bugs on sourceforge ... do people find that bug tracker to
be worthwhile?)

The following have been fixed or acted upon, or were improperly listed:

} 10187		combining multiple zstyle commands into one
} 10154		$param:x and the FAQ
} 8698		bad node type in freenode (related to 9095?)
} 8619		locales and globbing
} Document the kshautoload problem with the completion system and how one
} works around it with zcompile.

The following are going to be left as they are in 3.1.7-pre-2, so that
counts as a resolution:

} users/2973	clear to end of display
} 10403		<(...) doesn't really create a FIFO
	(This one got some documentation at least.  I still think it
	could be fixed, but probably not entirely within getproc(),
	due to the race condition PWS noted.)
} 10071		xtrace behavior of `.' and `source'
} 10005		bogus "no such job" / STAT_NOPRINT
	(I guess that's what Sven's "Sniff." meant.)
} 9996		vared keymap
} 9945		somebody check my work ...
} 9062		suspending `.' / `source'

The following will be dealt with for 4.0, along with other reorgs:

} 10080		move compctl support functions out of Misc/
} 9962		renumbering comptest

The following have been discussed a bit further, but no conclusion yet:

} 10346		rebuilding zshpaths.h
} 9778		hanging on loops with lots of output
} 8780		format of error messages

And last, these are still entirely un-addressed:

} 10169		%(l.t.f) and line wrapping in prompts
} users/2979	assigning a string containing `:' to $path
} 9982		comptest (lack of) verbosity
} 9762		nameddir assoc elements
} 9702		configure switch for mymods.conf (cf. 9727)
} 9575		export arrays like ksh
} 9095		getopts is broken
} 9000		parameter formatting / ksh export (cf. 8674)
} 8861		posix module
} 8758		locales and math (cf. 8792)
} 8378		configure --zsh-mem-debug

Of those, I think 9095 is the only really crucial one.  The others might
warrant mention on the BUGS list or some such.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~2000-05-01  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-12  6:14 List of unresolved issues Bart Schaefer
2000-04-12 15:56 ` Andrej Borsenkow
2000-04-12 20:55 ` Peter Stephenson
2000-04-13  0:26   ` Bart Schaefer
2000-04-13  8:56     ` Peter Stephenson
2000-04-13 14:10       ` PATCH: local exports Peter Stephenson
2000-04-13 15:42         ` Bart Schaefer
2000-04-13 17:54           ` PATCH: " Peter Stephenson
2000-05-01  5:21 ` Bart Schaefer [this message]
2000-05-01  9:09   ` List of unresolved issues (update) Adam Spiers
2000-05-02  9:50   ` 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=1000501052127.ZM8590@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).