6 ms·
Cool. The link to "Risks" in the README is broken. What I would love: `ell -r` automatically, and an alias `fix` that proposes a fix, including making changes
by mherrmann 2y ago
Cool. The link to "Risks" in the README is broken.
What I would love: `ell -r` automatically, and an alias `fix` that proposes a fix, including making changes to a file. For example, say I have a typo in main.cc and do `gcc main.cc`. When I run `fix`, I want ell to propose a fix in the file with a diff. If I accept, it should make that change. Then it should propose running `gcc` again - and run it for me if I accept.
- Zambyte 2y agoRegarding running ell -r automatically, you can just add it to your .bashrc
- mherrmann 2y agoYup. But the rest of the functionality is missing, I think.
- simonmysun 2y ago> The link to "Risks" in the README is broken. Fixed. Thanks for pointing out! > `ell -r` automatically, and an alias `fix` that proposes a fix, including making changes to a file. Good idea! `ell -r` can be added to `.bashrc`, but I'm not sure if it will conflict users' original configurations or there will be other issues. Except confirming a patch, I think it is feasible with template and plugins, but making actuall changes is challenging for me, both techinology wise and user interface design wise. I will try to figure out what can be possible