I use screen with vim. One of the things I like about vim is that, much like unix itself, I’m always discovering useful new features, even after years of use.
Recently, I’ve been using tabs in vim to complement window regions. I’ve found it pretty useful, as there are times I’d want to keep certain tasks on one tab but not another. e.g. different source files open in windows on one tab; a test file + vim-pipe buffer showing the rest.
While I’m not using screen to change between multiple vim sessions in the same project anymore, I still use it pretty much everywhere: it’s there, and sometimes a wireless network isn’t. (Or you’re working one place and need to pack up and move to another place.) screen preserves your working sessions, so you don’t have to get everything “just right” again.
Unfortunately, screen seems to mangle the C-PgUp and C-PgDn commands vim gives as default (right?) shortcuts to switch between tabs. Leaving out that these key sequences are also used at the windowing level to switch tabs, it turns out that screen was mangling them on the way through to vim, so vim didn’t see C-PgUp, for instance, it saw some other sequence.
Adding this to your ~/.vimrc will cause vim to recognize the sequence it sees when running under screen:
" make C-PgUp and C-PgDn work, even under screen
" see https://bugs.launchpad.net/ubuntu/+source/screen/+bug/82708/comments/1
I’m in lovely Madison, WI right now, and will be headed over to my first YAPC::NA tomorrow. The first couple days are the hackathon, at which I think I’m going to work on a Dist::Zilla stash to hold repository related information. There are a bunch of Git related plugins for Dist::Zilla, a couple that I maintain, and a lot of code is duplicated between them; a stash should resolve that.
I’ve seen a couple references lately to using lazy attributes as a form of caching. This is a great approach to thinking about lazy attributes, as they share a number of characteristics with traditional caching: you only have to build a (potentially) expensive value once, and then only when you actually need it.
But what about when that lazily generated value is too old to trust?
A lazy attribute isn’t going to help you much then, as your instance is quite happy to keep on returning the same value forever once it has been built, unless you clear or change it manually. This is no good when, say, you’ve run a database query and you can really only expect your painfully contorted query to get the twitter ids of all the left handed Justin Beiber fans north of the Mason-Dixon line who own hypo-allergenic cats to be valid for, oh, say 55 minutes or so.
You could add an attribute to store the age of the value generated for the lazy attribute and check it either manually (boring!), or by wrapping the reader method (less boring, but still, unsightly).
Ok, method modifiers can be fun, but still… That’s a lot of annoying little code that, well, isn’t Moose there to help reduce that sort of code in our lives?
What we’re running into here is that while we implement one part of a cache (generate once, return many), lazy attributes don’t have any internal logic to determine when a value is no longer good. They don’t even have any concept of that, just “someone needed my value, so we’re going to get it and hang on to it until told otherwise”.
This is just the sort of behaviour an attribute trait can alter.
The AutoDestruct Moose attribute trait allows us to specify an expiration date for our stored values. We can specify a time-to-live option at attribute creation, and then every time a value is set, the set time is stored. Every time the value is accessed, the attribute checks to make sure the value isn’t older than the set time to live, and if it is, clears the value. This allows the lazy value generation to kick in once more, without requiring any extra effort on the part of the user — just as one would expect.
One thing that that had been particularly annoying me lately, was the ridiculously long package names called for in a certain project of mine. The package names themselves weren’t the problem, it was writing them out. With filenames like lib/App/MediaTracker/TemplateFor/Browser/PrivatePath/libraries/things/document.pm, the corresponding package names become very long and very painful very quickly.
Fortunately, I use vim as my editor of choice. Along with the fantastic snipmate vim plugin it’s possible to create a snippet that runs a little vim code as part of it:
The snippet should be stored in ~/.vim/snippets/perl.snippets, unless you have things arranged otherwise.
Now, assuming that my filename and package name are the typical parallels, simply typing pkg<tab> will create a proper package line for me, with an absolute minimum of pain.
Lazy attributes are wonderful. They allow us to postpone generating attribute values for any number of reasons: it’s expensive and we don’t want to do it unless we need it, it should be initialized after instantiation because it depends on other attributes, etc. And it does this without our having to worry about the value being around: if we need it, it’ll be generated on the fly without any extra effort on our part.
As an example, let’s say we have a simple config file that defines key/value pairs. We need to find out the author’s name, which has the key ‘author’ in the config file. We could create a lazy attribute as such:
Simple, yes? Now, whenever you need the authors name, you have it.
So, let’s now say that a couple days later, you realize that you also need to get the author’s email from the config file (key ‘email’):
Except… Hm. We’re now loading and parsing the config file twice. Though it’s likely to be very low cost to do that (assuming a local, simple config file on the filesystem), it still feels wrong. Besides, what happens when you run into a situation like this and the base set of data (e.g. what load_config() is returning) is expensive to generate?
There are a couple things we could do here: we could create a config attribute, make it lazy and load the config, then change our attributes to pull their value out of the config attribute; we could create a new class to handle the config, and setup a config attribute that delegates to it; etc, etc. That’s a lot of work, however, and work that doesn’t need to be done if we leverage other parts of Moose correctly.
One of the easy, often overlooked ways to do this is to use the tools Moose itself gives us: native attribute traits and accessor currying.
In the above, we see one attribute being created. Note the “is => ‘bare’”; this keeps the attribute from generating the reader, writer or accessor methods. We’re applying the “Hash” native trait, and using the delegation it provides to create custom accessors that pull from the hash without needing the end user to provide keys to a generic lookup.
Note that with either of these approaches gives us the same interface to someone using our class:
This isn’t always appropriate, but if you ever find yourself with multiple attributes whose values can all be generated through one builder, then this may be a good starting approach.