Hacker Newsnew | past | comments | ask | show | jobs | submit | zdkaster's commentslogin

Got the same issue, LOL.


If you have experienced in racing, motocycle racing in particular, you can relate this message very well. Trying too hard can really reduce performance or laptime, similar to run the marathon. You have to feel very relax to get better result. And, feeling relax in death-pace or very risky situation like racing is something you need to work on overtime. The appropriate amount of effort is the key.


I completely agree. Start with what works, rough, understand it a bit deeper develop better solutions. Any trial-error, brute force or inelegant makes more natural for practioner. I think this aligns with George Pólya https://en.wikipedia.org/wiki/How_to_Solve_It book. The brute force is more productive and will build better intuition when you will realize the pattern and so elegant will come.



MOST is a paging program includes splitting screens, lockable scrolling, wide file support, ANSI color support, and mouse wheel scrolling.


You know "less" has wide file support and horizontal scrolling (-S), ANSI color support (-R), mouse wheel scrolling (by default)?

It does not have splitting screens, but if you need to do this, then emacs or tmux can help. And I am not sure what "lockable scrolling" means.


Kind of tmux sync panes. Windows locked together, scroll together.

Refer to: [1] https://linux.die.net/man/1/most


Thanks for your feedback. Let me think through the interface a bit more.


For some rarely use server, this could be the case. However, any frequently used servers that will always be some base configuration via ansible, dotfiles etc. that can add the base alias to the shell.


Similar, rm-safely is just a simple shell function though. you don't need to really install another specialty command, just copy over rm() function put them in your shell rc.


Great point. Actually rm -i should be baked in our workflow so we can be a little bit more aware.


The @ symbol’s history traces back to 1739. Evolved from a commercial character to @ in email addresses, as detailed in the blog post.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: