Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing content in The Art of Unix Programming #20

Open
mlafeldt opened this issue Feb 2, 2013 · 5 comments
Open

Missing content in The Art of Unix Programming #20

mlafeldt opened this issue Feb 2, 2013 · 5 comments
Milestone

Comments

@mlafeldt
Copy link

mlafeldt commented Feb 2, 2013

Hi @danchoi,

While reading the mobi version on my Kindle, I noticed that some bits were missing from http://www.faqs.org/docs/artu/ch01s06.html

In the original it says:

Doug McIlroy, the inventor of Unix pipes and one of the founders of the Unix tradition, had this to say at the time [McIlroy78]:

(i) Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features.

(ii) Expect the output of every program to become the input to another, as yet unknown, program. Don't clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don't insist on interactive input.

(iii) Design and build software, even operating systems, to be tried early, ideally within weeks. Don't hesitate to throw away the clumsy parts and rebuild them.

(iv) Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you've finished using them.

He later summarized it this way (quoted in A Quarter Century of Unix [Salus]):

However, points (i) to (iv) are completely missing in the mobi.

I guess the Ruby parser has to be extended to parse this HTML too:

<div class="blockquote"><blockquote class="blockquote"><p>(i) Make each program do one thing well. To do a new job, build
afresh rather than complicate old programs by adding new
features.</p><p>(ii) Expect the output of every program to become the input to
another, as yet unknown, program. Don't clutter output with
extraneous information. Avoid stringently columnar or binary input
formats. Don't insist on interactive input.</p><p>(iii) Design and build software, even operating systems, to be
tried early, ideally within weeks. Don't hesitate to throw away the
clumsy parts and rebuild them.</p><p>(iv) Use tools in preference to unskilled help to lighten a
programming task, even if you have to detour to build the tools and
expect to throw some of them out after you've finished using
them.</p></blockquote></div>
@mlafeldt
Copy link
Author

mlafeldt commented Apr 7, 2013

I guess this is a duplicate of #11. Didn't see it when posting the issue.

@bmbeverst
Copy link

@mlafeldt Hey, I was able to manually fix the mobi. Take a look at the other issue.

@danchoi
Copy link
Owner

danchoi commented May 18, 2014

Sorry I've been MIA -- I've been busy

On Sat, May 17, 2014 at 3:59 PM, Brooks notifications@github.com wrote:

@mlafeldt https://github.com/mlafeldt Hey, I was able to manually fix
the mobi. Take a look at the other issue.


Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-43422679
.

@bmbeverst
Copy link

Without you there would have been nothing for me to fix, I am really enjoying it.

Thank you!

@danchoi
Copy link
Owner

danchoi commented May 19, 2014

You're welcome and thank you

@dmitry dmitry added this to the 2014 milestone Oct 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants