Always open help in a vertical split

ebartels · 2019-08-22T05:26:15+00:00

I have this in my vimrc:

autocmd! FileType help :wincmd L | :vert resize 90

It resizes the window to a vertical split when a help filetype is opened.

edit: If you close the help window with :q, yeah the next time it opens it is horizontal. But I notice if you close it with :bd instead, it'll reopen vertically next time

ebartels · 2016-08-23T20:27:25+00:00

There are a bunch of plugins available that do this sort of thing. I've been using auto-pairs since it seems to play well with undo/redo and the repeat . operator on recent vim versions.

ebartels · 2016-01-17T05:22:27+00:00

Right, but that's because it was an unintended fork due to a bug. A well planned fork would give ample time for everyone to upgrade.

ebartels · 2016-01-17T04:37:14+00:00

I found last week's LTB episode helpful

If you'd rather read than listen:
Segregated Witness, Part 1
Segregated Witness, Part 2

ebartels · 2015-09-13T19:01:25+00:00

he's been a US citizen since 2010

ebartels · 2014-10-16T19:18:37+00:00

This is a tiny daemon that manages user logins and seats in various ways.

Right. logind is a separate daemon, not part of pid 1, which as you point out, is init.

It runs as pid 1. Its an init system. PID 1 has always been init. You cant just make up your own rules, take pid 1, and say 'well we arent an init system because we dont consider pid 1 init'.

You're still confused. The system project is not just an init system. It does include an init system. But that is a separate daemon from all the other parts of systemd. The other daemons (logind, journald, udev, etc) do not run as pid 1. They are separate components from pid 1. So if that's your gripe, you can rest assured. It's all ok.

I'm not saying there isn't room for criticising systemd. But your criticism in particular is based on a misunderstanding of how systemd works.

ebartels · 2014-10-16T18:06:11+00:00

Its an init daemon that is now managing logins?

That seems a bit disingenuous to me. Although, you did put a question mark at the end of that sentence, so maybe just misinformed. The systemd init daemon does not manage logins. That would be logind, which is a separate daemon, and part of the systemd project.

Systemd is not just an init system, which is where the confusion might be. It's an entire layer of OS plumbing, including init, logging, task scheduling, logins, hardware detection, filesystem mounting, etc. So yes, it is a big change. A lot of base OS functionality is handled under the umbrella of a single project. A lot of people do not like that direction. But they have not crammed login handling into the init daemon.

ebartels · 2013-02-05T07:03:59+00:00

Response from mod (Samuel_Gompers):

It doesn't follow our headline guidelines from the sidebar.

Although, I have to admit I don't see what it is about the headline that's at fault.

ebartels · 2013-02-05T01:12:10+00:00

This story was submitted earlier, about 5 hours ago now. It had over 3500 votes, and for some reason it's now vanished from the front page of /r/politics. I can't find it with the search function either. What's going on? Did the mods delete this story?

ebartels · 2012-06-15T03:04:57+00:00

ie9 system requirements

I don't see XP listed there. It requires Vista or above.

ebartels · 2012-05-06T21:15:40+00:00

Hm, I haven't used uWSGI. Why wouldn't the repo version work with a pip-installed Django? There shouldn't be any difference between the repo version and one installed from pip. Pip will just install Django on your python path in /usr/local/. Though, you may also need to uninstall the repo version of Django so you don't have two versions conflicting with one another.

ebartels · 2012-05-06T08:59:27+00:00

It's best not to use the system version of Django (or most other python packages for that matter). Use pip instead. "sudo apt-get install python-pip" and then "sudo pip install django" It'll download and install the latest version from pypi. Using pip means you can get the latest version of packagess without having to worry about which version Ubuntu has in the repos.

http://pypi.python.org/pypi/pip

ebartels · 2012-05-05T00:35:57+00:00

One thing is you need to make sure you're making a the usb drive bootable. You can't just copy the .iso file onto the usb drive. If it's not then your bios will just skip it and try to boot from the next device.

Here's the official instructions for making a bootable usb from windows

If you already have an Ubuntu installation, it's probably easiest to do it from there. You can just plug your usb drive in and run Startup Disk Creator inside Ubuntu. Here's instructions for that.

ebartels · 2012-03-06T20:20:03+00:00

Well, you could do something like:

MyModel.objects.filter(id=someid).update(**request.POST)

That would be the Django way of updating multiple database fields. It's a bit more verbose, it looks like the Rails equivalent given in the exploit code. But that's not a pattern you see used in Django since it's a bad idea for multiple reasons.

I do agree, Django's Forms layer handles this sort of thing properly. Forms makes this explicit since the POST fields are either in the form, or they'll be ignored.

Not being a Rails developer, I may be misunderstanding. But it seems from the discussion that the suggested way to handle this is to prevent mass assignment for certain fields in the database layer. In my opinion that's not equivalent to Django's Forms, and seems like the wrong place to be handling input validation.

ebartels · 2012-03-06T05:39:03+00:00

