{"action":"opened","issue":{"url":"https://api.github.com/repos/tldr-pages/tldr/issues/273","labels_url":"https://api.github.com/repos/tldr-pages/tldr/issues/273/labels{/name}","comments_url":"https://api.github.com/repos/tldr-pages/tldr/issues/273/comments","events_url":"https://api.github.com/repos/tldr-pages/tldr/issues/273/events","html_url":"https://github.com/tldr-pages/tldr/issues/273","id":64249621,"number":273,"title":"Command search","user":{"login":"rubenvereecken","id":5216553,"avatar_url":"https://avatars.githubusercontent.com/u/5216553?v=3","gravatar_id":"","url":"https://api.github.com/users/rubenvereecken","html_url":"https://github.com/rubenvereecken","followers_url":"https://api.github.com/users/rubenvereecken/followers","following_url":"https://api.github.com/users/rubenvereecken/following{/other_user}","gists_url":"https://api.github.com/users/rubenvereecken/gists{/gist_id}","starred_url":"https://api.github.com/users/rubenvereecken/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rubenvereecken/subscriptions","organizations_url":"https://api.github.com/users/rubenvereecken/orgs","repos_url":"https://api.github.com/users/rubenvereecken/repos","events_url":"https://api.github.com/users/rubenvereecken/events{/privacy}","received_events_url":"https://api.github.com/users/rubenvereecken/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-25T11:44:57Z","updated_at":"2015-03-25T11:44:57Z","closed_at":null,"body":"I'd like to raise an idea I've played with for the last couple of days, especially when I noticed @rprieto raised it in #267 as well. \r\n\r\nThe next step after (or for) tldr is searching for commands by descriptions in natural language. When I thought of it I didn't think of it necessarily as part of tldr but it could be built on top of it. The idea is simple: we can already invoke tldr to remember those pesky command line options for a certain command. Now take a step back into novicehood and you'll want to find commands that do something in the first place. That's where this idea comes in.\r\n\r\nA very naive version would consist of tagging commands (again, not necessarily inside tldr) and search through those when a user tries something along the lines of `(tldr) search unpack tar`. This can actually be built straight into #tldr using the index proposed at #267 because then the client could search the tags that would be included in the index.\r\n\r\nTake a step further and you need an actual server to do language processing. I'd actually be interested in trying this out but it'd be a considerably bigger project and it couldn't live inside tldr anymore.\r\n\r\nThoughts on this?"}}