zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues
Date: Thu, 13 Apr 2000 14:46:06 +0200 (MET DST)	[thread overview]
Message-ID: <200004131246.OAA14948@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 12 Apr 2000 06:14:57 +0000


Bart Schaefer wrote:

> Some of these may actually have been resolved and I just forgot/missed it.
> Also, these are only issues raised in messages I sent myself.
> 
> ...
> 10187		combining multiple zstyle commands into one

I have the feeling I should have an opinion about this one but it
appears that I haven't. If my setup is anything to go by (58 calls to
zstyle ;-), it *would* simplify some of them, but I normally add new
ones with \M-w\C-y, so...
I offer to write it when you folks decide that we want it. I don't
think I'll offer to make `zstyle -L' print them in this form, though
(but I haven't really thought about how difficult that would be).

> ...
> 10080		move compctl support functions out of Misc/

Maybe together with the other function cleanup in the completion
system.

> 10071		xtrace behavior of `.' and `source'

I still find our behaviour much more consistent and it gives us both
possibilities. So if at all, I think we should use a option for it
(yet another `emulate ksh' thing).

> 10005		bogus "no such job" / STAT_NOPRINT

Sniff.

> 9996		vared keymap

A very simple way would be to just allow users to give a keymap via an 
option that would be used as a `local' keymap the way menu-selection
does it, i.e. all functions but undefined-key in that map override the
definitions in the normally used keymap.
This is the place where I wished Anthony would have found the time to
give us the code for the stuff he told us about in 6938.

> ...
> 9778		hanging on loops with lots of output

Oops. I had forgotten about this one. Does it still happen?

> ...
> 9062		suspending `.' / `source'

An option? Tested only after the init scripts have been read?

> ...
> 8698		bad node type in freenode (related to 9095?)

I sent a patch for this in 8721 (at least it solved it for me). And
Peter had a look at and a patch for it when he came back. And since
then the whole node-stuff has been removed (the nodes in question were
the ones used to store executable code).

> 8619		locales and globbing

The last reply to this was 8625 -- and I still think this should be
done with a glob flag or an option and a glob flag. Or something.


And there is also still your FPATH-in-the-environment-and-then-that-if
thing...

Bye
 Sven


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


             reply	other threads:[~2000-04-13 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-13 12:46 Sven Wischnowsky [this message]
2000-04-13 15:55 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-04-14  8:18 Sven Wischnowsky
2000-04-14 14:57 ` Bart Schaefer
2000-04-12  6:14 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

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=200004131246.OAA14948@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).