Cecile Tonglet
Cecile Tonglet
Well... you do you of course. You don't have to do as I said :sweat_smile:
Words like `Closes ...`, `Fixes ...`, `Related to ...` are actually used to link stuff together and sometimes even close the issues/pr automatically. But I think it's important to remember...
@jayjamesjay are you expecting something with mio more like this? ``` tmp-h9kdub v0.1.0 (/home/cecile/.cache/cargo-temp/tmp-h9KDuB) ├── http_req v0.8.1 │ ├── native-tls v0.2.8 │ │ ├── log v0.4.14 │ │ │ └──...
(This is the only feature I'm waiting before trying amp again. But I would prefer the fuzzy search I describe in #133 which is like jumping in a file but...
One workaround I found for now is to use these arguments to ignore the json files: `git diff -- . ':!*.json` https://maheshwaghmare.com/git/how-to/exclude-files-from-git-diff-command/
Sorry I can't... maybe if I find a way to anonymize the file somehow... :thinking: All I can say is the JSON is in multiline and has been generated with...
> (I agree that maybe difftastic should be consistent for git-lfs, but it shouldn't crash.) Actually, imo, it's a feature that it can shows the diff of files that are...
With `DFT_GRAPH_LIMIT=500000` the memory fills up very close to the limit BUT it worked :sweat_smile: ``` 1/374 --- Text (exceeded DFT_GRAPH_LIMIT) ```
It is strange that for the Rust file that is even bigger it doesn't fill up the memory at all
> there is a plan to merge this code in the master branch? > why is this not implemented? stylish/greasmonkey don't really work for something like Rambox :/ Yeah actually......