This is the follow up to #968
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/969
-- Commit Summary --
* GeanyVC: Add support for Fossil SCM (fossil-scm.org)
-- File Changes --
M geanyvc/README (8)
M
I'm using [Fossil SCM](https://fossil-scm.org) with most of my projects, as
it's free, quite lightweight yet mighty just like Geany :). Apart from
distributed Version Control, Fossil also packs Issue tracker, Wiki, Forum, and
Server all in single binary executable. So pretty much all I need for
Thanks for the heads up. I'll have a look to see what can be done. I don't know
GTK so something new to learn on lockdown.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The open dialog is provided by the GTK library, not Geany itself. On my Linux
box it shows a list of available protocols, but maybe GTK on Mac doesn't
provide any such protocols, and hence the red background when you type `:`.
Maybe there is no list because nobody interfaced GTK to the
Just downloaded the latest version for MacOS.
When I click File > Open > + Other Locations and then the green ? I get the
following:
https://user-images.githubusercontent.com/259543/80197654-d50ca680-8616-11ea-9d7a-fe87559769e5.png;>
As soon as I type the ":" in "ssh:" the input field goes
I have downloaded Geany from here -
https://download.geany.org/geany-1.36_osx-2.dmg
After successful installation I want to open Geany from terminal, but terminal
can't find it:
How can
Follow up to previous comment, as suspected, its not possible for plugins to
get the `FILE*` between the write and the close, so no way a plugin can `fsync`
the file. If the functionality is added it will have to be in Geany itself.
--
You are receiving this because you are subscribed to this
You are correct that its a diversion from the issue at hand.
All I did was propose a possible reason why nobody else has seen the problem
(not knowing much about Suse, but assuming a rolling release is bleeding edge).
That possibility may not be correct.
If its a version of VTE thats common
> The so is `libvte-2.9[01].so`, which is how Geany finds it and knows its the
> right API.
sure; yet if you were to reply a bug against libvte-2.91, upstream would have
zero chance to know what you're running; just because API/ABI does not change
in a backward incompatible way does not mean
The so is `libvte-2.9[01].so`, which is how Geany finds it and knows its the
right API.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2457#issuecomment-618873849
of course; but if you refer to vte 2.91, you run into a void as the library
does not exist :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2457#issuecomment-618872066
Ok, Geany only cares about the API of course :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2457#issuecomment-618871553
2.90 / 2.91 are the API/ABI versions of the library - 0.58 / 0.60 are the
source versions as tagged by upstream (both are from the 2.91 ABI tree
https://gitlab.gnome.org/GNOME/vte/-/tags)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
@DimStar77 VTE versions for GTK3 are 2.90 and 2.91, I think your 0.58 is a
_package_ version, not the library version.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Possibly nobody else has seen the problem due to you having a bleeding edge
> VTE version that has changed something for the worse.
So far, openSUSE Tumbleweed was still on GNOME 3.34, hence vte 0.58.3; not very
'bleeding edge' for that component (3.36 merge was slow due to syncup with Leap
15 matches
Mail list logo
