The following three of the provided services don't work:
dpaste.de
fpaste.orgtinypaste.com
Maybe some URL has to be adjusted in the configuration or if they don't have any API for this any more, they should be removed.
--
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-plugins/issues/548
Purpose:
* do not show info bar asking about reloading if file hasn't changed.
I have copied the logic from `document_reload_prompt`, however I am not sure about the following:
* would the same logic apply? (I did a copy/paste)
* is it safe to ignore the result of `document_reload_force`?
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1463
-- Commit Summary --
* Do not show reload info bar if file hasn't changed
-- File Changes --
M src/document.c (32)
-- Patch Links --
https://github.com/geany/geany/pull/1463.patchhttps://github.com/geany/geany/pull/1463.diff
--
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/pull/1463
I have noticed that there are no UI tests in this repository, nor upstream at major distros.
autopilot seems to be the best choice for GTK-based applications, for an example see http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-autopilot-tests/trunk/v… (there you can browse tests for other applications like firefox etc)
* would Geany benefit from such tests? is this repository a natural and correct place to add them?
* shall a Github project be opened to track this?
* can we easily integrate such tests in Travis PR builder by using some fbdev-based container or qemu?
Obviously I think there would be some benefit, as regression tests can progressively be added during development. I can probably be of help to bootstrap the GH integration to make this happen with some dummy tests, but I would likely not have the momentum/desire to add hundreds of tests at once and rather expect that new developments on the UI front would also add some autopilot tests for completeness (if that becomes an accepted good practice).
--
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/1462
I was looking for autocomplete support that would be aware of all relevant Go packages (in GOPATH, in project and vendor'd); I played a bit with ctags but couldn't get anything out of it.
So here I am proposing to add autocomplete support through [gocode](https://github.com/nsf/gocode) which is pretty much what other editors use (although I find gocode buggy itself, but that is another topic).
## General idea of this PR
* we would need an option to use gocode, either enabled or disabled by default; possibly gocode port too in case you're running multiple gocode daemons
* once this feature is enabled, the `autocomplete_scope` radically changes behavior and instead of using `tm_workspace_find_scope_members` it would rely on a gocode CLI call for each autocomplete resolution request (yes, pricey, but useful)
* the gocode CLI call receives the current buffer text via stdin and the results are parsed into `TMTag` structures
* once tags are generated the autocomplete feature is pretty much unchanged (I am thinking of adding something for calltips, but not sure yet)
By the way, nice work with the block folding feature, I just noticed by compiling master.
## Feedback request
Please notice this is a few ours work (kind of a POC), but I would like to have early feedback.
## Known issues of this PR
* the tag creation should be improved and possibly moved to tagmanager (please advise on that)
* the feature should be configurable and better packaged
* not much used to C/GTK, so I don't even know how many leaks I am introducing here (possibly need to check with proper debug options or valgrind)
* will adjust to proper coding style (yes I noticed the style you are using)
It works already (in this shaky version), see screenshot:
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1457
-- Commit Summary --
* Preliminary work to add gocode support for autocomplete
-- File Changes --
M src/editor.c (242)
-- Patch Links --
https://github.com/geany/geany/pull/1457.patchhttps://github.com/geany/geany/pull/1457.diff
--
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/pull/1457
In Geany for Windows: There is a wrong behaviour of accented
letters (e.g. Czech keyboard) when Caps lock is on: All accented
letters like ě, š, č, ř, ž, ý, etc. are lower case while they should
be upper case. It is known bug in Gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=165385
but it was recently fixed and the fix was already released
in Gtk+ 3.22.7 - see
http://ftp.gnome.org/pub/gnome/sources/gtk+/3.22/gtk+-3.22.7.news
Please update the Gtk+ version used by Geany Windows builds
to Gtk+ 3.22.7 to fix this bug in Geany for Windows.
--
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/1374
@b4n Sorry to bother you, but please state in spawn.c that you are the author of the unicode support. It doesn't matter what the exact text will be, as long as it makes clear that unicode was not part of the original code. Thank you.
--
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/commit/a45091413a0dae1bc72546281210674fa250d…
It's in line 28, something nibbled at the parenthesis:
This happens to me in rare occasions time after time. l don't know how to reproduce it.
--
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/1444