Live data from Hacker News

Unified access to the best community-driven cheat sheets repositories

github.com

61–70 of 87 posts

Re: Unified access to the best community-driven cheat sheets repositories

#61
post #45
post #17

Wow I love the idea. Will try it out today. Could be a time saving pal when switching to topics you are not working on every day.

# Sorry, we are experiencing extremely highload now. # We are working on the problem and how to get it fixed soon. # Please come back in several hours or try some other queries Would be cool to get offline functionality...

We are working on that but it is not so easy because many queries are generated just in time.

The high load problem is mitigated by the way, so you can try now if you want.

Re: Unified access to the best community-driven cheat sheets repositories

#62

The output seems to be optimized for people with dark background color on the xterm. Is there a possibility to have a different color scheme?

Yes

curl cht.sh/:styles-demo

select the best style for you, and use it in the queries.

curl cht.sh/:help

for more info.

Also, use the special client cht.sh which supports persitent configuration and many other useful features.

Re: Unified access to the best community-driven cheat sheets repositories

#63
post #33

It is interesting to see how the title effect number of upvotes and comments. I’ve submitted this other day and it did not get any upvotes. My submission: https://news.ycombinator.com/item?id=17471476

Yes it’s called “marketing” and it has a huge impact on initial perception. Consider each of these and think of which would catch your eye enough to click it, read about it, then come back and upvote it: * Meta cheatsheet * The only cheat sheet you need * Cheatsheet.sh * Cheat Sheetah * Unified CLI Cheetsheet People gaming the title is the reason for the rule that the title has to match the actual linked article. Tho…

Unless something has changed in the repo, the Github description -- as close to a "headline" that a Github repo can get -- is: "the only cheat sheet you need"

I agree that "Meta cheatsheet" is not a very effective title. When the repo doesn't have a Github description, I usually go with:

      [repo name] - [first line of README.md]
In this case:

cheat.sh - Unified access to community-driven cheat sheets repo of the world.

(I modified it to abbreviate "repositories" to "repo" and to omitted the phrase "the best", to go along with HN's rule for avoiding sensationalism.)

Re: Unified access to the best community-driven cheat sheets repositories

#64

Is the dropdown at https://cht.sh/ a little sluggish in chrome for everybody?

Yes, it is not good, we are working on the new frontend.

I can give a link to it to you if you want, but not here, because it will not handle the load that comes after that; just write me a mail if you want to test it.

Everybody who reads this and what to help testing the new frontend write an email to me I will share the link with you.

Re: Unified access to the best community-driven cheat sheets repositories

#66
post #60

Wait, in stealth mode it's listening for any text selected, even in other programs? This is a bit mind boggling - what's to prevent any program listening to any other (like a password manager for example)? Is this sort of access not prevented by an accessibility permission?

This is how traditional desktop operating systems work... some things require admin rights but most stuff is indeed fully accessible to any application.

Re: Unified access to the best community-driven cheat sheets repositories

#67

Not very respectful of https://github.com/chrisallenlane/cheat to use the same name. The original cheat does exactly the same thing, has a big following and more stars, and has existed for years. I've opened an issue re: the name conflict https://github.com/chubin/cheat.sh/issues/34 Afaik these are the big players in the space: - bro: https://github.com/hubsmoke/bro - tldr: https://github.com/tldr-pages/tldr - cheat:…

We are of course aware of the beautiful cheat project and we even use it (what is documented in our README.md file), but please keep in mind that: 1. Our project is called cheat.sh and not cheat (for example xterm.js and xterm are two separated projects and xterm existed for decades before xterm.js; should they be renamed too from your point of view?); 2. We are trying to mitigate the impact by using cht.sh where pos…

The reasoning boils down to Google-ability.

sh is not a distinct enough term when googling for shell suggestions, because both cheat and cheat.sh will have sh in the results. That is very distinct from xterm.js where xterm-only results are very unlikely to have JS in them.

A similar debate played out when the gofish package manager was launched, which conflicted with the fish shell https://github.com/fishworks/gofish/issues/37

Anyway, the choice is not mine to make, it just seems like an easy issue that could have been avoided by choosing a name that wasn't already in use.

Re: Unified access to the best community-driven cheat sheets repositories

#68

Is the dropdown at https://cht.sh/ a little sluggish in chrome for everybody?

Yes, it is not good, we are working on the new frontend. I can give a link to it to you if you want, but not here, because it will not handle the load that comes after that; just write me a mail if you want to test it. Everybody who reads this and what to help testing the new frontend write an email to me I will share the link with you.

Do you know what's causing it?

Re: Unified access to the best community-driven cheat sheets repositories

#69

The output seems to be optimized for people with dark background color on the xterm. Is there a possibility to have a different color scheme?

Yes curl cht.sh/:styles-demo select the best style for you, and use it in the queries. curl cht.sh/:help for more info. Also, use the special client cht.sh which supports persitent configuration and many other useful features.

Thanks, that helps.

Re: Unified access to the best community-driven cheat sheets repositories

#70

I like the idea, and think it has potential, but… The search engine is not great. The tutorial gives the example of searching for "execute+external+program". Change "program" for "command", you're OK. Change "execute" for "run"and it bombs. For something that simple, this causes doubt that if I were to look for a solution to a problem in a language I was learning and it bombed, is the fault with cht.sh, or with me? D…

I agree about the search engine.

I'm a big fan of Dash, but Dash is currently built around documentation rather than cheat sheets. If someone loaded up Dash with a bunch of cheat sheets, that would be really handy.

Post reply on HN