Great work on Geany. It's by far my most favorite text editor. A few minutes
ago with the help of dmaphy on IRC, I was able to make it a bit more awesome
for me by having it execute .m files on octave the way it does with python.
All I had to do was add:
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
# (use only one of it at one time)
run_cmd=octave -q "%f"
to the end of the file ~/.config/geany/filedefs/filetypes.matlab, that would
execute the script on octave if it's installed. I was wondering if this
could be added by default.
Octave is a pretty decent matlab-compatible free tool (
So, what do you guys think?
Had spare time this week end, so I started working on a little project...
If some of you use Gedit on Linux, Textmate on Mac, or E texteditor on Win,
you may be familiar with the concept of multi-edit....
if not check this video:
the author of the Multi-edit plugin for gedit)
it's one the feature of gedit that really DO save me some time...very nice
for small refractoring...
the closest thing approaching in Geany (and basically all scintilla-based
stuff I believe...) is the zero-width rectangular selection...
you'll find a patch for editor.c for an embryonic start on this....
the code is awful I reckon...just a draft...
the idea behind it is:
you click somewhere you want to edit...
a subsequent Control+Atl+click somewhere will start a multi edit session...
and keep storing these positions...
if you add a char, and multi edit is on, it will appear to all positions
stored before (this is happening is on_char_added)
if you delete, it was a bit more complicated as handling the message
SCN_MODIFIED gave weird result....so basically i added a
callback on the delete key...that will call on_char_deleted....deleting at
all mult edit positions...
a regular click will cancel the multi edit session...
for the moment I only implemented the case where multi edit positions are
below the first editing positions (adding and deleting are moving positions
around...and it's not easy to keep track of these movements...)
there is no indicators showing the other editing positions...(trying to find
how to change locally the background of the editor)
I need to implement more protections (ex: for exemple, if you change the
document with keyboard shortchuts, and dont click anywhere at all, multi
edit is not erased, causing pb)
would probably nice to implement to start a session without mouse...
refine the whole thing to sum up :D....
you can try it out nevertheless and point out what i missed
Hi at all...with this message I would do a request if is possible...
When a comment line, you can do so through a combination of keys????
With JCreator is possible through Ctrl-E for comment...and Ctrl-D for
Sorry for my bad english..
I'm happy to announce a new version of GeanySendMail plugin, a little
plugin for Geany to send a document as attachment using the preferred
This release is just the second maintenance release of plugin depending
on Geany 0.16 and above and includes some minor changes:
* Code cleanup
* Adding an abort botton to recipient’s email address dialog.
I've uploaded the source code package as well as updated the website.
Frank Lanitz <frank(a)frank.uvena.de>
I just wanted to leave a note for everybody who is not reading the the
svn mailing list. I've just upgraded the minimum dependencies for Geany
plugins project to 0.16 since most of the included plugins will not
compile with any version below. Please note, I only did the change on
waf build support. Plugin maintainer that are using autotools needs to
update the dependencies on their own ;)
I have been looking at the implementation of the build-system and in
particular interactions with other parts of Geany. In general it looks ok,
but the latex menus and commands system seems to have a few interactions
with the build system and menu.
Since the new build-system allows the menu labels to be changed, (not just
the commands) if I allow two run commands can we bring the latex build
system back into the normal system?
This has the advantages:
1. removal of lots of nearly duplicate code building menus, dialogs and
2. much simpler and cleaner build system (I'm not all that altruistic, this
means that it is easy for me to see what I might break with my changes ;-)
Can anyone point me at any glaringly obvious problems that I've overlooked?
A couple of month has been passed by but now I'm happy to announce a
new major version of GeanyLaTeX for Geany 0.16 and above.
Since 0.3 a lot of changes has been done:
* Adding a toolbar with often used format commands
* Adding a configuration dialog to configure basic options of plugin
* Moved documentation into a TEX-document; Include a precompiled pdf
and html version into source tarball
* Replace \u-UTF-8 letters by octal coded chars to don’t depend on C99
* Added a function to bulk replace special characters inside marked
text by keybinding
* Added a function to replace special characters on typing
* Update of German translation
This release of GeanyLaTeX is depending on Geany v0.16 and should also
work with Geany 0.17 without problems. Versions below are not supported
at the moment.
I've uploaded the source code as well as updated the website.
Happy TeXing and feedback is welcome ;)
Hello Geany developers,
I just wanted to say a few words about the editor customization (syntax
highlighting and the likes)...
While the possibilties of customization are good already (and probably more
I always somehow missed the possibility of defining different fonts/size for
It's not so important, so I let it go, until I used SciTE for a while...and
passed to level of customization
that was such a luxury that it was hard to let go...
Now, it might have been obvious to most of you but I figured since Geany use
scintilla as well, it must have the same possibilities
and sure enough with some hacking of the source, i got where I wanted...see
screenshot to have a better idea
multi-font/size possibilities, perfect dark background for the folding bar,
bigger choice of markers, size of the margins...
it's not much but it counts in the long run...
and geany is even better than before in my eyes now....
Now, to the main point, I understand the aim of developing a lightweight
sober IDE....so right from the bat, confusing the user with millions of
possibility of customization might not be suited...
I'm kinda testing the water here...if this extra customization matters to
people, I could clean up my hacks...and come up (or anyone willing to) come
up with a system to implement it...
in any case, it would be nice to have this possibilites mentionned in
Hacking Geany at least...I'm sure some people would be glad to find the
Sorry for no progress, Ive been busy finishing off work as my contract ends
at the end of the month (TODAY!!!).
Now I will have time to finish what I set out to do for you since it is
likely to be a while before the next contract starts.
I just committed to build-system a change to add a build commands tab to the
project properties dialog to save project commands from.
To save you building the branch, I've attached a screen shot. The XXX will
of course have the correct filetype when some code gets behind the dialog.
I propose to use the same for the Build menu 'set build commands' (or
whatever we are calling it) dialog.
After some thought I propose to put the error regex in both because as you
change the compiler it is likely that you may need to change the regex. So
having one associated with each set of commands is useful.
I appreciate that there will probably be no comments til after the 0.17
release. I'll just keep plodding on.
PS Enrico, I can't help with the Addons problem since I am Autotools
illiterate, I didn't even *look* in configure.in or I'd have seen the todo.
Some of these build-system changes are to allow me to use alternatives to
I was thinking of making a vim syntax reader as a plugin. It would be nice
to start out small by only implementing the adapter that would read the vim
file and translate it to set the appropriate formatting on the currently
active document only. If the plugin goes well and is used often, it may be
possible to implement it in the main project and allow the vim reader to act
like a built in language.