I think just adding something like the "Filter Selection" option of NEdit
would go a long way to solving issues like this. You can select some text,
pipe it into an external command or shell script, and replace the selection
with the output of the command.
For instance, you could use something like this perl script to emulate
the "Justify Paragraph" option:
http://directory.fsf.org/all/rewrap.html
But "Filter Selection" would also allow for all sorts of other user-specific
filters, without adding a lot of bloat to Geany, almost like a sort of "plugin"
or "macro"
- Jeff
PS: Sorry if you got this twice, John - I still haven't gotten accustomed the
geany list not munging the mail headers. All other lists I subscribe to use
a Reply-To:<list> header.
Dietrich Weber
Heidestr. 10
56729 Arft
dietrich-weber(a)web.de
Feb. 20th, 2007
Hi,
using GEANY to write some PASCAL code I wonder if it might be possible
to make the code auto completion non case sensitive. At the moment it
only works when the statements are lower case, not when they are
upcase.
Since the PASCAL code rules do allow the statements to be written in
all possible cases (lower case, upcase, mixed in any way), it would
be a help if the code auto completion would function in all these
ways.
For example: I prefer to write WriteLn instead of writeln, but only in
the latter version the code auto completion works.
This is not of the highest urgency though, but it would be nice.
Greetings from Arft,
Dirk Weber
Hi,
ich benutze GEANY, um damit PASCAL Code zu schreiben. Wäre es möglich,
die Autovervollständigung des Codetextes unabhängig von Groß- und
Kleinschreibung zu machen? Momentan funktioniert dies nur mit klein
geschriebenen Befehlen, bei Großschreibung nicht.
Da die PASCAL-Syntaxregeln zulassen, dass Befehle in allen
Schreibweisen (Klein-, Großschreibung und gemischt) verfasst werden
dürfen, wäre eine Autovervollständigung unabhängig von Groß- und
Kleinschreibung hilfreich.
Beispiel: Ich bevorzzuge die Schreibweise WriteLN statt writeln, aber
nur im letzteren Fall funktioniert die Autovervollständigung.
Das hat natürlich nicht die höchste Proirität, aber es wäre hübsch.
Gruß aus Arft,
Dirk Weber
ps
Schreibt/liest eigentlich hier jemand mit, der auf den Gebrauch der
Deutschen Sprache mehr oder weniger zwingend angewiesen ist? Falls
nicht, ich bin es auch nicht, dann könnte ich es beim Englischen
belassen.
dw
--
dietrich-weber(a)web.de
mail(a)dietrich-weber.de
Hi ...
I have just found this nice little IDE project, and I like the basic
idea of a simple and fast IDE in GTK2.
But I have some questions about your future plans.
In the 0.11 code (from SVN) there is the start of a project manager but
it seems a bit primitive, what is the plan for this project manager ?
Have anyone thought about making it all script able in f.ex. python (or
lua :-)), to make it possible for the script to handle compiler output,
generate Makefiles (from project lists), or make custom script
manipulation ( and in the mean time keep the overhead down) ? I know
this is not a new emacs, but scripting is a very strong feature if done
properly :-)
I realize that if this have to remain a small application, it need to
keep features (and init time) down, but this could be some nice and
strong features, that only cost if used.
I am looking forward to see how this project unfold :-)
Regards
/BL
Hi
First of all, once more the biggest of all compliments for geany. My
eternal search for a simple, functional, and featurefull editor at last
has come to and end and I just can't imagine life without it anymore, at
least not life as a programmer.
The only thing that irritates me at the moment is the comment
autocompletion, for c-style comments, in c and e.g. php.
If I start a line with
/*
and then press enter four times, this will result in the following output:
/*
*
*
*
This is not really what I would like, I'd prefer geany not to put any
asterixes for me (and if, then at least consistently on the first or
second column). Switching off autocompletion does not seem to help.
Would it or is it already possible to be able to switch off this behaviour?
Bye
Tim
OK, here's what I want to do: I want to add some syntax highlighting for
Lua, but I'm not sure how (or if I even can).
Here's what I've tried:
1) Making a filetypes.lua file
2) Adding a line (Lua=*lua;) to my filetype_extensions.conf
...
Well, that obviously didn't work; so my question is How can I add support
for more filetypes, if I can at all?
Thanks in advance!
--
Cory Burgett
~
~
:wq
Hello,
After an update today, I tried to compile geany (r1309), but it failed.
The problem appears in the configure script:
andy@shannara:~/Programming/Projects/geany$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
andy@shannara:~/Programming/Projects/geany$ gcc --version
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Best regards
Andreas
--
("`-''-/").___..--''"`-._
`o_ o ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' .'
(il).-'' (li).' ((!.-'
Andreas Tscharner andy(a)vis.ethz.ch
http://www.vis.ethz.ch/~andy ICQ-No. 14356454
Hi all,
We've just committed a HACKING file to SVN with information for new
contributors, or anyone interested. It hopefully explains all the basic
things about the code such as:
Patches
File organization
Glade
C coding
Coding style (not compulsory but it helps us)
Libraries
http://svn.sourceforge.net/viewvc/geany/trunk/HACKING?view=markup
There may be things we've not explained, so feel free to ask on the ML
or by email.
Also there are now short descriptions of the src/*.c files under each
file header. These things should help explain the structure of the
project.
Regards,
Nick