Problem seems to have been solved! Not sure exactly what solved it --
maybe I fixed a build script earlier, or maybe it's because some of the
libraries I used to build today are only weeks old releases.
I verify that gspawn-win32-helper.exe ends up in my build folder, and
when I install and run th
** WORKAROUND **
If running from the Windows .exe package, you should have "*.zim"
registered in your desktop to be handled by zim.exe, by default. Browse
to the notebook you want to open and double-click the .zim file.
--
[win] cannot open another notebook
https://bugs.launchpad.net/bugs/569091
I've confirmed this isn't a problem with the installer. If you run Zim
with all of GTK's global installation in your $PATH, this problem still
occurs. :^(
I might take a look at this later, but Jaap I'm assigning it back to
you.
** Changed in: zim
Assignee: Brendan Kidwell (bkidwell) => Zim
I mean if you run it from source, on Windows, ignoring build_win32 and
its output -- in this case it still fails to open another notebook by
launching "zim.py --no-daemon" whereas if you run the .exe build it
fails to run "[path ...]zim.exe --no-daemon"
--
[win] cannot open another notebook
https
4 matches
Mail list logo
