[smacktoward]

> So you have GUI output.

Which seems like it would be a Big Deal, for a Mac user. The entire appeal of the Mac (for a developer) is that it layers a friendly GUI over a Unix-ey foundation. Presumably a user who values that GUI would also value GUI-oriented ways to do things that were previously terminal-only.

If "just use screen" was an answer that would make that user happy, they wouldn't have spent the extra money to buy a Mac in the first place.

[yliang]

The "Show Output" menu of Marathono opens a Terminal/iTerm tab to tail the output. Currently Marathono is designed for start-and-forget kind of processes - outputs are for occasional debugging purpose only.

[vikeri]

Does this have to be the case? I have a couple of long running processes that I would really like to check the output of from time to time. Couldn't you have an option to just show the last line for example? Was super excited to see this as I've been bugged by exactly this but if I can't see the output it's a dealbreaker for me unfortunately

[yliang]

What do think would be a place to show "the last line"? Or would [1] be more useful for your use case? If not, would you mind creating a new issue?

1. https://gitlab.com/marathono/marathono/issues/7

[vikeri]

Posted an issue here: https://gitlab.com/marathono/marathono/issues/10

[noobermin]

That's good to know, I clicked around looking for a hint of whether it did that. Thanks for informing the conversation.

[eropple]

This feels like a caricature of Mac users. I mean, I like solid GUIs for graphical-friendly tasks. But launchd already exists and this doesn't even use that.

[brazzledazzle]

Launchd is a pain in the ass. And a poorly documented one at that. When they changed how it worked in a fundamental way somewhat recently (Yosemite I think) they couldn't even be assed to update their online documentation.

I wouldn't mind if this used launchd under the hood though.