Hi All,
A question for the Geany translation/intltool expert.
I have been creating a Latex filetype file for the build-system branch which
contains labels for the menu items which need translation, "View PDF File"
and "View DVI File" for example.
The filetype is read in a locale sensitive manner and should load any
translations that are in the file, and my reading of the intltool
documentation leads me to believe that it should be able to extract marked
entries from config files like filetype.latex and include them in the
translation process alongside the source code strings and then merge the
translations back into the config file.
What I can't work out from the documentation is how do I tell intltool to do
it. I read it as it will include desktop.ini and other known files but it
doesn't tell how to include other files. X-S
Can anyone help please.
Cheers
Lex
Hi,
I have a really strange problem with Geany.
Using Geany 0.17 standard install on open suse 11.0, logged in as a
different user to where I was developing Geany so there is no leakage
from development versions.
When typing 's' the save as dialog pops up?? I have a keybinding
<super>s for save as but undefining it didn't fix the problem but it
did let me check that <super> isn't stuck on. It seems to depend on
Geany a <super> keybinding existing when Geany is opened.
I can turn the problem on and off by closing Geany with the <super>s
keybinding defined and next time I open Geany typing s invokes the
keybinding.
If I undefine the keybinding and close and re-open the problem has gone away.
Its like the <super> is permanently defined so when there is a
keybinding using it then typing just the character s is interpreted as
<super>s.
I tried defining several <super><character> keys and all of them react
the same way, when first defining the keybinding all is well, but on
closing and re-opening Geany the strange behavior starts. Removing
the keybinding does not fix the problem until Geany is closed and
re-started. So the problem may be in the load of keybindings.
~/.config/geany/keybindings.conf contains the <Super>s as expected.
Cheers
Lex
Hi all Geany developers,
I am new to the geany-plugins project and just added my new plugin, called
"Code navigation", which aims at facilitating common operations
like switching from a header to the implementation or directly opening a
file by typing its name.
Hi all,
I've created a basic Scintilla lexer for the Markdown formatting syntax
along with Geany syntax and tag support. It doesn't do everything;
indented code blocks and embedded HTML aren't highlighted, but it's
already very useful. Some extra highlighting features are added for
the Pandoc implementation: strikeout, using '#.' as a default ordered
list item marker, and delimited code blocks.
Patch against build 4026 with -p5 from Geany's top build directory.
This was built and tested on Linux.
Cheers,
Jon
Hi All,
The first alpha release of a version of Geany with flexible configuration of
the Build Menu is available in the build-system branch of svn,
https://geany.svn.sourceforge.net/svnroot/geany/branches/build-system/
This release is still under active development (see Known Bugs, Limits and
Incomplete below) and is released to allow consideration of the
functionality and how it might impact/assist other Geany activity.
Some of the highlights are: (see the Build Menu section in the manual for
the gory details)
- Both build menu labels and commands are configurable
- Configuration sourced from project if open, preferences, filetypes,
defaults (in that order)
- The maximum number of items in each section of the build menu is
configurable
- Unused items are hidden
- New configuration dialog in the build menu (for preferences configuration
source) and the project dialog (for project configuration source)
- By default the build menu should operate the same as the old Geany.
- New build configuration is in a new section in each config file and won't
interact with settings used by older Geany versions, but will use the old
settings if no new ones are available.
Examples of potential capabilities that need to be considered for Geany
overall are:
- Now that labels are configurable, should interpreted languages have the
compile and build labels configured to something more appropriate
- If so, labels read from the system filetypes.xxx files are locale
sensitive iaw the GKeyFile specification, but how do the translations get
made?
- Can any languages benefit from extra or differing menu items?
Known Bugs, Limits and Incomplete (in no particular order)
- Latex doesn't work yet, all the hard coded functionality has been removed
but the filetype hasn't been updated to configure it back.
- Only one execute command is currently supported/working
- Dialog entries in preferences and project, for settings that are replaced
by the new dialogs, have not been removed yet, but they probably do nothing
- Error regex setting field in the new dialog does nothing yet
- Not compiled at all on windows
- Very limited testing so far (C/C++ filetypes only)
- Sections of the manual other than build menu have not been changed, eg
file formats, hidden settings any sections that reference build menu etc
Enjoy
Lex
Hi Guys,
When typing a function call, the calltip is shown when the '(' is
typed. It is then replaced by autocomplete suggestions as the
parameter is typed. If the autocomplete is accepted then the calltip
is re-displayed, but if the autocomplete is not accepted, such as by
typing ',' then the tooltip is not re-displayed, very annoying. I
know I can re-display it manually by twisting my fingers into a knot
;-) but automatic would be better.
AFAICT the editor.c code intends to re-display it but I can't see why
it doesn't work in this case.
Also I noticed that the manual doesn't describe symbol autocompletion
operation and the keycodes for accept and dismiss. It does for
snippets, but not for symbol autocomplete.
Cheers
Lex
Hello,
I try to code a small plugin that uses libxml2 to parse some data. I
searched a lot, but I don't understand how I can tell Geany that I want to
use that lib...
To compile my file, I use the following command lines :
compilation
gcc -o "output.o" -Wall -c -fpic "plugin.c" `pkg-config --cflags geany`
`pkg-config --cflags libxml-2.0`
for the shared library
gcc -shared -o "output.so" "output.o"
Thanks and best regards !
Cedric
Hi all!
I wrote a plugin that embraces the selection in configurable text.
I made it with HTML in mind. It's possible to define variables which the
user can fill in a dialog, for example with a file selection dialog or a
comboBox with predefined values.
Screenshot: http://primandras.hu/stuff/geany_embrace/screenshot.png
Some documentation: http://primandras.hu/stuff/geany_embrace/ConfigFile.html
The tar.gz: http://primandras.hu/stuff/geany_embrace/embrace-0.9.tar.gz
I'd like to contribute it in the geany-plugins project.
It still needs tidying and stuff. For example I tried to set different
set of key bindings for different filetypes and dynamically change them
when the user switches documents (so the same key combinations could be
re-used) but now only those appear in the key binding setting dialog,
which apply to the filetype visible at plugin_init() (However using the
same key combination on different documents does work as expected.)
Best regards!
András Prim
Hi, today after update and recompile geany from svn rev.4048 i have a
little strange
problem - i cannot run geany under console as root (sudo geany or etc.)
.May be this is not geany issue, i`m not sure, sorry.
Configure log :
Install Geany in : /usr/local
Using GTK version : 2.16.2
Build with GTK printing support : yes
Build with plugin support : yes
Use virtual terminal support : yes
Use (UNIX domain) socket support : yes
Compiling Subversion revision : r4048
My system :
Linux nask0 2.6.29.6-213.fc11.i586 #1 SMP Tue Jul 7 20:45:17 EDT 2009
i686 athlon i386 GNU/Linux
Geany 0.18 (svn >= r4048), GTK+ 2.16.2, GLib 2.20.4
--
Regards,
Atanas Beloborodov [nask0]
Programmer
a.beloborodov(a)viscomp.bg
Mobile: +359 896 733 612
Viscomp EOOD *Viscomp EOOD*
92V "Hristo Botev" Blvd
4000 Plovdiv
Bulgaria
Tel: +359 32 655 175
Fax: +359 32 655 176
www.viscomp.bg <http://www.viscomp.bg>
