When I was younger, I'd read slowly, trying to visualize the setting, keep track of character preferences, look up words I don't know, etc. I'd remember a book well enough to talk about it even a year or so after.
These days, I just skim over descriptions and read as fast as I could while still getting the main plot. I get attached to characters only if the book is really good and savor them during rereads.
I mostly read fantasy and sci-fi, which tend to have multiple books in a series. If they are easy-to-read and short (300-400 pages per book), it becomes easy to consume. Also, I read for escapism, so I don't read too closely.
alias a='alias'
a c='clear'
a p='pwd'
a e='exit'
a q='exit'
a h='history | tail -n20'
# turn off history, use 'set -o history' to turn it on again
a so='set +o history'
a b1='cd ../'
a b2='cd ../../'
a b3='cd ../../../'
a b4='cd ../../../../'
a b5='cd ../../../../../'
a ls='ls --color=auto'
a l='ls -ltrhG'
a la='l -A'
a vi='gvim'
a grep='grep --color=auto'
# open and source aliases
a oa='vi ~/.bash_aliases'
a sa='source ~/.bash_aliases'
# sort file/directory sizes in current directory in human readable format
a s='du -sh -- * | sort -h'
# save last command from history to a file
# tip, add a comment to end of command before saving, ex: ls --color=auto # colored ls output
a sl='fc -ln -1 | sed "s/^\s*//" >> ~/.saved_commands.txt'
# short-cut to grep that file
a slg='< ~/.saved_commands.txt grep'
# change ascii alphabets to unicode bold characters
a ascii2bold="perl -Mopen=locale -Mutf8 -pe 'tr/a-zA-Z/𝗮-𝘇𝗔-𝗭/'"
### functions
# 'command help' for command name and single option - ex: ch ls -A
# see https://github.com/learnbyexample/command_help for a better script version
ch() { whatis $1; man $1 | sed -n "/^\s*$2/,/^$/p" ; }
# add path to filename(s)
# usage: ap file1 file2 etc
ap() { for f in "$@"; do echo "$PWD/$f"; done; }
# simple case-insensitive file search based on name
# usage: fs name
# remove '-type f' if you want to match directories as well
fs() { find -type f -iname '*'"$1"'*' ; }
# open files with default application, don't print output/error messages
# useful for opening docs, pdfs, images, etc from command line
o() { xdg-open "$@" &> /dev/null ; }
# if unix2dos and dos2unix commands aren't available by default
unix2dos() { sed -i 's/$/\r/' "$@" ; }
dos2unix() { sed -i 's/\r$//' "$@" ; }
Thanks a lot for the feedback on Coreutils book! It's so nice to hear that it helped in your thesis.
Regarding the ebook versions, I use pandoc to convert GitHub style Markdown to PDF/EPUB (wrote a blog post about my process here: https://learnbyexample.github.io/customizing-pandoc/). I had to search through stackexchange threads to customize the few things I could. I don't know how to fix the kind of page breaks you mentioned. But, I'll try to find a solution. Thanks again for the feedback :)
Krakauer examines what it is about Everest that has compelled so many people -- including himself -- to throw caution to the wind, ignore the concerns of loved ones, and willingly subject themselves to such risk, hardship, and expense. Written with emotional clarity and supported by his unimpeachable reporting, Krakauer's eyewitness account of what happened on the roof of the world is a singular achievement.
learnbyexample @ learnbyexample @programming.dev Posts 123Comments 73Joined 2 yr. ago 
True, perhaps a case of doing too much of anything over a long period ;)