From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Open bugs and questions?
Date: Tue, 1 Aug 2000 15:09:53 +0000 [thread overview]
Message-ID: <1000801150953.ZM30770@candle.brasslantern.com> (raw)
In-Reply-To: <200008010900.LAA06432@beta.informatik.hu-berlin.de>
On Aug 1, 11:00am, Sven Wischnowsky wrote:
}
} Semester-holiday has definitely begun now. So, does anyone have a list
} of unfixed bugs and open questions? Bart?
I haven't updated the one I made just before 3.1.9, but I don't think
everything on that last list got done, either.
} 12344, 12350, 12382
} Make `_arguments --' use the short options, too?
I have a patch for this first part, but:
} And make it prefer a user-supplied description if there is one (and
} a automatically found one).
I don't have a patch for that second part.
} 12225
} The return value of _arguments with `->state' actions doesn't tell
} if options were completed.
I meant to reply to that message. I've never been happy with using the
exit status to indicate that an ->state action was taken. The only
simple test on exit status is true/false; for anything else, you have
to compare against $? -- which means you might as well be testing some
other parameter instead, e.g. [[ -n "$state" ]] which is what most of
the functions that use ->state already do anyway.
So I suggest simply dumping the 300 exit status; zero means that matches
were added, anything else means that no matches were added, and if you
want to use states you test the $state array directly.
} 12054, 12071
} There is no way to handle ^D at the beginning of the line with a
} widget, because the zle main loop deals with it directly.
It *is* possible to handle ^D at beginning of line: stty eof undef
permits it. This is equivalent to having to turn off flow control in
order to use ^S and ^Q in keybindings.
So maybe the right answer is that `setopt ignoreeof' should affect ZLE
the same way that `setopt noflowcontrol' does. An actual zero-byte
read would still be handled as it currently is; only ^D in column zero
would be different (actually invoke the ^D binding rather than print
"zsh: use 'logout' to logout.").
THEN we could change delete-char-or-list to print that warning when there
are no characters in the editor buffer, et voila: the default behavior is
exactly as now.
} ..., 11973
} Completion after `{a,b}'. Urgh. I don't want to think about this
Then don't.
} 11399, 11400, 11413, 11428
} Context names for styles not used by the completion system
} itself. More specifically, for function that call the completion
} system, but have other styles used directly. And where to document
} them.
I've been toying with the idea of adding a "user contributions" chapter
to the manual and throwing into it: incremental-complete-word, zed, the
prompt themes, predict-on, zrecompile, nslookup, etc. With appropriate
sections, of course.
} 11465
} Interrupting builtins. E.g. with `cmd1 | builtin ; cmd2' a ^C should
} keep cmd2 from being run.
There's also 11468. I wish I had a suggestion.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-08-01 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 9:00 Sven Wischnowsky
2000-08-01 9:19 ` Peter Stephenson
2000-08-01 9:46 ` Andrej Borsenkow
2000-08-01 15:09 ` Bart Schaefer [this message]
2000-08-01 10:58 Sven Wischnowsky
2000-08-02 12:08 Sven Wischnowsky
2000-08-02 16:24 ` Bart Schaefer
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=1000801150953.ZM30770@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).