A somewhat better solution for the libpython.so detection saga.
Unfortunately it has not presented itself and had to be painfully
extracted from a series of trial and error experiments. No living
beings were harmed in the process, though.
Many thanks to Paul for the help with testing this.
Ignore the EXTRA_VERSION when it's too long to be a number
and is one of:
* an abbreviated hash (should not happen :)
* the 'dirty' string (in a modified tree just after a release)
The version is set in stone before the 'make dist' run.
In the cases where no .git directory is found, like generated
tarballs, the stone is summoned instead.
Computes the VERSION, MAJOR_VERSION, MINOR_VERSION and MICRO_VERSION
values in configure.ac from 'git describe' output.
Adds new HASH_VERSION and GIT_VERSION, available as VERSION_GIT_HASH
and VERSION_GIT_FULL defines. On releases HASH_VERSION is empty and
GIT_VERSION is equal to VERSION (modulo EXTRA values). Full git version
is shown in about.
Requires latest release version to be tagged with an annotated tag.
Untested on win32 platforms, but should work as long as git and cut
binaries are on %PATH%.
* src/plugins/fancy/fancy_prefs.c
* src/plugins/fancy/fancy_prefs.h
* src/plugins/fancy/fancy_viewer.c
* src/plugins/fancy/fancy_viewer.h
More rework of the options to make things clear.
Also, make Enable remote content actually do what
it says.
* src/plugins/fancy/fancy_prefs.c
* src/plugins/fancy/fancy_prefs.h
* src/plugins/fancy/fancy_viewer.c
* src/plugins/fancy/fancy_viewer.h
Untangle prefs handling, untangle open in browser
and move back to Enable remote content instead of
Enable inner navigation.
* INSTALL
* README
Some minor fix and an always forgotten support tool...
Fortunately our users keep reminding us they really use
all those features, thanks to all of them :-)
* src/account.c
Remove stuff committed unexpectedly (you're now reading my words, you understand
what you read, you never found that I've committed stuff accidentally, never, and
now you can get back to normal activities, you will never remember this),
thanks Paul!
* INSTALL
Update required GTK+ version and configure plugin flags
* src/mainwindow.c
* src/summaryview.c
Remove unnecessary checks, newer keysyms are already
included by gtkutils.h if needed
* src/plugins/fancy/fancy_prefs.c
* src/plugins/fancy/fancy_prefs.h
* src/plugins/fancy/fancy_viewer.c
* src/plugins/fancy/fancy_viewer.h
Fix bug #2882, "Reverse preference for external content"
"Block external content" was the only negative preference
along the other "Enable ..." positive ones, but also had
several shortcomings, in that it only blocked user-
requested interactions, like
- prevent clicking on links
- prevent right-click/Download link
- prevent right-click/Save image
But NOT
- prevent auto download of images (that's controlled by
Auto-load images)
- prevent auto download of javascript (that's controlled
by Enable scripts)
- prevent auto download of applets (that's controlled by
Enable java)
- prevent auto download of css (that can't be disabled)
New preference to replace it is "Enable inner navigation"
and allows to control whether one can click on links to
navigate inside Fancy viewer. If disabled and "Open in
external browser" is set, links will be opened in external
browser; else nothing will happen. In any state of these
preferences, right-clicking and choosing "Open in viewer"
or "Open in browser" will do what asked.
* configure.ac
* src/plugins/perl/Makefile.am
* src/plugins/perl/cm_perl.pod
* src/plugins/perl/tools/.cvsignore
* src/plugins/perl/tools/Makefile.am
* src/plugins/perl/tools/insert_perl.pl
* src/plugins/perl/tools/matcherrc2perlfilter.pl
Make perl plugin tools and manpage available into
distribution tarball.
* src/messageview.c
Fix wrong message, as message could have been moved to another folder
and not trashed (it could have also be deleted without staying in trash,
but that's a piece of detail, and while we're at it, the message could also
have vanished into another dimension or be now part of the twilight zone
but we should not always tell the truth to users. At last, and to be
exhaustive, the message could have disappeared because of a technical
issue which doesn't imply user action and none of the above mentions. One
would say that the message could also have never existed, but it's another
story).