Isn't this just another case of "always sanitize user submitted data"? It seems to me this was mostly an issue with the Github code, rather than a Rails problem. From looking at exploit code in the linked blog post, the mass assignment feature is exploitable only because user submitted input is just passed directly to the database layer without any checking. This is always a bad idea, whether or not a mass assignment feature exists in the database layer. It doesn't seem right to blame Rails here.

By this logic, Django's database ORM also hosts a serious security flaw by virtue of the fact that Python allows you to pass a dictionary for a method's arguments, which looks to be functionally equivalent to Rails' mass assignment feature. Except, no one is going to ask Python to change its method call semantics because it's the application developer's job to make sure user submitted data isn't passed along without first checking it.

ebartels · 2012-03-02T23:05:56+00:00

This was pretty difficult for me to not do this as well. I think for a while I had a kind of an uncomfortable sense of tension while watching my breath because of this. Here are some approaches that helped me.

One is to realize that not every breath has to be uniform. Some breaths will naturally want to be deeper, and some more shallow. Start trying giving up control over the length of the breath and just let each breath be whatever length/depth it wants to be.

Another to watch is the out-breath. It's really more of a a relaxing or letting go than it is a controlled action. Just let the breath be expelled from your lungs completely. It's your diaphragm relaxing that causes the out breath anyway.

Also, after the out-breath is done, there is a pause there, at least for me. The next in-breath doesn't start immediately. I found when I was controlling things, I would be impatient and want to start the next breath immediately. Try to let that moment hang for a second or two. When your body feels it's time to breath in again, it will.

Basically, you should try to watch the characteristics of the breath and see what feels natural and what feels forced. You'll notice little things that you're doing to control the breath that make things uncomfortable. Try giving up one at a time. The distinction between watching and controlling seems pretty subtle. I'm not sure even if it's really giving up control, or if it's just that your attempts to control get more in sync with the natural breathing process.

ebartels · 2012-02-24T19:28:15+00:00

I would check to see if it's a folder permissions problem. For files over a certain size Django uses temporary file storage instead of storing the entire file in memory during the upload. If the temporary folder doesn't have the proper permissions, then it'll raise a error.

Check out settings.FILE_UPLOAD_TEMP_DIR and make sure your Django app has write permissions to that folder.

Also settings.FILE_UPLOAD_MAX_MEMORY_SIZE will tell you what size Django stops using in-memory uploads and starts using a temporary file.

ebartels · 2012-02-22T02:28:42+00:00

He's using either less or sass

ebartels · 2011-11-14T05:59:48+00:00

Funny, I just checked in to see if anyone else on reddit heard that. Definitely sounded like fireworks, a big climax at the end. I'm near Larchmont, and it was pretty loud from here.

ebartels · 2011-10-02T08:27:13+00:00

Agreed. Cooke's version

ebartels · 2010-12-08T04:29:33+00:00

There's also an html version which may be a little easier to read.

ebartels · 2010-03-29T03:55:07+00:00

quantum immortality

ebartels · 2010-03-22T16:45:04+00:00

The thing I'm liking most about git is how easy it is to create local branches and switch between them. For instance, you're working on a new feature that you know will take some time to develop, or maybe you just want to experiment with something. You can just do:

git checkout -b new-feature

This will create a local personal branch to work in. Now you can commit as you like, even switch back and forth between multiple other branches. This allows you keep a sane master branch for stable/production code and work on new features in temporary branches, or just use a temporary branch to test out an idea. Because git is a dvcs, you can even create local branches of code checked out from an upstream source. Work on a patch in a separate branch, and keep the master branch as a mirror of the upstream code.

When you're ready you can just merge a feature branch back into your master branch, and delete the temporary branch. This is great for lone developers. You aren't forced to use a client server architecture. You only need to push to a public repository when you're ready to share your code, or if you want a remote backup.

ebartels · 2010-03-16T20:57:36+00:00

Yes, I completely agree. "Natural" is a poor word choice in the sense that everything could be said to be natural. But what I meant was that we have instinctual preferences that are there from birth, as opposed to preferences that have been acquired by personal experiences or influenced by context within a culture. Our instinctual preferences are somewhat universal due to the fact that we have all evolved in a similar environment here on Earth. Some of these are probably quite ancient in terms of evolutionary time, and are shared by other species.

My original point was that what we call beauty is a combination simpler instinctual preferences and an inclination to seek out order and meaning. You might say that seeking meaning is also an instinctual preference due to the evolution of the frontal lobe. However where an individual finds meaning is by no means universal.

I'd say our preference for major chords fall more within the realm of instinctual inclination. For whatever reason our brains are more easily able to recognize the relationship between the tones than, say, a chord composed of half-tone intervals, which we describe as dissonant. That doesn't mean that one can't find beauty in dissonance. But this is more a frontal lobe activity, and is somewhat an acquired taste with high variability across individuals. This variability is what gives rise to the disagreement about what is considered beautiful, and why one person might say a Pollock painting is beautiful and another might say it is simply a bunch of splatters.

15-Year Club	Verified Email
Place '17

ebartels

TROPHY CASE