Re:Using hashtags to organize your bash history
by pyre on Sunday June 30, 2013 @10:31AM
(#5965896)
The phplint example isn't a great one. If you use phplint enough you should either:
1) Create a generic shell script as others have stated.
2) Create a Makefile for your projects with a 'lint' target. If you create many different PHP projects, consider a project template directory with a Makefile that already has this, so that every new project automatically has the functionality:
make lint
This idea has been around though. I can't recall if I've seen tagging used before, but saving an unexecuted commandline in the shell history by commenting it out is another useful hack that's been around a while.
Re:Using hashtags to organize your bash history
by scribu on Sunday June 30, 2013 @11:17AM
(#5966037)
The technique might have been around for a while, but it's the first time it made the connection in my head between twitter hashtags and bash comments, so +1 to the OP.
1) Create a generic shell script as others have stated.
2) Create a Makefile for your projects with a 'lint' target. If you create many different PHP projects, consider a project template directory with a Makefile that already has this, so that every new project automatically has the functionality:
This idea has been around though. I can't recall if I've seen tagging used before, but saving an unexecuted commandline in the shell history by commenting it out is another useful hack that's been around a while.