You mean in areas you are less expert in? :) Maybe it's bad at everything, but each person can only tell when it comes to their own area of expertise.
3,339 karma · joined December 30, 2009
You mean in areas you are less expert in? :) Maybe it's bad at everything, but each person can only tell when it comes to their own area of expertise.
EDIT: I just saw in my own comment history that I knew (but forgot) there is a more recent Zed text editor which is probably the one you meant.
Try writing a table in Emacs Org Mode before you say that!
All non-ancient packages use lexical scope. Most ancient packages anyone cared about were converted.
EDIT: I was made aware of the guidelines to not comment on voting, I apologize.
Also, the refunds for Cetes when you go over the limit take a few days, not 8 to 10 weeks.
- Interactivity: the results are updated live as you type, so you catch typos sooner and can tweak the search terms as you go.
- The buffer of search results you collect with Embark is not dead text like it would be in the terminal, instead, each line is a link to the corresponding file taking you to the line that matched.
- Wgrep lets you edit all the matching lines in place!
Packages referenced:
1. Consult: https://github.com/minad/consult/
2. Orderless: https://github.com/oantolin/orderless
3. Embark: https://github.com/oantolin/embark
4. Wgrep: http://github.com/mhayashi1120/Emacs-wgrep/raw/master/wgrep....
Put your phone in landscape orientation, pinch-zoom until the text takes up the entire width of the screen.
And that's excluding Word line-breaking which always looked rather poor to me: some lines were left very empty and others overcrowded. It just didn't look professional to me. Perhaps that was been fixed too.
You should give Evil a try, people say it's much better than Viper. At the very least Evil emulates Vim, while Viper just emulates vi.
- https://github.com/asdf-vm/asdf/issues/383 - https://github.com/asdf-vm/asdf/issues/547
They did do something to ameliate this though: now they refer to the proect as asdf-vm as much as possible, to distinguish it from Common Lisp asdf.
I guess knowing allowed types for each parameter is informative (more if very specific types are used rather than string or integer), but documentation usually specifies that anyway. And even knowing all the types isn't usually enough without documentation.
My point is just that I've used plenty of libraries in dynamically typed languages without needing to read the source. And conversely, I've occasionally needed to look at the source of a function in a staticly typed language, to answer some question not answered by the types and documentation.
I understand everything in that sentence except the word "so".