since my knowledge in writing good regular expressions is very limited,
I wasn't able to write one to parse something like the following:
<h1><a href="#id109">Some Text</a></h1>
<h1>Some Text</h1> */
In tagmanager/html.c you can find the relevant code (INNER_HEADING
macro) and there is one regexp for each case of the above examples. But
I wasn't able to combine these regexps so that both examples can be
parsed sucessfully with one regexp.
If anyone feels bored, have a look ;-).
Get my GPG key from http://www.uvena.de/pub.key
based on the suggestions in  I added some new features in
-> third argument can be used to turn the caret into a block caret
(hello emacs users ;-))
line_wrap_visuals and line_wrap_indent
-> new settings for display of wrapped lines
-> most funny feature: you can make the selection and the current line
transluncent to not completely cover the styles below
More information about usage can be found in the file filetypes.common
itself or in the manual.
Get my GPG key from http://www.uvena.de/pub.key
I was remembering a discussion, we had a few weeks ago. So I'm
forwarding a maybe interesting posting of the Debian legal mailing
Begin forwarded message:
Date: Fri, 7 Mar 2008 22:40:55 +0100
From: Francesco Poli <frx(a)firenze.linux.it>
Subject: Re: GPL v2/v3 ?
On Thu, 6 Mar 2008 09:38:21 +0100 Miriam Ruiz wrote:
> 2008/3/6, Francesco Poli <frx(a)firenze.linux.it>:
> > In my opinion, the decision boils down to:
> > o if you want to enhance compatibility *and* you trust the FSF to
> > keep the promise that future versions of the GNU GPL will be
> > "similar in spirit to the present version", then you may
> > choose a "v2 or later" approach
> > o if you want to enhance compatibility *and* you don't mind
> > seeing your copyleft more or less weakened (or even completely
> > destroyed) by successive versions of the GNU GPL, then you may
> > choose a "v2 or later" approach
> > o if don't mind reducing compatibility *and* you want a strong
> > and certain copyleft (while not trusting the FSF to keep the spirit
> > of the GNU GPL v2 in successive versions), then you should choose a
> > "v2 only" approach
> There's another possibility: dual-licensing your code under the GPLv2
> only and the GPLv3 only.
You're right. That would be the following case:
o if you want to slightly enhance compatibility with existing
licenses *and* you don't mind seeing your copyleft weakened by some
clauses of the GNU GPL v3, *but* you don't trust the FSF to publish
good future versions (v4, v5, ...) of the GNU GPL, then you may choose
a "v2 or v3" approach
Frank Lanitz <frank(a)frank.uvena.de>
Here is patch that make filetypes_detect_from_filename() use
find_shebang() for better filetype detection. The former function is
renamed to filetypes_detect_from_extension().
This should provide complite geany filetypes autodetection for plugins.
hi all, I'm new to the list and somewhat new to geany. I'm a developer and
have recently moved from Windows + Editpad Pro for my editing to Linux +
Geany. The move has been somewhat rocky, mostly due to the slightly
different workflow, but there is one "feature" in Editpad that I really
found useful and I'd like to bring it to Geany.
Editpad has a sidebar file browser that is a mix of Geany's Documents
sidebar + the file browser plugin. That is, it only shows open documents,
but it reveals which directory each file is in, like so...
So if you're working on files in different directories, it gives you a
visual representation of that, rather than a flat list of open documents in
the Geany Documents sidebar. And it only shows files that are open.
Geany can be made to show the full path of files, but even if all the files
are in the same directory, it shows the entire path (/home/adam/.....) for
I was wondering if this functionality already exists in either Geany or in a
plugin. If so, I haven't been able to find it. If this functionality
doesn't already exist, would it be better for me to look into making a
plugin for it? I haven't actually opened up the geany code yet, so I don't
know much about what is going on internally. But I would appreciate some
steering in the correct direction as to the best way I could implement this.
Leider ist das in der falschen ML gelandet. geany-i18n ist ursprünglich
für die Koordination der Übersetzungen gedacht. Habe einfach mal die
"normale" Geany List in den CC genommen.
On Mon, March 3, 2008 10:22 am, askforitagain(a)gmx.de wrote:
> kann man in Geany auch die Möglichkeit nutzen, per FTP Daten zu laden und
> zu speichern, wenn ich die entsprechenden Veränderungen an einer Datei
> durchgeführt habe... damit man sich das lokale Abspeichern spart und
> online quasi wie lokal arbeiten kann.
Ein solches Feature ist noch nicht für das Hauptprogramm in Planung, da es
eine große Anzahl von Abhängigkeiten mit sich bringen würde. Eine
Implementation als Plugin wäre aber denkbar, nur gibt es nach meinem
Wissen kein Projekt dafür.
Question was: Is there a function to make Geany work together with ftp to
upload a changed file directly to ftp.
No, there isn't and there are no plans for including such a feature into
main tree of Geany sincee it will need a lot of depedencies. Sorry. I
think this could be implemented as a plugin, but I'm not sure, if somebody
already is working on it.
I guess it is time to release geanyprj plugin. Main goal of this release
is make "go to tag declaration/definition" work for all files in project
(not just currently opened ones).
Plugin webpage: http://users.cosmostv.by/yurand/geanyprj/
Example of usage:
On Geany sources:
1. Download geany-0.13.tar.gz
2. Unpack it somewhere, for example in ~/src/geany-0.13
3. Open ~/src/geany-0.13/configure.in
4. Click "Tools->Project->New Project", and click "Create" button
This will create and save .geanyprj file in ~/src/geany-0.13.
From now, every time you open any file from ~/src/geany-0.13
directory or it's subdirs .geanyprj will be opened. So next time
you don't have to create or open project manually.
1. Open any geany source code code file
"go to tag declaration/definition" should work for any geany
function. (Not limited to opened files).
1. Now you open file that doesn't belong to Geany. For example
~/src/myprj/a.c Geany project will be closed. If
~/src/myprj/.geanyprj exists it will be opened as current
2. Switching back to any Geany file will open Geany project again.
The plugin will work bad on Windows, since it assume filenames encoding
First of all I have to say, that I have posted this message to the wrong
list. At home on my laptop, I have not subscribed this list. Instead I
use Gmane.org for reading. The only geany-list available is
geany-general. So I've posted this message there. Now I see that there is
no posting an this list and I found my mistake. Mea Culpa ;-)
Now the original posting.....
As mentioned in my previous posting, I have spent some time to try 0.13
new project features. While starting to test, I've found to smaller
* vcdiff: if the CVS access uses SSH, the passphrase entry is invible. If I
call geany from the shell, I'm able to enter the passphrase there.
* enforce the extension of the project file. I've edit the filename first,
and forgot the extension. After this, ".geany" got lost.
* opening a project automatically closes all files from outside the
the project, if the file was loaded previously to the project. After
closing the project, these file got loaded again.
Now I load the project first, and than the "other file". After closing the
project, the "other file" is closed too. This is also the case, if Geany
is closed with the project and the "other file" open. After the new start,
all files are open. But again, closing the project will close the
"other file" too!
Is this a bug?
But now the notes on the project management.
* I need to switch between different projects. It would be
good to have a sidebar with all projects listed. The project properties
should have a checkbox to hide a (inactive) project in the sidebar. It
therefore must be visible in the "open project" dialog.
All files from outside these projects can be automatically added to an
"virtual" project 'unmanaged'. So the user can fast toggle between a
project and the "other" files.
* The tabs with the opened files and the "documents" sidebar allways shows
the loaded files of the current project. To make access even easier, the
"documents" sidebar could hold all of todays used projects as special entries
(i.e. as bold text). Maybe this highlighting could be used for the
"projects" sidebar to.
* The "projects sidebar" or the main toolbar should have a "drop down" box
with a list of "release flavours". The list can be fix or may be part of
the project properties. The handling of these "flavours" is done in the
makefile. To make the change of a flavour visible, Geany should remove
a flag file in the project director. This file should be defined in the
project properties. As default .build-stamp can be used. Without this file,
a "make clean & make" is performed (by the makefile) to force a rebuild.
The only thing Geany has to do: (1) if the project properties defines a
"stamp file", this file must be removed when switching the "flavour".
(2) The project properties must be extended to hold configurable list of
"flavour" stings. (3) The selected flavour must available as macro for
the make command (of the project). So it will be passed to make, which
will do all the work. This means there is no makefile generator.
I personally use the flavours "DEBUG", "BETA" and "FINAL". I pass them as
variable RELEASE to make (i.e. make RELEASE=DEBUG). This is handled inside
* one last thing for now ;-) My old Laptop has a screen resolution of
1024x768. It would be great to have icons instead of text as lables for
the tabs of the sidebar.
Email: Joerg Desch <jd DOT vvd AT web DOT de>