Hacker News Reader

Some random bits of context.

This conflict goes back a long time. In the early 1990's, with online journals just getting started, MIT was able to insist on principles like "anyone physically in the library has full access, even if they are not otherwise affiliated with MIT". A couple of years later, power shifted, and Elsevier could "our terms, take it or leave it". Then three decades, a human generation, of Elsevier rent-seeking, and so many people working towards Open Access, unbundling, google scholar, arXiv, sci-hub, and so on. Societal change can be so very slow, nonmonotonic, and profoundly discouraging. And yet here we are, making progress.

For anyone unfamiliar with "author [...] required to relinquish copyright [...] generous reuse rights", journals would require authors to completely sign over copyright, so authors' subsequent other-than-fair-use usage of fragments would be a copyright violation. Rarely enforced, but legally you'd have to obtain permission. While some institutions sign contracts easily, and struggle with the fallout later, MIT legal culture has been pain-up-front careful with contracts. Which is sometimes painful. But IIRC, we're today using X Windows instead of CMU's Andrew, because MIT could say "sure!" while CMU was "sure, err,... we'll get back to you... some mess to clean up first".

View on HN

typescript (see Figure 4 (Sample Typescript Window)) provides an alternative to xterm. You enter commands to your shell in the input window and the results are shown in the same window where they can be scrolled, searched or saved. Typescript does not support curses like xterm does, so you cannot run vi or bash in a typescript, for example. However, you can use the tcsh or pdksh (ksh) shells. Typescript has several other features that I find very useful. The README for the word processing package describes how you can cause the current working directory to be kept in the title of the typescript window. Typescript is "smart" about these paths, too. Notice in Figure 4. that the path shown in the title of the window is "~", my home directory, and not a fully qualified path. Typescript supports use of several PC keys to make it easier to enter commands. The Cursor-Left and Cursor-Right keys can be used to edit the command I am entering (regardless if my shell supports this). The Home and End keys will move the cursor to the beginning or end of the line (or selected area). The cursor keys are also mapped to allow me to move up and down the the command history. Cursor-Up gets the previous command entered, Cursor-Down the one after. In my opinion an even more useful feature is command completion. If I type "ls" and then press Cursor-Up, I get the previous command that began with "ls". File completion is supported with the tab key. If I enter "ls src/tp" and then press the tab key, typescript will complete the path "src/tp" to "src/tpg-config" (in my case). It makes entering paths to files ten times easier. I love it! If I enter a command like "ls /etc", the window will likely fill and scroll automatically. If I want to see the beginning of the scrolled data, I must use the mouse (or Page-Up/Down keys) to scroll. However, if I enter "ls /etc control-J" (where I enter the command with a control-J keystroke, rather than the normal Enter), the command is executed, but the output is pushed to the top of the current window so I do not need to scroll. Typescript also allows me to create my own menus in the file ~/.shmenu. In Figure 4, you can see I have a menu card Internet on the menubar. This is from my own .shmenu file which looks like this: