Martin Kopischke
kopischke

Jul 18, 2016
Jul 18, 2016
Jul 18, 2016
Jul 17, 2016
Jul 13, 2016
kopischke commented on issue kopischke/vim-stay#30
@kopischke

Thanks for reporting this: I can see where the issue is and will fix as soon as I have some time to get back to stay. If you need a quick fix no, y…

Jul 10, 2016
@kopischke

@ridiculousfish that would certainly help: as far as I’m concerned, the more limited and explicit the scoping of this kind of feature, the better.

Jul 10, 2016
@kopischke

IMO, the correct way to think about strict mode is not that things terminate on error, but that ignored error codes are bubbled up until something…

Jul 10, 2016
@kopischke

Having had to contend with side effects of rbenv’s decision to go “strict” I can only deem idiotic [1, 2], I must say I am less than sold on it. I …

Jul 10, 2016
Jul 8, 2016
Jul 4, 2016
Jul 4, 2016
Jul 1, 2016
Jun 29, 2016
Jun 29, 2016
kopischke commented on pull request fish-shell/fish-shell#3182
@kopischke

s/serach/search (this line and previous)

Jun 28, 2016
Jun 28, 2016
Jun 27, 2016
Jun 27, 2016
Jun 21, 2016
Jun 20, 2016
Jun 14, 2016
Jun 8, 2016
@kopischke

@floam thanks for pointing out the grep behaviour, you are right to reopen this. I’ve changed the issue title to better reflect the question at hand.

Jun 7, 2016
@kopischke

@msteed so was I, though I have to admit that thinking this through (now that I have let off my steam) it is correct: after all, one would expect /o+/

Jun 7, 2016
@kopischke
string builtin mishandles “*” quantifier
Jun 7, 2016
@kopischke

I just tested against actual regex engines in JavaScript (WebKit ES6 subset), Ruby (2.3), Python (2.7) and Perl (5.18) and they behave as described…

Jun 6, 2016