#88 Add CLI option to remove paperstyle

[Johannes May]

This patch adds a CLI switch to remove the paperstyle of an opened xoj file. It builds upon Patch #48 and is meant to be used together with the -A export option in order to create pdf without the annoying ruling in the background.

See my fork at GitHub for a version of xournal with a couple of patches applied.

[Denis Auroux]

Thanks! But note that there is already a config option (Print Paper
Ruling in options menu / print_ruling in config file) to have printing
and export-to-PDF remove the rulings from paper backgrounds. So, unless
you really need to have an export feature that sometimes includes and
sometimes excludes background without having to change the config
setting, I am not sure how useful this extra command-line option really is.

Frnid

[Johannes May]

I did actually not know about this config key, but I might actually need the possibility to switch it based on some condition (I use a simple bash script to convert all my xoj files automatically).

Another benefit of this option for me is that the output of the export won't have the paperstyle no matter on what machine I run it, so I don't have to rely on having the correct configuration in place.

BTW, is the development of Xournal still active? The latest changes where made quite a while back and I don't see too many of the patches beeing incorporated into xournal. I think integrating the basic CLI patch would be a really nice feature for many people. My current workflow with xournal is to store xoj files on my personal cloud and automatically convert them to xoj so I can look at them on my smartphone.

[Denis Auroux]

Xournal's development is not so active at the moment due to real-life
and work constraints -- but I am still fixing bugs when they come up,
and considering patches when I am satisfied that they serve a common
need and do things the right way without complicating the UI. The
command-line interface patch is just at that threshold where it doesn't
hurt but I'm not sure whether the functionality is consistent with
hypothetical grander plans for a more robust command-line functionality,
so I've been sitting on it unduly. Sorry...

Denis