Suppose, not hypothetically, that you have found a useful Goprogram but when you test it youdiscover that it has a bug that's a problem for you, and that afteryou dig into the bug you discover that the problem is actually in a separate package that the program uses . You would like to try todiagnose and fix the bug, at least for your own uses, which requireshacking around in that second package.

In a non-module environment, how you do this is relativelystraightforward,

Suppose, not entirely hypothetically, that you have some sort ofspiffy program that wants to use Control-Cas a key binding to get it to take some action. In Unix, there aretwo ways of catching Control-C for this sort of thing. First, youcan put the terminal into raw mode , where Control-Cbecomes just another character that you read from the terminal andyou can react to it in any way you like. This is very general butit has various drawbacks, like you

One of the things in the Go 1.13 release notes is a little noteabout improved support for go.mod . This is worth quoting inmore or less full:

The GO111MODULE environment variable continues to default to auto , but the auto setting now activates the module-aware mode of the go command wheneverthe current working directory contains, or is below a directorycontaining, a go.mod file — even if the current directory iswithin GOPATH/src .

The important safety note is

In my recent entry on writing Go with Emacs's lsp-mode , I noted that lsp-mode or more accurately lsp-ui has a 'peek' feature thatwinds up letting you jump to a definition or a reference of a thing,but I didn't know how to jump back to where you were before. Thestraightforward but limited answer to my question is that jumpingback from a LSP peek is done with the M-, keybinding (which issurprisingly awkward to write about in text)

Over on Twitter, I said :

Today I was unpleasantly reminded that CentOS 7 (still) doesn't shipwith any version of Python 3 available. You have to add the EPELrepositories to get Python 3.6.

This came up because of a combination of two things. The first isthat we need to set up CentOS 7 to host a piece of commercialsoftware, because CentOS 7 is the most recent Linux release itsupports. The second is that an increasing number of our localmanagement tools are now

Now that Go 1.13 has been released ,we're moving that much closer to a module-based Go world. I've become cautiously but broadlypositive towards Go 1.13 and this shift ( somewhat in contrast towhat I expected earlier ), and I'm probablygoing to switch over to Go 1.13 everywhere and move toward modulesin my own work. Thinking about working in this environment has leftme with some questions.

Let's suppose that you have some

As part of their user interface, many programs these days have someway to jump around (or navigate around) the information they display(or portions of it, such as a help system). Sometimes you do thisby actually clicking on things (and they may even look like weblinks); sometimes you do this through keyboard commands of varioussorts.

(The general common form of these is that you are looking at onething, you perform an action, and you're now looking at anotherthing

We have a Python program to log mail attachment information forExim . Oneof the things it does as part of looking at attachments is try tolook inside various sorts of archives to find out what sort ofthings are in there (occasionally the answer is interesting ). Back in the summer of2016, I added the ability to look inside RAR archives using therarfile module , in addition toZIPs and tar files (for which I was using the standard library'smodules). At the time

As part of my casual Internet browsing, I recently read 6 Lessonswe learned when debugging a scaling problem on GitLab.com . Assort of an aside (although listed as a lesson), the article mentionedWireshark's Statistics menu and how it can show you per-conversationinformation (and thus let you find specific sorts of conversations,such as short ones). I didn't think about it much at the time, butthis mention stuck in the back of my mind (as such things often