git completion horribly slow in kernel tree Zsh Mailing List Archive Messages sorted by: Reverse Date , Date

References : git completion horribly slow in kernel tree From: Jörg Sommer Re: git completion horribly slow in kernel

Re: git completion horribly slow in kernel tree Zsh Mailing List Archive Messages sorted by: Reverse Date , Date

References : git completion horribly slow in kernel tree From: Jörg Sommer Re: git completion horribly slow in kernel

Re: git completion horribly slow in kernel tree From: Clint Adams References : git completion horribly slow in kernel

References : git completion horribly slow in kernel tree From: Jörg Sommer Re: git completion horribly slow in kernel

References : git completion horribly slow in kernel tree From: Jörg Sommer Re: git completion horribly slow in kernel

completion horribly slow in kernel tree Clint Adams 2008/01/23 Re: git completion horribly slow in kernel

Re: Unicode problem Re: git completion horribly slow in kernel tree Re: git completion horribly slow in kernel

code. First, the calculation of "up" in listmatches() can go horribly wrong in some

w->u.fnnam); You'd expect use of shf to fall over horribly if there was really

bash did, and it is possible to write working scripts without using horribly convoluted constructs. If you

Using =+ as a special token would break all sorts of things fairly horribly. integer i=+3 i

And I've never found printing with it to be particularly successful either---horribly slow, horribly big PostScript

validate Re: zsh 5.0.8.-test-3 Hungarian mirror listed on http://www.zsh.org/ horribly out of date

dev/null; do done > > ^C > > pride% echo yes > > <- nothing. stdout has disappeared. > > Help Actually, it's horribly obvious. When errflag is

only > needed locally. (Robustly except for the fact the shell crashes > horribly if it runs out

the free documentation. "Linux Programming Tools" has a chapter on zsh, but it's horribly limited. It doesn't

Bart privately by mistake.) execute-named-command as well as the isearch commands have horribly incestuous ways of

8) bound to a func-key to restore sanity after X11 horribly hexes things. And

On the other hand, there's a danger that zsh might be horribly slow as a

13am, Peter Stephenson wrote: > } > } execute-named-command as well as the isearch commands have horribly > } incestuous ways of

split-chars : Given how brutal this is, I can well imagine there are cases this fails horribly.  It is at least

do the trick; objections? Grotesque nested expansion cases that are going to go horribly awry? diff --git a

of a fully-customizable completion system, but every time i turn it on, i get horribly confused by the

to have zero impact there: I'm still unable to interrupt the horribly slow expansion using ctrl

cmd does not export it at all. something strange here. > There's something that had me horribly confused (though it's

turn up first time and sorry if Yahoo re-wraps the text horribly. Bart Schaefer wrote: > I

shell calls are similar). The only simple answer (there are plenty of horribly complex answers --- three personal

13am, Peter Stephenson wrote: } } execute-named-command as well as the isearch commands have horribly } incestuous ways of

convesion that way, but for some reason that now escapes me (but could become horribly clear again) I thought

having a second shell running commands in the background might go horribly wrong for the

only needed locally. (Robustly except for the fact the shell crashes horribly if it runs out

zsh scripting etc. > "Linux Programming Tools" has a chapter on zsh, but it's horribly > limited. It doesn't

could of course move it under Unix/Command (and since ps(1) is horribly platform specific we'd

AC) or using battery (DC). For example (hopefully Mail.app doesn't wrap it horribly... --INSERT-- :zsh-4.2

to } have zero impact there: I'm still unable to interrupt the horribly } slow expansion using ctrl

modify the string in place. > > > > I think this fixes it, but it's horribly complicated around there. > > Hmm

modify the string in place. > > I think this fixes it, but it's horribly complicated around there. Hmm

part of completion + * and so everything to do with it is horribly complicated. + */ + case ZLE_CMD_READ: + { + char

sections to get the test to exit sooner if something goes horribly wrong. However, there's

modify the string in place. I think this fixes it, but it's horribly complicated around there. Index

above and output them separately without updating the display but that's horribly non portable and

fix, and I think it's good enough. There's something that had me horribly confused (though it's

part of completion + * and so everything to do with it is horribly complicated. + */ + case ZLE_CMD_READ: + { + char

case is simple — more complicated expressions with "test" or "[", as opposed to "[[", can go horribly wrong, but two arguments

send. I'd like some indication there are non-standard terminals that this doesn't wreck horribly before committing it. Index

the CLI stuff--most of it is hoary with age and horribly unfriendly. That's all

a device called "dev" in the general case, that will screw up parsing horribly. > And I

none. (For zsh-workers only.) By the way, I'm sure this is horribly incomplete at best --- and