Live data from Hacker News

I quit my job to work full time on my open source project

ellie.wtf

151–160 of 190 posts

Re: I quit my job to work full time on my open source project

#151
post #150

I'm curious to hear what people's usecases are for retaining long shell history. For myself, I never really use it beyond the current work day (up arrow)

for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.

Yep, I do `history | grep ""` all the time..

I should probably make it a function now that I think about it.

Re: I quit my job to work full time on my open source project

#152
post #150

I'm curious to hear what people's usecases are for retaining long shell history. For myself, I never really use it beyond the current work day (up arrow)

for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.

It may just be that I don't use the shell very much compared with other people, mostly for building and running local code

Re: I quit my job to work full time on my open source project

#153
post #80

Earlier quoted context omitted.

There are grants, but you have to qualify for them. https://opensource.guide/getting-paid/ https://www.state.gov/supporting-critical-open-source-techno... https://new.nsf.gov/tip/updates/nsf-invests-over-26m-open-so...

Some grants exists but they are really tiny compared to the amount of FOSS that needs funding.

You have to weed out the people who just want to dick-around at home versus people who are actually providing value to society, so the bar is set very high right now.

Re: I quit my job to work full time on my open source project

#156
post #150

Earlier quoted context omitted.

for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.

Yep, I do `history | grep " "` all the time.. I should probably make it a function now that I think about it.

Most of the shells have built-in recursive search, why not just use that? `Ctrl + R` in bash / fish / zsh at least.

Re: I quit my job to work full time on my open source project

#158
post #150

Earlier quoted context omitted.

for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.

Yep, I do `history | grep " "` all the time.. I should probably make it a function now that I think about it.

i called my function `fh` for "full history"

Re: I quit my job to work full time on my open source project

#159

Earlier quoted context omitted.

Yep, I do `history | grep " "` all the time.. I should probably make it a function now that I think about it.

Most of the shells have built-in recursive search, why not just use that? `Ctrl + R` in bash / fish / zsh at least.

i usually want to just see all the options at once and pick the one i want, rather than searching through them one by one
Post reply on HN