Hacker Newsnew | comments | show | ask | jobs | submit | ieure's commentslogin

Because I want my shell prompt to be a giant graph.

▁▁▁▁▅▁▇▁▁▅▁▁▁▁▁▂▂▁▃▃▁▁▃▁▃▁▂▁▁▂▂▅▂▃▂▃▃▁▆▃▃▃▁▇▁▁▂▂▂▇▅▁▂▂▁▇▁▃▁▇▁▂▁▇▁▁▆▂▁▇▁▂▁▁▂▅▁▂▁▆▇▇▂▁▂▁▁▁▂▂▁▅▁▂▁▁▃▁▃▁▁▁▃▂▂▂▁▁▅▂▁▁▁▁▂▂▁▁▁▂▂$

Ship it.

-----


Does HN really not have any protection against comments that are very long single words that screw up the page width?

-----


This is what I started from to create the ePub. If you look all the way back in the repo history, the first commit is a mirror of those files.

-----


It's probably worth running the HTML through tidy to get cleaner XHTML and then spending a little while trying to get http://code.google.com/p/epubcheck/ to be a bit happier. In general, EPUBs that "pass" epubcheck have a better chance of working interoperably in a lot of EPUB readers.

-----


Link is definitely dead, mirror: http://www.youtube.com/watch?v=h1r9XZZISS4

-----


Also, http://bit.ly/aD0TiH

-----


Cool story, bro.

-----


Nice summary. http://bit.ly/9Pq3aE

-----


If you put the URL into Safari on your iPad, it should prompt you to open it in iBooks.

-----


doesn't work for me. It only offers to open the .epub file in Stanza or GoodReader. iBooks is not shown as a possible choice.

-----


Wow, lame. It works with PDF, I assumed it would work with ePub. I assumed wrong.

-----


I sympathize; I was in a simliar situation around five years ago.

There are three things I've done which have been responsible for literally every job I've had in the last decade. In order of importance, they have been:

1. Know people. 2. Engage in the FOSS community. 3. Challenge myself.

That's it. Now, the interesting thing is that if you reverse this list, you get the steps you need to get a new job:

3. By challenging yourself, you will increase your knowledge base and become a better coder. 2. Find an project, tool, or subject that interests YOU. Something YOU would find useful and rewarding. Whatever it is, write it and RELEASE IT. If there's a project that already does what you want, start contributing. Help other people use it. Write documentation. Anything. Whatever it is, RELEASE IT. Doesn't matter if it's something a hundred people worldwide will find interesting - you'll get their attention, which leads to… 1. Knowing people who can get you jobs.

I cannot stress this enough: RELEASE CODE. The great thing is that you can usually get your employer on board with this. If other people use it, they can contribute features and bugfixes back, which they can make use of. It's like having programmers work for them for free.

The fact that you have this ambition at all puts you at a significant advantage over other programmers. Keep hold of that drive.

-----


Clever shortcut to use JS literals, which means that parsing it can be read with eval(), but the syntax sure is awful. No symbols to speak of, no keywords, and commas everywhere.

-----


I just checked the breakdown with sloccount.

C: 20% ELisp: 78%

-----


The parts that are written in C are mainly the lisp interpreter itself, and some windowing stuff. Unless you are doing something really strange you never need to dive into the C internals.

-----


What's the last 2%?

-----


Python? http://pymacs.progiciels-bpi.ca/pymacs.html

-----


"magic"... ;-)

-----

More

Applications are open for YC Summer 2015

Guidelines | FAQ | Support | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: