-
Notifications
You must be signed in to change notification settings - Fork 179
Conversation
…e of possible menubar)
Data is now installed globally Settings have been moved to gsettings/dconf
o_o This is awesome! You'll forgive me if I'll need some time to digest all of it before actually merging, which from what I have seen so far I fully intend to do. I'll be nitpicking around the code a bit about style and minor stuff; ideally, I'll want to merge your pull request unchanged. A few points:
I greatly value your contribution. Tonight, I hope to start a development blog for Final Term to coordinate the combined efforts where I will outline a plan towards an initial, "somewhat-stable" release. I will mention your efforts there. P.S.: The pull request currently doesn't apply to master. I've pushed a few fixes this morning. |
Glad you like it so far! For your P.S., it's actually the first time that I use git, so if I'm required to do something, it'd be great if you could paste the appropriate commands ;) |
You could try to pull again from master ( |
Hi, this patch allows finalterm to build for me on arch linux. Configure works fine:
And it builds fine (ignoring numerous warnings that are extremely common with vala projects), but I get a couple of linker errors.
Edit: seems both libraries are available on my system, they just don't have the soname it's complaining about
|
Would you mind me fixing more stuff in this branch, unrelated to cmake? For example I found the cause of the endless "queueing a relayout is not recommended" warnings, and I'd also like to get rid of all the warnings at compile time, because this mass of output sometimes makes it hard to spot the error amongst the warnings, which makes the compilation fail. If not I'll just wait till the branch's merged and make a new pull request for those :) |
@TomB95: The queuing bug? REALLY? That one's been bugging me for ages, but I never quite felt like going too deep trying to find the cause. Wonderful! As for getting rid of all compile time warnings, good luck. While most of the Vala ones are simply unhandled errors, Vala has numerous bugs that let problems slip through to GCC without it noticing (both warnings and errors, many of them documented in Final Term's source code, which I imagine might become a treasure trove of test cases for the Vala makers). I doubt it is possible to eliminate all warnings. As for all this magic going into this branch... I somehow would prefer if those were separate pull requests made afterwards – which now makes merging the CMake stuff my number one priority, and I'll try hard to get that done tomorrow. Keep going :) |
@TomB95: I looked through the entire pull request and feel confident to merge now, problem is, it doesn't apply to the current master branch. If you can fix that I'll merge immediately, otherwise I'll try manually tomorrow. BTW I noticed tom95@89154e2, if that is necessary for the pull request to work properly feel free to add it. |
Now here's the ugly part: On Fedora, trying to build with cmake, I am getting
If I change "keybinder-3.0" to "keybinder" as in the Makefile I get the same error:
Although keybinder can be found when I run the makefile. Me knowing nothing about CMake, do you have an idea what is going on? |
I guess you haven't made pkg-config aware of the package. You can check that by running "pkg-config --list-all | grep keybinder". It should show keybinder-3.0 then. For the changes, you could either wait for me to come back home in around 10 hours from now or change them yourself when merging if you don't feel like waiting, I agree with all your remarks :) |
I'll be going out now myself and be back in about 10 hours too. I guess we live in the same part of the world :) Will be trying that out then. |
With the current setup, will it work on other desktop enviroments other than Gnome? for example, KDE. If not, then I'd go for the .json file for the settings. Maybe, there should be another bug filed where there can be further discussion about this. |
@varemenos: See #20 (comment) |
Found it:
And WOW, does it work! And how many issues it solves. Turns out that the entire library copying hack can be done away with if the pkg-config search path is pointed to the (unusual) location where the libkeybinder Let's get this merged! |
@TomB95: I'm doing the merge right now, no need for you to fiddle. Will let you know when it's done. |
@varemenos it will run the same way Gedit or basically any other Gtk app would run on Kde. |
Done! |
It got to be a bit more complex than I originally planned.
The terminal now supports (and requires) installing (make install).
The settings desktop file has been removed. Instead, there is a gsettings/dconf replacement, to make per user config easier. The keybindings file would either have to be ported to gsettings as well or be created by the app when a user runs it, or you just leave them the same for all users.
I also moved the file around to make things tidier, we have a cmake folder which hosts the vala related cmake modules, a src folder, which has all the vala files and a vapi folder which has the keybinder-3.0 vapi file. Downloading it manually will no longer be required, except for the library itself of course. (The problem previously was probably that you didn't rename your vapi to keybinder-3.0, so there were some troubles resolving the correct files).
In case you're wondering, the Config.vala.cmake file will be filled by cmake with the requested variables and then put as temporary vala file in the build dir for compilation.
For compilation, just do
mkdir build
cd build
cmake .. # you can add -DCMAKE_INSTALL_PREFIX=/usr, otherwise it will go to /usr/local/share/finalterm
Feel free to change or revert anything you don't like (or reject the entire thing), I'm open for questions or suggestions :)