[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49571] Command-c and command-v aren't default
From: |
John Swensen |
Subject: |
[Octave-bug-tracker] [bug #49571] Command-c and command-v aren't default cut/paste in editor (and command-v doesn't work even when changed in preferences) |
Date: |
Fri, 19 Jan 2018 02:32:16 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.99 Safari/537.36 |
Follow-up Comment #21, bug #49571 (project octave):
I am going to pick this one up again, but would ask in the last 4 months
whether we can now assume that we are using QT5 for all MacOS builds? If that
is the case, it makes the solution a lot more simple.
@bpabbott You made it sound a while back that you were still building with QT4
with Fink (not sure if <4.7), but you recently gave me scripts for Homebrew
with QT5. Fink doesn't even look like it has a default package for >Octave
3.8. Both Fink and Macports have version 4.8+ at their qt4 version, so I think
we are safe to assume that every MacOS package manager is shipping >4.8.
So, unless anyone has objections, I am going to proceed by modifying any
MacOS-specific sections under the assumption that Octave is being built with
QT >4.8. Does anyone have any objections to this assumption?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49571>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #49571] Command-c and command-v aren't default cut/paste in editor (and command-v doesn't work even when changed in preferences),
John Swensen <=