Wilfred

8 ms·

31.
by Wilfred 5y ago
Ooh, I'd not seen this and I've seen a bunch of diff tools at this point! Thanks for sharing.
32.
by Wilfred 5y ago
Yep, that's a fair description. Note that I'm not providing a merge algorithm, just a pretty way of viewing changes. I did look at modelling moves in an earlier prototype, but it's incredibly hard to display the result in a c
33.
by Wilfred 5y ago
Yeah, so it's basically a lexer with an extremely simplistic parser. Compiler parsers aren't a great fit for difftastic. They discard comments, they may not give you output if there are syntax errors, and they're usually tied
34.
by Wilfred 5y ago
Wow, thank you for the pointer! I've added it to https://github.com/Wilfred/difftastic/wiki/Structural-Diffs as I'm trying to understand the other solutions in this space. Difftastic does not create
35.
by Wilfred 5y ago
Yep! There's a lot of .unwrap() and .expect() in the codebase, so it panics. Since it's Rust, you get a line number and an error message rather than a segfault. I will tidy it up at some point, but I spend too much time throwing a
36.
by Wilfred 5y ago
Definitely! I still look at diffs in the terminal pretty often, but all my code reviews are in rendered HTML. That said, there needs to be a credible tool before review tools can adopt it! GitHub does a line-based diff with word-based highl
37.
by Wilfred 5y ago
Thanks, this is good advice. There are some super featureful diff tools out there. For example, https://github.com/dandavison/delta does a line-based diff but it also syntax highlights its output. I'm hoping that
38.
by Wilfred 5y ago
I agree sliders are a problem, and I hope to have a solution there. Syntactic differs already do better because they understand that parentheses/brackets are paired. Difftastic does OK with this example: https://imgur.com&#x
39.
by Wilfred 5y ago
A syntactic differ like Difftastic is very helpful when your codebase is autoformatted. Formatters often reflow code. Given the code: foo(one, two, three); If you add an argument and reformat: foo( one, two, new,
40.
by Wilfred 5y ago
Author here! Happy to answer any questions :)
41.
by Wilfred 10y ago
Numeric | https://www.numeric.com | Full time | Onsite | Boston, MA Managing $19.7 billion of other people's money presents interesting technology challenges. At Numeric, we're looking for Python people to help build,
42.
by Wilfred 10y ago
Numeric | https://www.numeric.com | Full time | Onsite | Boston, MA Managing $19.7 billion of other people's money presents interesting technology challenges. At Numeric, we're looking for Python people to help build,
43.
by Wilfred 11y ago
> you can still buy the Symbolics OpenGenera LISP environment I don't think this is still the case. I sent an email to their sales email address, and heard nothing. I also tried contacting their engineer, and even found the MIT emai
44.
by Wilfred 12y ago
ESS includes a fork of julia-mode. I'm hoping to replace this with a dependcy on julia-mode, so ESS benefits from all the highlighting improvements we're doing. See https://github.com/emacs-ess/ESS/issues
45.
by Wilfred 12y ago
You may also be interested in https://github.com/nschum/highlight-symbol.el which provides highlighting of the current symbol, and provides highlight-symbol-{next,prev} commands to move between occurrences of a symbol.
46.
by Wilfred 12y ago
Wow, I wasn't expecting to see this on HN. Thanks for the kind words :)
47.
by Wilfred 14y ago
Sure. There's no single feature improvement that is much better, but when considering the improvements together the difference is striking. 1. The search term is highlighted. 2. The search is far more discoverable, its key binding means you
48.
by Wilfred 14y ago
1: a. Superb readline colouring. Nonexistent commands are shown in red, commands that exist and are on PATH in green. Unclosed string literals become obvious. b. A history search that is orders of magnitude better that Ctrl-r in Bash. (Thou
49.
by Wilfred 14y ago
> "Smart people don't assume others are stupid". FWIW: This is Chersterton's fence fallacy. This states that you should not criticise a viewpoint without understanding the reasoning behind it. The reasoning may be unsound, but without k
50.
by Wilfred 14y ago
> The word and character etymologies are also treated abominably poorly in the Memrise story. I never advocate filling one's mind with junk just to have memory hooks for learning new information. Etymology is a complex and often convolu
51.
by Wilfred 15y ago
I've read the paperback version and came away slightly disappointed. The book is essentially a distillation of papers the author found interesting and applicable. The separate chapters felt completely disconnected from each other. There wer
52.
by Wilfred 15y ago
The death of Kazaa was a major contribution to BitTorrent usage. If it becomes the easiest way of accessing pirated content then I could see it doing very well.
53.
by Wilfred 15y ago
Interesting that it's on paste.lisp.org. It strongly reminds me of Emacs' rx macro. I suspect this a port of another toy regexp implementation -- otherwise I would expect the author to use `itertools.chain` rather than implementing somethin
54.
by Wilfred 15y ago
That's a consequence of memoisation. It scales better than the original code though. Still, the original point (node is cooperatively multitasked) was clear. Anything beyond that and I just want to reach for better Fibonacci algorithms.
55.
by Wilfred 15y ago
For what it's worth: that's stock Emacs behaviour, at least on the current version (23.3). Seems like a highlighting bug.
56.
by Wilfred 15y ago
It is, though that's not very surprising. Here's a quick proof: S-K combinators[1] are a Turing-complete subset of lambda calculus. Here's an implementation of them: k = (x) -> (y) -> x s = (x) -> (y) ->
57.
by Wilfred 15y ago
It's remarkably hard to get this right. pwdhash notes[1] that being a browser plugin stops JavaScript grabbing the password, but it's still possible with Flash. Third-party ports to other browsers don't even have the JS protection. pwdhash
58.
by Wilfred 16y ago
> determining whether a given file constitutes a virus seems equivalent to solving the halting problem. In fact (for a sufficiently rigorous definition of virus), it is provably the case that we cannot determine whether a file is a viru
59.
by Wilfred 16y ago
Yes. Why not? Who does it hurt? I intend to write a Twitter client this year, since existing clients don't meet my needs: * web app * multi-account support * rate-limit noisy accounts * automatic language detection for people who tweet in m
60.
by Wilfred 16y ago
Funny you should mention that. There was a survey of favoured web frameworks[1] in the Lojban community, and Haskell with snap won[2]. 1: http://www.surveymonkey.com/s/T6B69LK 2: http://teddyb.org/~rlpowell/public_media/lojban_survey.PNG

More ›