rmurri

I don't know about TST, but sidebery can alter your window title when it's active, so you can match css rules against it.

    #main-window[titlepreface*="Sidebery"] #TabsToolbar {
      visibility: collapse !important;
    }

From the web page: Dragonfly is an in-memory data store built for modern application workloads. It is fully compatible with the Redis and Memcached APIs, required no code changes to adopt

What settings and repo are you using for GTX 1050 with 2GB?

Yes and No. They are not mutually exclusive.

I find that generally I'm much more productive in Emacs, so I use it most of the time. But I reach for the IDE when it makes sense.

It's not merely nostalgia or availability. I continue to use emacs because it has the features that I want, where other software does not.

Some things I want out of an editor:

* Never having to touch the mouse in any way.

* The ability to customize any feature for my current project or mindset on a whim.

* No UI, as much as possible. Show me the content I'm editing and nothing else.

* A good, extensible, set of keybindings with a bunch of features for editing of raw text

I run my project in an IDE and will sometimes use a feature, but I generally don't develop there.

I'm another happy enpass user. They are also having a 30% sale on their lifetime plan right now. Works on Windows/Mac/Linux/Mobile.

Reproducibility and peace of mind! There's nothing worse that getting woken up at 3:30 AM and realizing that it'll probably take a few hours to rebuild a server because it's dead and not coming back.

When infrastructure is code, you just spin up a new machine...no thinking involved. Also, since you're used to deploying this way, the process is smooth and as quick possible.

When you build the server by hand...you're often searching around for old ssl certificates, installing packages you forgot were dependencies, etc. Takes a long time to get it right.

If you're skeptical of the cost/benefit of the approach, you realize really quick that it's worthwhile when stuff starts to fail. Especially if it happens more than once.

They also have good support for different screen sizes, and multi monitor differences between machines.

I don't think the intent is to do code review from email. The idea would be to send the merge request through email, which is then imported into your local git as a branch. Then you're able to do review/analysis/etc with whichever git tooling you prefer.