43 Matching Annotations
  1. Jun 2020
    1. copy editing

      I'd like to strike a blow for line editing. From Peter Ginna's brilliant What Editors Do:

      A line edit dials down to the paragraph/sentence/word level. As we said, it’s usually a much more expensive job than a developmental edit. A line editor will go through the pages of your book with a fine-toothed comb, looking for dialogue that feels awkward, sentences that don’t quite work, repetition, and more. Obviously this happens when the bulk of the work in terms of plot, character, beginnings, middles, and ends is done. It’s not that a line edit can’t address the bigger picture. But in most publishing houses an editor simply won’t do a line edit until the bigger issues are addressed, so as not to have to do the same work twice. It’s smart to stick with that order in self-publishing too. Line edits may or may not come with an editorial letter. But be sure that the fee includes time for you to meet in person or talk on the phone once you’ve had a chance to digest the edits. Often the same person could do both a developmental edit and line edit, if that’s what you decide to pay for, but you will also need a copyeditor. Copyeditors are the grammarians, the fact-checkers, the formatting gurus, the identifiers of repetitive words and phrases. They are the ones who make a book as smooth as a fresh jar of Skippy. The one instance where you might not need a separate copyeditor is if you hire someone to do a line edit who does a copyedit simultaneously. Some people have both skills and can pull this off, though it’s rare.

  2. May 2020
    1. Eric Schmidt, former Google CEO and Chairman, famously said “Google’s policy on a lot of these things is to get right up to the creepy line, but not cross it.” But for most people, that line was crossed by Google, Facebook, and others long ago.
  3. Apr 2020
    1. I had never considered it that in nearly a decade of using GNU find! Thank you for that! It will definitely change the way I think about -prune from now on.
    2. I think this structure is much easier and correlates to the right approach
    3. it isn't actually -prune itself that causes this, by the way. The issue is that the or operator "short-circuits", and or has lower precedence than and. The end result is that if a file called .snapshot is encountered it will match the first -name, -prune will then do nothing (but return true), and then the or returns true since its left-argument was true. The action (eg: -print) is part of its second argument, so it never has a chance to execute.
    4. If all you want to do is print the results you might be used to leaving out the -print action. You generally don't want to do that when using -prune.
    5. which means that it'll also print out the name of the directory you're pruning, which usually isn't what you want. Instead it's better to explicitly specify the -print action if that's what you want
    6. The thing I'd found confusing about -prune is that it's an action (like -print), not a test (like -name). It alters the "to-do" list, but always returns true.
    1. Did you expect the temp directory to get printed? In the last example, we saw the directories ./temp and ./C/temp got printed, but not now. This is the effect of the -print option. By default, the find command prints all the files matching the criteria. However, once the -print option is specified, it will print files only on explicit print instructions. In this find command, -print is associated in the other side of the OR condition, and hence nothing will get printed from the 1st part of the condition.
    2. 12. Same using the wholename option and prune to exclude directory: $ find . -wholename "./temp" -prune -o -perm 644 -print ./area.pm ./C/temp ./C/f2.c find has a switch with the name 'wholename'. Say, in your directory tree, there might be more than one temp directory. The earlier approaches will prune all the temp dierctories. In case, if the requirement is to prune a specific temp directory, then you can give the path of the directory itself. Note: The path specified in the wholename option should be relative to the search path specified, not the absolute path. 
  4. Mar 2020
  5. Jan 2020
  6. Dec 2019
    1. GitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.

      Looks like GitHub Packages acts as a wrapper to these clients, acting on your behalf so you don't have to use the CLI yourself.

    1. Using find and cpio is a more unix-y approach in that you let find do the file selection with all the power that it has, and let cpio do the archiving. It is worth learning this simple use of cpio, as you find it easy to solve problems you bang your ahead against when trying tar.
    2. find
  • Nov 2019
    1. From the man pages The environment variables can be specified in lower case or upper case. The lower case version has precedence. http_proxy is an exception as it is only available in lower case. Using an environment variable to set the proxy has the same effect as using the --proxy option
  • May 2019
    1. The RNA-seq data for all 64 cell lines expressing 89% (n=17544) of all protein-coding human genes are presented in the Cell Atlas and can be used as a tool for selection of suitable cell lines for an experiment involving a particular gene or pathway or for further studies on the transcriptome of established human cell lines.
  • Oct 2018
  • Jun 2018
  • Dec 2017
  • Nov 2017
    1. In Bash you quite often need to check to see if a variable has been set or has a value other than an empty string. This can be done using the -n or -z string comparison operators.

      Two most useful commands in bash

  • Jun 2017
  • May 2017
    1. Distant Early Warning Line (DEW Line)

      The Distant Early Warning (DEW) Line was a chain of 63 radio and communication centers that spread from Alaska to the Canadian Arctic to Greenland. The DEW line was an American defense project to protect them from Russian threat. The DEW line was the first joint American and Canadian defense project (Lajeunesse). Because the majority of the project was paid for and spearheaded by the United States, Canada feared losing sovereignty in the Arctic. The United States did not wish to control Canadian land, but would control military forces in that region. Canada feared American presence and demanded that any American military air force bases be located away from densely populated areas. The DEW Line was functional by 1957. The DEW line was primarily controlled by the American Air Force, as the Canadian Air Force personnel did not have proper training or manpower to serve the DEW line. The Canadian presence on the DEW line was largely ceremonial to display Canadian approval and control of their land. The Canadian government pushed for the DEW Line to become NATO territory to minimize American dominance of the region, but this hope was never realized. In order to regain control over their Arctic territory, Canada constructed its own radar line called the Mid-Canada Line. Constructing their own line allowed Canada to regain recognition as a powerful ally and partner to the United States.

      References: Lajeunesse, Adam. "The Distant Early Warning Line and the Canadian Battle for Public Perception." Canadian Military Journal. Accessed May 04, 2017. http://www.journal.forces.gc.ca/vo8/no2/lajeunes-eng.asp.

  • Nov 2015
    1. If you have a copy of the ReSpec repository handy, you may see that there is also a respec2html.js tool under tools/. Feel free to try using it instead of the above process, but please note that it is not used much currently and may behave in a somewhat experimental manner (experiences with it vary — but it's worth a shot if you're looking for a way to generate ReSpec output from the command line).

      Respec (sadly) doesn't quite have a command line tool...at least not one comparable to a browser's output.

      Maybe PhantomJS (which Respec uses for tests) would do a better job?

  • May 2015
    1. esta ficha, pero cualquier otra parte de la página mantiene una línea de baja interacción por parte del usuario: por ejemplo, al no poder subrayar alguna de las partes del texto, la funcionalidad de hypotesys queda reducida a referirse a algún concepto en particular. Claro, ha de pensarse que el cut and paste tiene contrapeso en propiedad intelectual solo qe también merma el potencial de hipervínculos para el aprovechamiento de la información de manera académica. Unas de cal .... En este caso quedan a debate las palabras referidas a "De esta manera los indígenas protegieron a la deidad de su destrucción"