On Jul 18, 2018, at 14:17, Richard L. Hamilton wrote: > But...as soon as I tried to run it, it popped up its own updater telling me > that 3.1.7 was available. Now I know enough NOT to use a non-MacPorts > updater on something installed via MacPorts, but IMO, the MacPorts build > really should (if there's a way to do it) disable the built-in updater, so as > not to tempt people to do the wrong thing. Yes; by all means file a ticket about that. > Presumably that also means it might be nice if someone updated the port to > 3.1.7. :-) Yes. Someone has already filed a ticket: https://trac.macports.org/ticket/56779
- iTerm2 and High Sierra 10.13.6 incompatible... Comer Duncan
- Re: iTerm2 and High Sierra 10.13.6 incompatible..... Eitan Adler
- Re: iTerm2 and High Sierra 10.13.6 incompatib... Mark Anderson
- Re: iTerm2 and High Sierra 10.13.6 incompatible..... Ryan Schmidt
- Re: iTerm2 and High Sierra 10.13.6 incompatib... Comer Duncan
- Re: iTerm2 and High Sierra 10.13.6 incomp... Richard L. Hamilton
- Re: iTerm2 and High Sierra 10.13.6 incomp... Ryan Schmidt
- Re: iTerm2 and High Sierra 10.13.6 in... Comer Duncan
- Re: iTerm2 and High Sierra 10.13.6 incomp... Richard L. Hamilton
- Re: iTerm2 and High Sierra 10.13.6 in... Ryan Schmidt
- Re: iTerm2 and High Sierra 10.13... Richard L. Hamilton
- Re: iTerm2 and High Sierra 1... Mark Anderson
- Re: iTerm2 and High Sier... Richard L. Hamilton
