On 12 Apr 2017, at 16:21, Ryan Schmidt wrote:
> If you want to get this fix right now, before the next version of MacPorts is
> released, the official way would be to check out the master of the repository
> and build the whole thing from source.
Oh well…from what I gathered in history, last fi
> On Apr 12, 2017, at 09:01, db wrote:
>
> On 12 Apr 2017, at 11:02, db wrote:
>> On 12 Apr 2017, at 01:19, Ryan Schmidt wrote:
>>> That sounds like a bug. We probably didn't test the change with shell mode.
>> #53967, I hope I filed it correctly.
>
> That was quickly fixed. Should it be fine
On 12 Apr 2017, at 11:02, db wrote:
> On 12 Apr 2017, at 01:19, Ryan Schmidt wrote:
>> That sounds like a bug. We probably didn't test the change with shell mode.
> #53967, I hope I filed it correctly.
That was quickly fixed. Should it be fine if I replace the binary, right?
On 12 Apr 2017, at 01:19, Ryan Schmidt wrote:
> That sounds like a bug. We probably didn't test the change with shell mode.
#53967, I hope I filed it correctly.
> On Apr 11, 2017, at 13:18, db wrote:
>
> After installing a port with notes, these show after every command during the
> same shell mode session on port 2.4.1. Is there any way to disable this great
> feature?
That sounds like a bug. We probably didn't test the change with shell mode.
After installing a port with notes, these show after every command during the
same shell mode session on port 2.4.1. Is there any way to disable this great
feature?
