line-by-line | NodeJS module that helps you reading large text files | Document Editor library

Your problem is that the matching you are doing, both grep /$var/ and index($line, $var) allows for lines to match partially. I.e.

Package HISTORY-TREE does not exist

That message is clear: the package HISTORY-TREE does not exist. But you try to read symbols into this non-existent package, for example HISTORY-TREE:OWNER.

Every package which is mentioned in a printed symbol in that file needs to exist, before one can successfully read the file.

The default Common Lisp reader does not create packages on the fly by just reading symbols.

Example:

The floating of .talent is most likely the culprit. When floating elements the parent looses track of their height, so if you check the dev tools you will most likely find out the divs with the class yui-gf are actually ending there.

Remove the floating and width of the .talent and try using grid on the parent to align its childs in columns.

The problem here is that readline.question is asynchronous and you need to wait for each callback to return, before you (a) can use the input and (b) create the next question. You are executing the console.log statement, however, directly after the question call. It's probably the easiest way to wrap the question into a promise, so that you can await the response.

Here is an example using promises: https://stackoverflow.com/a/47999168/3233827

I could make it work by changing the updateOne() to insertMany().
Quick explanation: instead of inserting one by one, we would be inserting by 100k. So I just created an array of user and when it reached 100k documents, we would insert with insertMany()

I was confused as well until I found this page of documentation. The part you are interested in is:

A line that defines a value can be continued to the next line by ending it with a \; the backslash and the end-of-line are stripped. Leading whitespaces after name =, the remainder of the line after the first comment character # or ;, and trailing whitespaces of the line are discarded unless they are enclosed in double quotes. Internal whitespaces within the value are retained verbatim.

Inside double quotes, double quote " and backslash \ characters must be escaped: use \" for " and \\ for \.

The following escape sequences (beside \" and \\) are recognized: \n for newline character (NL), \t for horizontal tabulation (HT, TAB) and \b for backspace (BS). Other char escape sequences (including octal escape sequences) are invalid.

So, here the correct alias in .git/config:

There are apparently (5 or) 6 cases of consecutive values, and the omnipresent default.

The jump table contains one address per case, and you will find these addresses in your listing.

For example, 0x00000000004005a1 is the address of this part:

Consider better-files which gives an Iterator into the compressed file

require is implemented inside the VM, so it has access to internal functionality that normal Ruby code does not. For example it can manually escape its current scope and execute code at the top level. That is "how".

As for "why"? Imagining if you could require into a specific scope, this would be extremely prone to breakage since it would change top-level self from main (which is an Object) to... anything (in your example it would be A, which is a Class). It would be very hard to predict in general what would happen when your code is required.

By always executing loaded code at the top-level, the result is always consistent. And you can use the built-in hook mechanisms (included, extended, prepended, inherited) to access specific selfs from the scope that loaded you.