Hi all,
during the last days I worked on a spell check plugin and here we go.
It checks the content of the current document in Geany with
the spell check program Aspell. You can also select a certain text
passage, then the plugin will only check the selected text. All lines
with misspelled words are highlighted with a red squiggly underline and
the wrong words are printed in the messages window at the bottom of
Geany together with available suggestions. For the plugin to work at
all, you need to have the Aspell library installed together with at
least one dictionary. The plugin's configure dialog lists all available
languages/dictionaries which can be used for the spell check.
It requires a recent SVN version of Geany to compile and load, at the
time of writing, revision 2590 should be good.
Website:
http://geany-plugins.sourceforge.net/spellcheck/
Downloads:
http://geany-plugins.sourceforge.net/spellcheck/spellcheck-0.1.tar.bz2
or
http://geany-plugins.sourceforge.net/spellcheck/spellcheck-0.1.tar.gz
Subversion checkout command:
svn checkout
http://geany-plugins.sourceforge.net/svnroot/geany-plugins/trunk/spellcheck
There is still much room for improvements, like the ability to
automatically replace misspelled words with a chosen suggestion or to
add words to user dictionaries.
If anyone wants to work on this or want to maintain this plugin in the
future, just contact me (I will otherwise).
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Thanks, that does just what I want.
> From: Enrico Tr?ger <enrico.troeger(a)uvena.de>
> Subject: Re: [Geany] key bindings request
> To: geany(a)uvena.de
> Message-ID: <20080518144725.ba24b8f7.enrico.troeger(a)uvena.de>
> Content-Type: text/plain; charset="us-ascii"
>
> On Fri, 16 May 2008 13:56:54 -0500, Thomas Stover
> <thomas(a)wsinnovations.com> wrote:
>
> Hi,
>
>
>> There should be an option for switching focus to the compiler output
>>
>
> it wouldn't be a big deal to add it.
>
>
>> area. Especially in light of the fact that you can arrow key up and
>> down the list. For example, wouldn't it be cool if you could: make;
>> change focus to make output; arrow through the errors; then jump to
>> the relevant source line; repeat - all with no mousing around.
>>
>
> But the desired feature is already available in an even easier way:
> Next Error. It's a menu item in the Build menu and it jumps to the file
> where the next error of the build output is.
> You can assign a key for this, too.
>
>
> Regards,
> Enrico
>
>
Hi.
Just encountered this.
Open Geany. Open a sql file (ending in .sql), make any change and press
F5.
Geany crashes immediately. If you save the file and then press F5 the
projects script runs without a problem.
I'm running Geny 0.13 on Ububtu 8.04.
Cheers
--
Javier Vilarroig Christensen
X Infor
sip:javier.vilarroig@ekiga.net
mailto:javier.vilarroig@gmail.com
There should be an option for switching focus to the compiler output
area. Especially in light of the fact that you can arrow key up and
down the list. For example, wouldn't it be cool if you could: make;
change focus to make output; arrow through the errors; then jump to the
relevant source line; repeat - all with no mousing around.
Keep up the good work.
I contacted the main developper of Geany to ask him if integrating a PHP
Debugger in Geany was planned. Unfortunately, there is no plans for this.
I would like to have this in Geany since it is the only primary thing
that prevent Geany from beeing a major PHP IDE to my opinion. It has
many advantages over other IDE's i used for PHP : straight foward &
simple, fast, lightweight, not too many dependencies (easier for cross
platform), fit for more than one language.. etc. I think you know the
advantages....
I have basic knowledge in C++ so i don't think I would be able to do it
myself but with some help I would be glad to participate in this project
if someone is willing to this.
However, here are some explanations on how a debugger works, what work
should be done to integrate this into Geany
First of all, a PHP debugger is an extension your load in the php.ini
file on your PHP developement server as usual extention for PHP. There
are mainly 3 debuggers available for free to install on your web server :
- xdebug (free open source) http://xdebug.org/
- zend debugger (free, not open source)
- DBG (free open source) : http://sourceforge.net/projects/dbg2
These debuggers opens a port on your test server ie. Zend Debugger (the
one I used the most) opens normally port 10000. It uses this port to
communicate with the app ie. Geany (with the client debugger running in
BG) to listen to where breakpoints should be. It also sends stack
information, current line, current file, etc. like a normal debugger would.
On unix, a PHP debugger is normally a .so file (shared object). On
windows, a DLL file. The .so or .dll file must match the PHP version you
are using. Only the main version and sub version must match. ie PHP
5.2.25 would need a debugger named xxx.5.2.so for unix/linux. This is
for the server part. Not all debuggers provides different versions for
different versions of PHP... DBG for example supports all major PHP
versions with the same DLL or .SO. Zend however do provide different DLL
or SO for all PHP versions
I dont know the internal mechanics of the debugger but I know how to
install it. However, the free debugger DGB would be a nice way to
introduce PHP debug into Geany since it is open source. Also, PDT for
eclipse supports Zend Debugger and I'm pretty sure it is open source (so
is Eclipse!) so we can see how to do it (unfortunately in java..so a bit
of java understanding is needed here).
In order to add this functionnality in geany, these must be implemented :
- A communication channel between the debugger & Geany.
Perhaps there is a client & server part for each debugger.
In DBG, a command line utility is available to debug a page without an
apache server.
Starting to debug a page on apache server is done this way by url call:
http://myhost/mydir/myscript.php?DBGSESSID=1@clienthost:7869
Just appending the green part to the url fires up the debugger...
or by the commandline this way :
dbg
>set mode on
>set mapurlroot http://localhost/
>set mapremoteroot /usr/local/apache/htdocs/
>set maplocalroot /usr/local/apache/htdocs/
>file /usr/local/apache/htdocs/myfile.php
>run
>break /usr/local/apache/htdocs/myfile.php:12
>cont
DBG have a DBG-cli as a client you can capture command line output in
Geany & interract with the debugger in background.
Communication between app & debugger may vary from one to another... not
sure it is always as DBG does...
- Stack pannel : Displays variables values, expandable object structures
& values within objects, ...
- Watch pannel : displays infos about a variable each time it encounters
a breakpoint.
- Local stack (normally presented as thumbs in the same pannel as stack.
- Output view (optionnal but useful)
- Errors view... the errors PHP encounters while parsing the page.
- A browser plugin for firefox (similar to zend toolbar, a must have. I
guess I could do that, its in XML... so I'm ok with this !). This
plugins allows a browser to start a debugging process & opens the file
in Geany.
- A debugger configuration dialog. Sets the base path of the server so
files are converted tu urls by the app when you start debug from the app.
- A setting to automatically add breakpoints on first line & ending line
of a script.
- A clear all breakpoints setting
- A clear all breakpoints in project setting
- A test debug connection functionnality (tells if the debugger works)
- A port setting to change the port used (don't know how this might work...)
- The ability to bind a key combination to hide all debugger pannels
(they take a lot of screen space and have to be showed & hidden often)
In the edit area :
- Clicking on a line number toggles a breakpoint. Normally visible by
changing bg color of that line.
- When a breakpoint is reached, the BG color of that line must change to
something really visible.
- As PHP debugger goes into included files, files containing a
breakpoint should automatically open & have focus
- While debugging is stopping on a breakpoint, you should be able to add
other breakpoints in any file live (without restarting debugger)
I know that the app ie Geany has to controls the debugger. For example
you normally have a play button, a step into, step out & a stop buttons
to control debug progression. The app must send a signal to the debugger
port/or hidden commandline to tell continue to it. In DBG it is a
command issued on the command line in an hidden shell...
I'm pretty sure all the vars are not queryed by the app. Ie. the app
dont know which vars should be in the stack. Instead the debugger send
all vars & values to the app. & the app displays them blindly.
* For local & general stack views, I think the app must do something for
this... I'm presuming the app must know in which object/function we are
and filter the stack data to reflect the local view... not sure after
reading a bit on DGB thought.
* I never looked into a debugger code neigther I unsterstand how the
communication works between the app & debugger so I am making
assumptions here (where there is a * before a line)...
Other infos you might find useful :
- I never saw a PHP debugger run fast. Is is all slow, I suspect the
debuggers from being coded in an awful way...
- Only one debugger can run on a PHP install. That means that if you
install one by loading the extension in your PHP.ini file, you have to
remove it & load the extension for the second, then restart apache to
make it work.
- Zend Debugger : I came across a couple of innacuracies with Zend
Debugger particularly in complex PHP apps. A script was not working, a
bug in there somewhere maked it stop. I debugged this script with Zend
and it passed throught it without an error. So I am suggesting to take
another debugger than that one or add multiple debuggers possibility to
Geany (this feature is not present in any IDE I saw, would be nice thought).
- There is a toolbar for firefox to use with DBG debugger (from
NuSphere) so this a bit less work !
- DBG is free and has been in the market for a long time... as long as
Zend Debugger.
- xDebug is fairly new
- I heard bad & good comments with xDebug but never tried it. Seems like
it is not ready for stability & accuracy yet. However it may have
evolved since these comments.
That is all I can think of right now...
I'll check if I can find a more in depth doc about how to communicate
with a debugger in the point of view of Geany. There is a brief view of
how to communicate with the debugger in the DBG CLi sources in the
readme file...
I attached you DBG C++ source code so you can see by yourself...
Included DBG CLI (client commandline)
& DBG (server part)
Let me if someone is interested in doing this plugin for geany...
I personnaly would choose DBG for the debugger but that should be more
discussed before doing anything.
--
Cordialement,
Emmanuel Morin
Président
Inside a C/C++ block comment, geany insists on prefixing each new line
with " * " characters, which has been driving me batty. How can I disable
this behavior? I don't want these characters, so I end up having to
backspace over them for every new line I type.
Hello World,
I have a question and a problem about the VC diff plugin
1) Question: Is it possible (it doesn't to be so at the moment, so maybe
planned) to configure an external diff viewer to start instead of the
version control diff?
2) Problem: If I try the VC Diff plugin in Windows, I get a message that
it cannot read the diff output (Kann die Ausgabe von "diff" nicht
einlesen). It is version 0.14 for Windows, under Windows XP; we use
CVSNT (http://www.cvsnt.org/wiki) for version controlling (it is more or
less compatible to standard CVS. Any tipps to make it working?
Best regards
Andreas
--
("`-''-/").___..--''"`-._
`o_ o ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' .'
(il).-'' (li).' ((!.-'
Andreas Tscharner andy(a)vis.ethz.ch ICQ-No. 14356454
Dear Geany devs,
I'd like to display line endings, but I find the current [LF] display
rather ugly. Can this be replaced by the same character as the 'Line
Wrapping' one?
I also found a small display bug in the 'Line Wrapping' function: the first
character on a new line moves the 'long line marker' one char to the right.
|
This line |
-is wrapped | <- one char shifted to the right
|
Cheers!
-H-
I've enabled the visibility of spaces (these small dots). If I mark some line now (Shift+Cursor), the block isn't solid anymore. The background of the spaces does not change within the block mark.
Is there a way to change this? It is really confusing because I can't see, if the indentation of a line is marked too.
--
Email: Joerg Desch <jd DOT vvd AT web DOT de>
Hi.
I've called my fresh backport from the command line today. Here I see these messages.
(geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed
(geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed
(geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed
(geany:10536): GLib-CRITICAL **: g_key_file_load_from_file: assertion
`file != NULL' failed
What's the reason for them? My backport? Or the old configuration file of my previous Geany 0.12?
--
Email: Joerg Desch <jd DOT vvd AT web DOT de>