Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pmurach
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Show HN: Slideck – Markdown-powered slides in the terminal
(github.com)
6 points
by
pmurach
3y ago
|
0 comments
2.
▲
Show HN: TTY::Option - A declarative command-line parser for Ruby
(github.com)
2 points
by
pmurach
6y ago
|
0 comments
3.
▲
Looking Inside a Ruby Gem
(piotrmurach.com)
1 points
by
pmurach
6y ago
|
0 comments
4.
▲
The Tao of Writing a Ruby Gem Specification
(piotrmurach.com)
1 points
by
pmurach
7y ago
|
0 comments
5.
▲
by
pmurach
7y ago
Exit codes are only used in the context of terminal shells. So it seems appropriate to refer to terminals. Wouldn't you agree?
6.
▲
by
pmurach
7y ago
You're right. However, I'm also extending the set of exit codes with Bash recognised statuses[1]. This also includes a list of fatal signals, e.i. exit codes 128 + n, where n is a corresponding signal error.[2] [1] http:/&#x
7.
▲
by
pmurach
7y ago
In this context "Do not use them.", these are reserved codes and shouldn't be redefined in your programs to mean something entirely different. So codes in range 64-78 are a standard across Unix systems. Usually, specific prog
8.
▲
by
pmurach
7y ago
This library improves the situation as: * It includes default user-friendly error messages for all the built-in exit codes. For example, the code 64 will print " "ERROR(64): Command line usage error" to stderr. * Machines, e.
9.
▲
TTY-Exit: terminal exit codes for humans and machines
(github.com)
61 points
by
pmurach
7y ago
|
14 comments
10.
▲
Working with Capistrano: Environment Variables and Remote Commands
1 points
by
pmurach
7y ago
|
0 comments
11.
▲
Express numbers as word numerals in Ruby
(github.com)
1 points
by
pmurach
7y ago
|
0 comments
12.
▲
Inflect English Nouns and Verbs in Ruby
(github.com)
1 points
by
pmurach
7y ago
|
0 comments
13.
▲
Working with Capistrano: Tasks, Roles, and Variables
(piotrmurach.com)
3 points
by
pmurach
7y ago
|
0 comments
14.
▲
Streaming Large Zip Files in Rails
(piotrmurach.com)
1 points
by
pmurach
7y ago
|
0 comments
15.
▲
Software Product – Fake It Until You Make It?
(piotrmurach.com)
2 points
by
pmurach
7y ago
|
0 comments
16.
▲
tty-logger: a readable logging for the terminal
(github.com)
2 points
by
pmurach
7y ago
|
0 comments
17.
▲
Bad Blood – A Tale of a Modern Vampire
(piotrmurach.com)
1 points
by
pmurach
7y ago
|
0 comments
18.
▲
Nobody Gives a Shit about Your Software
(piotrmurach.com)
3 points
by
pmurach
7y ago
|
0 comments
19.
▲
RSpec::Benchmark – Performance Testing in Ruby
(github.com)
2 points
by
pmurach
7y ago
|
0 comments
20.
▲
Can you learn a programming language in 48 hours?
(piotrmurach.com)
1 points
by
pmurach
8y ago
|
0 comments
21.
▲
The Path to Learning a Programming Language
(piotrmurach.com)
2 points
by
pmurach
8y ago
|
0 comments
22.
▲
Show HN: Coinpare – Compare cryptocurrency trading data in your terminal
(github.com)
1 points
by
pmurach
8y ago
|
0 comments
23.
▲
Show HN: Coinpare – Compare cryptocurrency trading data in your terminal
(github.com)
3 points
by
pmurach
8y ago
|
1 comments
24.
▲
by
pmurach
8y ago
Unfortunately, the majority of these projects are just forks of well-established ones without any contributions.
25.
▲
by
pmurach
10y ago
Many systems come preinstalled with Ruby. Bundler is a very elegant and simple solution - I don't think it is hostile. Quite often the tools that we build are written by developers for developers or system administrators. For example P
26.
▲
by
pmurach
10y ago
As always this depends. In principle I agree for example I wrote pastel-cli ( https://github.com/piotrmurach/pastel-cli ) that doesn't use any parser to figure out arguments. However, it's super basic, for any
27.
▲
by
pmurach
10y ago
The choice of not writing options parser was very deliberate. As much as it is a tempting proposition I believe there are already great tools around. TTY attempts to provide glue to stitch a lot of scripting needs together without opinionat
28.
▲
by
pmurach
10y ago
Very interesting. I haven't considered mruby but it makes perfect sense. Though I don't know how the situation looks like with regards to standard library? A lot of tty packages use esoteric stuff from Ruby standard libraries incl
29.
▲
by
pmurach
10y ago
I was aware of many progress bar libraries before writing tty-progressbar. The reason I ended up coding my own was to have a dead simple codebase - literally one file that does the job well. This makes it easy to maintain and receive contri
30.
▲
by
pmurach
10y ago
Regarding tty-table, I have number of things planned including different renderer types to account for more esoteric formats and also very simple formats like tsv(table separate values) etc...
More ›