Is it possible to make an archived mailing list which can contain
threads of comments posted to Github (maybe using Github API)? We have
sometimes when squash commits it deletes Github comments, but I thought
maybe we could have some stable backup + URL to link to (ex. in commit
messages, on the mailing list, etc) which could be searchable and
googlable and not be deleted by rebase.
I've been working a bit on my Geany-plugin Djynn. A few of the points in
the plugin wishlist has been added to the plugin.
** In Project mode, be able to open recursively many source files under an
- in the project manager, all files in a folder and subfolders can be
opened at once
** A 2nd sidepane on the right-hand side. It would be practical to see
filetree and class browser at the same time. (core-thingy? I dunno) or
split the sidepane to see the filetree above the class browser*
- the project manager with file tree can be opened as a second sidepane
** List of all projects in sidebar. The project entries should be
expandable to show a treeview of all files in the projects base path*
** Add a javadocs option for java users*
- djynn has an option for javadoc/doxygen comments
** HTML Characters - Inserts HTML character decimal references like "&"
andhexadecimal references like "&" as well as the existing support
forentity references like "&". This could be a setting in the Geany
- djynn has a function for encoding and decoding HTML and a few other
I was working on some changes to Geany that may affect "Geany Portable"
so I figured I'd have a look at the changes it makes to Geany to see how
it handles binary relocation, but I can't seem to find the source
The link on PortableApps.com seems to indicate that 1.24.1 is
available but when I check the sources on SourceForge, it only has 0.20
code (and it's not clear if it includes the changes or is just upstream
source). I'm pretty sure Geany's source code would have to be modified
in order to allow it to be "portable", since the location to the Glade
file is fixed at compile-time, which happens to be tightly related to
what I was curious about.
The website GeanyPortable.org linked on PortableApps.com seems to
redirect somewhere else now (judging by the pictures, I can't read the
language it's in).
Is the person(s) who release GeanyPortable on this mailing list, and if
so, would you mind providing me a copy of the modified source code so
that I could review it to make sure we don't further break "portable" Geany?
after some time spent debugging
I think the file saving options are a bit confusing and misleading and
should be simplified.
1. Both g_file_set_contents() and g_file_replace_contents() do absolutely
the same thing (saving to temporary file, then renaming the file), the only
difference is the first uses POSIX calls while the second GIO. The
use_gio_unsafe_file_saving name is very confusing because it's not unsafe
in any way.
2. It is now possible to set
and to users it's unclear which of the options will be actually used (it's
the use_atomic_file_saving case because it's checked first in the code).
3. The fallback "ordinary" file saving when
doesn't bring any benefit compared to the two above - it's similar to
use_atomic_file_saving=true in using POSIX calls, it's just a bit less safe
because it writes directly to the file without the renaming. The GIO
g_file_replace_contents() recreates the file's permissions/ownership
I would suggest removing the file saving option mentioned in (3) above and
have just a single settings option like