Atom package

I don't know how many of us use Atom, but I have a very early syntax highlighter here: https://github.com/markemer/language-macports which I am working on. Feel free to suggest things. Also, I'd like to make a plugin for the the linter package in atom as well as some standalone functions. Hit me u

iTerm Upcoming Versions

The upcoming 3.2 version of iTerm2 will require 10.13 or higher to build. The upside is Metal 2 rendering is being working on. I'm wondering if we want to keep older versions based on older macOSes or just say, hey, upstream only supports 10.XX at the latest and so that's what we support. —Mark __

Re: iTerm Upcoming Versions

Hi, 10.13 only would be quite a harsh requirement, so I think limiting iTerm2 to only that would not be good. Do you know why exactly they are doing this ? Is it the Metal 2 requirement, or Xcode or something else ? Sometimes within MacPorts we can support OSes beyond what upstream expects,

Re: iTerm Upcoming Versions

Turns out I'm wrong, it will run 10.10+, but will only build from source on 10.13 due to a Xcode 9.4 requirement. —Mark ___ Mark E. Anderson On Sat, Jul 28, 2018 at 4:53 PM Chris Jones wrote: > Hi, > > 10.13 only would be quite a harsh requirement, so I think limiting iTer

Re: iTerm Upcoming Versions

That sounds like it could be a compiler requirement (c++14 or something like that). If so its something that can be worked around in MacPorts by using a different (non Xcode) compiler… Chris > On 28 Jul 2018, at 10:05 pm, Mark Anderson wrote: > > Turns out I'm wrong, it will run 10.10+, but

Re: iTerm Upcoming Versions

Looking at https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile The port is already limited to 10.12 or newer… I do still wonder if that couldn’t be extended by using the compiler black list p

Re: iTerm Upcoming Versions

I haven’t dug into the code, but that’s a good idea. My worry would be things that XCode gives that are hard to build ourselves like AppKit w/ Swift 4.1. It’s already 10.12 because it will not build in XCode 8 at all. If they use @available or whatever that could be the problem too. Which is a sha