On Mar 6, 2017, at 09:33, db wrote:
>
> I would expect some output without verbose flag like
>
> $ port livecheck [port]
> [port] seems to be up to date
>
> Not worth a feature request, I guess.
I'm pretty sure it's intentional that, like many other unix commands, no output
is meant to signify
I would expect some output without verbose flag like
$ port livecheck [port]
[port] seems to be up to date
Not worth a feature request, I guess.
On 6 Mar 2017, at 15:05, Ryan Schmidt wrote:
> On Mar 6, 2017, at 08:03, db wrote:
>>
>> I meant try with other ports, e.g., emacs
>>
>> $ port li
On Mar 6, 2017, at 08:03, db wrote:
>
> I meant try with other ports, e.g., emacs
>
> $ port livecheck emacs
> $
> $ port -v livecheck emacs
> emacs seems to be up to date
>
> Not all ports give the same output with livecheck without -v.
Ah, I see. Yes, when non-verbose output is empty, it's
I meant try with other ports, e.g., emacs
$ port livecheck emacs
$
$ port -v livecheck emacs
emacs seems to be up to date
Not all ports give the same output with livecheck without -v.
On 6 Mar 2017, at 14:54, Ryan Schmidt wrote:
> On Mar 6, 2017, at 07:53, db wrote:
>
>> Try with emacs.
>
>
On Mar 6, 2017, at 07:53, db wrote:
> Try with emacs.
Sorry, I've never used emacs.
Try with emacs.
On 6 Mar 2017, at 14:47, Ryan Schmidt wrote:
> On Mar 6, 2017, at 07:44, db wrote:
>
>> Do you know of any means that I'm not aware of to make livecheck output its
>> result without -v?
>
>
> There doesn't seem to be any difference in livecheck output when using the
> verbos
On Mar 6, 2017, at 07:44, db wrote:
> Do you know of any means that I'm not aware of to make livecheck output its
> result without -v?
There doesn't seem to be any difference in livecheck output when using the
verbose flag:
$ port livecheck gcc7
gcc7 seems to have been updated (port version:
Do you know of any means that I'm not aware of to make livecheck output its
result without -v?
On 6 Mar 2017, at 13:45, Ryan Schmidt wrote:
>
>> On Mar 6, 2017, at 03:46, db wrote:
>>
>> Is there any way to enable verbose output _after_ entering shell mode with
>> `port`? I'd rather not use
> On Mar 6, 2017, at 03:46, db wrote:
>
> Is there any way to enable verbose output _after_ entering shell mode with
> `port`? I'd rather not use `port -v`, then I get it unnecessarily for all
> commands.
Not that I know of.
Is there any way to enable verbose output _after_ entering shell mode with
`port`? I'd rather not use `port -v`, then I get it unnecessarily for all
commands.
10 matches
Mail list logo