utils: output what files edit is opening.

[MikeMcQuaid]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew tests with your changes locally?

---

Since we've moved all formulae to taps it's not necessarily obvious what the path for the files are otherwise.

[UniqMartin]

This doesn't render very nicely if multiple arguments are supplied. May I suggest the following as a replacement?

ohai "Editing:", args

[MikeMcQuaid]

I thought it did render more nicely than that case as it's not truncated and the first argument (the typical case) is displayed on the same line.

[UniqMartin]

Aesthetically, the changing indentation and that only the first line is prefixed with “Editing” for the atypical case is bothering me more, even if the common case becomes nicer and shorter.

But to be honest, I'll probably be slightly annoyed by this output anyway, no matter how it is styled, because I basically never want to know where the formula I'm editing is and when I do, my editor can tell me quickly and efficiently. But I'll certainly manage as I guess this is a minority opinion.

[UniqMartin]

I guess the primary concern are formulae here, in which case something like brew which <formula> or something similar might be more appropriate? Once the file is open (I guess most often in a GUI editor), the path will be obvious from a context click on the editor's proxy icon (and the icon can be dragged to the terminal to get the full path into a command line).

On a side note, but not a serious suggestion for an alternative fix, this will also help:

HOMEBREW_EDITOR=echo brew edit qt5

[MikeMcQuaid]

I guess the primary concern are formulae here, in which case something like brew which or something similar might be more appropriate? Once the file is open (I guess most often in a GUI editor), the path will be obvious from a context click on the editor's proxy icon (and the icon can be dragged to the terminal to get the full path into a command line).

I think this is pretty editor dependent. This is designed to improve the flow for first-time contributors where it might not be obvious where these files are. It's also useful for more regular contributors to have a file path to copy/paste to various other locations outside of the editor (particularly for those editors that don't have a proxy icon).

[UniqMartin]

Yes, I understand the motivation for this PR and I imagine it will help the addressed user group. My needs and preferences are different, but that's not something that can (and should) stop this PR.

[MikeMcQuaid]

Cool, thanks @UniqMartin.