Hi all,
I just made a test build of Geany Plugins 1.22 for Windows.
A little surprisingly for me, it all worked fine on the first attempt :).
I only had problems loading the Geany-Lua plugin with some strange error
message which I didn't investigate yet:
http://pastebin.geany.org/EUmwJ/
The error message occurs on plugin loading. I'm not sure whether it is
caused by my system or something else.
If anyone wants to test it, any feedback is appreciated.
The installer...
http://www.uvena.de/tmp/geany-plugins-1.22_setup_testbuild.exe
... requires an existing Geany 1.22 installation.
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
I want to say, that it would be nice, if a DocumentMap/MiniMap would be added to Geany. Please add it to the Wishlist on your side.
Notepad++ have something called "Document Map":
http://notepad-plus-plus.org/assets/images/docMap.png
Sublime Text have something called "MiniMap":
http://www.sublimetext.com/screenshots/new_theme_large.png
Since some time, Kate have a MiniMap, too:
http://kate-editor.org/2012/11/03/busy-katekdevelop-sprint-results-in-mini-…
All three have a line, where with very small fonts a bigger part of the document is shown and the current visible part of the Textarea have a colored background in the map.
But they differ in additional functionality of it.
Where Sublime Text only shows the MiniMap, Kate on the other side, can replace the scrollbar with it. And on Notepad++ it is a mix between the two. The scrollbar is still there, but you can click in parts of the Document Map, to jump to that position.
An additional point I want to mention, is a bug in your Webside-software.
As I wanted to add this wish to the wishlist, I clicked at the bottom of the page on "edit this page" of the line "(If you have another idea/wish which should be listed here, edit this page)".
Then it asks for a username and password. Because I don't have an account for it, and I find no place to register, I have somewhat input. After that it shows be an empty page and Geany.org was no longer available.
I thought, it would be an coincidental/hazard/fortuity/hap, that that happens.
But now there was again Geany.org reachable, then I tried it again. And again the Geany-side was after that down. :-(
So please update your Geany homepage software. Or it is really a very big coincidental/hazard/fortuity/hap, that in two times the Geany side goes in that time down, I tried to login there.
Greatings
theuserbl
Matthew Brush <notifications(a)github.com> wrote:
> @elextr FWIW, the files `makefile.win32` and `win32env.mk` (and geanypy.nsis for the installer and README.win32 for the instructions) are needed for `src/makefile.win32` to be useful.
>
> @eht16 Any chance you could get some time to try getting the Waf build system working so it can be built on Windows?
Taking cause from Geanypy, there are 2 small problems with $subject:
- no header fiels are installed, or maybe they are copied somewhere
outside the $prefix. Copying the headers manually is OK.
- geany.pc contains paths with single backslashes, and plugins build
fails with "c:path1path2...: no such file or directory". Replacing
with forward slashes works. All other .pc files I've checked under
win32 use forward slashes.
I haven't tried the latest git though.
--
E-gards: Jimmy
Hi Enrico,
We have had a report on IRC that running geany on the windows command
line will only open files in the Geany install directory unless you
use the full path.
eg C:\somepath> geany somefile.txt
will open installpath\somefile.txt not somepath\somefile.txt.
And with the "Open new documents from the command line" option set it
creates somefile.txt in the install dir since it doesn't exist there.
Suspicion is falling on
https://github.com/geany/geany/commit/775ef628688c69de34640e12666aed5762a80…
As the most experienced windowser (and the committer of that change)
could you look at it please?
Cheers
Lex
Hi translators and friends of Geany,
We are on the final lap for a new release: 1.24 is near and will be
release at the second weekend of April. As usual in prior we are having
a phase to update the translations -- and here we are ;)
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next two weeks so we can include it to the next
release. Deadline will be 2014-04-12.
To make it more easy for you I've already uploaded updated versions of
the po files as well as to git master. You can either
download the direct via web or by cloning the repository from
https://github.com/geany/geany-plugins
This can be done e.g. with
git clone https://github.com/geany/geany-plugins.git
Also at http://i18n.geany.org/plugins are statistics and daily updated
files available (updated files by tomorrow CEST)
As mentioned before, we are trying to have all translations complete by
2014-04-12.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
Thanks and happy translating
Frank
Hi translators and friends of Geany,
As with the plugins, we are also on the final lap for a new release of
Geany core: 1.24 is near and will be release at the second weekend of
April. As usual in prior we are having a phase to update the
translations -- and here we are again ;)
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next two weeks so we can include it to the next
release. Deadline will be 2014-04-12.
To make it more easy for you I've already uploaded updated versions of
the po files as well as to git master. You can either
download the direct via web or by cloning the repository from
https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org are statistics and daily updated
files available (updated files by tomorrow CEST)
As mentioned before, we are trying to have all translations complete by
2014-04-12.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
Thanks and happy translating
Frank
Since we are about to produce a new release I propose a change to the
Geany workflow.
More regular releases.
Acknowledging that Geany hasn't the number of contributors that say
firefox has, monthly would seem too often, so instead I propose an 8
week schedule:
- week 4 feature freeze, alpha release for testing
- week 6 string freeze, beta release for testing
- week 7 release candidate
- week 8 THE RELEASE!!!
Then we don't need to be so careful about changes, because problems
only last for a couple of months until the next release, and since
only a few new features will be added each release nobody will feel
that they have lost much if they have to downgrade due to bugs.
I therefore propose that the eight week period should start today April 1.
Happy upgrading.
Cheers
Lex
Hi everybody !
I checked all my PR, didn't see any comment, but they're still not merged
and i don't if there is a reason, or anything else.
Can someone can check them ? :)
I think it would be nice to merge the PR#224, since it already been a
discussed PR !
I know the 2 other PR are maybe not good enough to be merged :)
https://github.com/geany/geany/pull/224https://github.com/geany/geany/pull/219 (make the string more accurate with
PR 218)
https://github.com/geany/geany/pull/218 (let the user choose between
Windows or Gtk color chooser)
Cheers,
Steven Valsesia
Hi guys,
I know everybody is busy with release of geany 1.24 .
Can somebody please find sometime to merge
PR#226<https://github.com/geany/geany/pull/226> so
that it goes to geany release 1.24?
If there is some problem please do tell me. I would fix it asap.
Thanks,
Shankhoneer Chakrovarty
On 14-03-28 10:31 AM, Pavel Roschin wrote:
>>
>>
>> Am 28.03.2014 10:00, schrieb Lex Trotman:
>>> On 28 March 2014 19:46, Frank Lanitz <frank(a)frank.uvena.de> wrote:
>>>> Am 28.03.2014 01:10, schrieb Lex Trotman:
>>>>> The one you made on Geanypy has already been improved by upstream
>>>>> (Matthew) so you should just commit that improvement.
>>>>
>>>> I was planning to have a look onto it Sunday (you mean #116, don't
>>>> you?). But this is not a feature, only kind of a bug fix ;)
>>>
>>> Yep that one, I guess its more a feature since there is no bug (in
>>> Geanypy), more its a bug in cppcheck :)
>>
>>
>> ... well.... puh... At least it's not changing any string ;)
>> However, will do it at the weekend.
>>
>> cheers,
>> Frank
>> _______________________________________________
>> Devel mailing list
>> Devel(a)lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>
>
> Here is definitely false-positeve. cppcheck was confused by a terrible define:
> return operator inside... Without return operator of course here could be a bug.
>
Good static analyzer (eg. clang's static analyzer) can expand macros and
would see the return. Maybe we could/should preprocess the code before
we cppcheck it?
IIRC Py_RETURN_NONE just expands to something like
Py_INCREF(Py_None);
return Py_None;
I'm not opposed to using the full code like this, it's maybe a little
nicer than the "fix" I mentioned in the PR comment, but IIRC there are
multiple places where `Py_RETURN_NONE` and `Py_RETURN_TRUE/FALSE` are
used like this that might also need to be updated.
Cheers,
Matthew Brush
