Sorry to hear that this release causes you so much trouble. To answer your
last question first: this release is not intended to have major
incompatibilities. Afraid that the reality of a project like zim is that we
do not find all issues unless we actually make a new release. There isn't a
big group of people testing changes before they are released, and although
I try very hard my own testing and the unittest suite do not catch
- headers are now removed at will
- removing an image while a page showing it is loaded now generates memory
fault and terminates zim (worked great before)
- renaming a page from outside while displayed in zim changed behavior to
These 3 are new issues for me - you are the first to report them. Will try
to reproduce and fix them.
- forking to background changed to blocking a terminal window
Here zim is now more inline with other applications. This was necessary to
remove a lot of issues other users where having with the background
spawning. This part of the code is now greatly simplified and *still*
giving issues :(
- new unremovable "attachments" button wastes room under the text area
(compromising my layout optimization)
This is a "rough edge" in the design. Side panes now "collapse" instead of
"hiding". Keeping the tabs of the side pane visible at all times makes the
behavior much more predictable for most users. It costs more real estate,
and I'm open for design suggestions how to gain it back - maybe we should
combine it with the statusbar for the bottom pane?
On Mon, May 1, 2017 at 4:29 AM Sara Ziner <sara.zi...@googlemail.com> wrote:
> Thanks, Jiri, for that hint. Helps a lot.
> Unfortunately, I had to find yet another unexpected incompatibility:
> Headers are removed even from existing files.
> For my workflow this means that I have to remove most well-formed-checks
> for the extension I have developed.
> Now it's 5 I found during the first day:
> - headers are now removed at will
> - forking to background changed to blocking a terminal window
> - new unremovable "attachments" button wastes room under the text area
> (compromising my layout optimization)
> - removing an image while a page showing it is loaded now generates memory
> fault and terminates zim (worked great before)
> - renaming a page from outside while displayed in zim changed behavior to
> the worse
> All those compromise my workflow and I will need a day's work or so (which
> I do not have at the moment) to recover.
> Is it really necessary to have such incompatibilities pushed to automatic
> Usually incompatibilities will give rise to a change of the major release
> and shall not be pushed automatically.
> All the best,
> 2017-04-29 16:39 GMT+02:00 Jiří Janoušek <janousek.j...@gmail.com>:
>> Or define an alias: `alias zim="nohup /usr/bin/zim > /dev/null 2>&1 &"`
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : email@example.com
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~zim-wiki
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zim-wiki
More help : https://help.launchpad.net/ListHelp