ELLIOTTCABLE

I'm in agreement on a delay being a terrible solution … if it's *invisible*. That is, not a behaviour that's surfaced, visually, to the user. Here's my thought: on click...

@Zodiase :-1: on this — small click/drag targets, like the tiny area of the top bar *not* covered by tabs in your example, are a UX antipattern, and an accessibility...

Although I had some trouble parsing through most of @Onfire7's suggestion, what *looks* like the ‘meat’ of it is definitely :+1: from me: > - Add a large space (75-100px)...

Unfortunately, that's only helpful for the _terminal_, yes? The main issue (since there's lots/various ways to get shell integration working as expected) is that the parent process, the GUI program...

I've tried logging out, and back in, on Dropbox.com; no dice over here. Same problem.

There's no way to set this in a `.shellcheckrc`, is there, since `$HOME` is being expanded by the shell in the above approach? Unfortunately, that workaround doesn't work very well...

:+1:

I also tried to use `pattern-inside` in this rule in a `.yaml`, as a half-measure — unfortunately, it yields "Invalid pattern for OCaml", and I'm not sure why: ```yaml -...

Pending some sort of benchmarking — log in-memory by default, dump to a marshalled log-format somewhere by default, don't include in text-logs; use a flag to decide whether to print...

Since a lot of these are updated thru major releases, did you have a chance to take a gander and see if any of the breaking changes affect their usage...