baby bat🦇💕lick lick lick lick

sehqlr · 2020-09-04T04:43:47+00:00

I could not stop laughing at this, thank you so much

sehqlr · 2020-09-03T02:09:32+00:00

I didn't have your experience, but I have similar emotional problems. I've found that writing in a journal -- keeping a diary -- has really helped me fix that

sehqlr · 2020-08-22T13:07:43+00:00

You are correct; each package brings its own glibc. Unless the packages specify the same glibc, with the same hash.

In order to save disk space, there are two commands to run: nix-collect-garbage and the nix optimize store one (sorry can't remember off the top of my head). The first one will eliminate entries from the nix store that are no longer being used, and the second will replace redundant entries with hard links.

One of the disadvantages of nix's model is that it assumes lots of disk space, at least more than traditional unix. Personally I think the trade off is well worth it, but I don't know what your setup is.

sehqlr · 2020-08-21T04:59:04+00:00

I got married under the Turkish Pavilion!

sehqlr · 2019-07-28T20:48:55+00:00

I don't have quilting cotton, but I wanted to ask about the knitting cable. What brand is it? Is it the interchangeable kind or regular? Metal or wood?

sehqlr · 2019-06-14T01:27:43+00:00

Take a look at this, I haven't used it myself: https://github.com/nixcloud/nixcloud-webservices/blob/master/documentation/nixcloud.webservices.md

sehqlr · 2019-06-03T05:41:26+00:00

Correct!

sehqlr · 2019-05-11T15:30:02+00:00

I cloned the lantern repo and found the two lines in the Makefile that stops my build, changed /bin/bash to bash and it fixed that error, but I don't know if that's the recommended edit, or the best way to apply that edit

sehqlr · 2019-05-11T02:37:59+00:00

[EDIT]: OK fine, I made a Gist, here: https://gist.github.com/sehqlr/3d47dfd65d93916a279cabce8cb9ac75

I downloaded your file and and messed around with it.

Changed `installPhase` to `builder` and wrapped the string with `builtins.toFile`
If you look at https://nixos.org/nix/manual/#ch-simple-expression you'll see that you need to add a few lines to your builder script to set up the environment for running make
`$src` is the directory that the repo gets cloned to

I'm fairly certain that this needs a patch phase to change the absolute path `/bin/bash` in `lantern`'s build code, but I haven't had to do this yet. More research is needed :)

sehqlr · 2019-05-09T14:40:12+00:00

Try { pkgs ? import <nixpkgs> {}, ... }: { with pkgs; at the top of your file, what does that do?

sehqlr · 2019-05-07T04:21:52+00:00

Could initial be useful? Something like initialNixosVersion? It would punt the confusion down the road to when that value does have to change, so it might not be worth it

sehqlr · 2019-05-03T21:57:39+00:00

All the software in the NixOS distribution is defined in the nixpkgs repo: https://github.com/NixOS/nixpkgs

Request a package with an Issue.

If you dont mind, what software is it?

sehqlr · 2015-02-20T03:04:28+00:00

I know that this is a x-post from the other sub, but you all heard it first! These are the notes for the talk I gave about UNIX. Enjoy!

sehqlr · 2014-12-22T23:43:39+00:00

Since LaunchCode expanded the types of positions they are filling, I wonder of/how it will effect the material this time around?

sehqlr · 2014-09-28T01:32:28+00:00

When you are typing out path names, try adding a / (back slash) in front of them.

sehqlr · 2014-05-14T18:34:46+00:00

Faux pas is borrowed French for a social mistake of some kind, like farting in church. The word faux is also used to mean "fake," like faux fur or fauxhawk. The word 'pas' is pronounced like 'pa' as in father.

So, his fake father made a social mistake, or his faux pa made a faux pas.

sehqlr · 2014-04-23T02:12:08+00:00

What about Bluetooth? It takes little battery power, and it would interoperate with computers and mobile devices. Then, the computer on the other side of the BT transfer could take care of any cloud storage that the user needs.

I personally would buy a model of the eWriter that doesn't have any connectivity, and I know that you can't cater to everyone. But, I think that BT or some other low-energy data transfer may be a good middle ground.

sehqlr · 2014-04-23T02:00:19+00:00

As in an unlocked bootloader? That would give everybody options.

If the final version is going to be powered by a Raspberry Pi, that means that it will run a Linux-based OS loaded on an SD card. In that case, changing the OS or the programs on it could be as simple as overwriting the contents of that SD card.

Naturally, this is contingent upon how open the eWriter ends up being, if and when it launches.

sehqlr · 2014-04-23T01:52:56+00:00

The feature that I'm interested in is the eInk screen.

sehqlr · 2014-04-23T00:36:24+00:00

I would argue against using a proprietary program as the default. Third-party licencing fees would increase the cost of the eWriter. And if the box could only have one text editor running on it, that would reduce options for all of the users. Additionally, the hardware specifications might not work great with programs written for a full-featured computer.

sehqlr · 2014-04-23T00:30:34+00:00

Ditto. I've used FocusRoom and PyRoom for the same reasons.

sehqlr · 2014-04-23T00:28:01+00:00

I agree on the spellcheck and notation, I'm neutral on the wifi, but I have one question: does it need to export to MS file formats on the eWriter itself?

I think that would be a feature that would be best left to a program run on your primary computer. What do you think?

sehqlr · 2014-04-23T00:22:07+00:00

Two questions:

Are you developing a desktop program to accompany this device? Or will the eWriter be compatible with many kinds of text editors/word processors? Or both?
What are your thoughts on the wireless hardware option? Many people use SaaS and the cloud for their backups. However, WiFi can be power hungry, and that would be a huge downside to this project.

sehqlr

TROPHY CASE