From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: xournalpp: update to 1.1.0.
Date: Tue, 20 Jul 2021 20:00:33 +0200 [thread overview]
Message-ID: <20210720180033.skKbbKAu0Nbl_2VrjFrW0N6k1XHW3aMlzw6RZlFBCl4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32049@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
There's a closed pull request on the void-packages repository
xournalpp: update to 1.1.0.
https://github.com/void-linux/void-packages/pull/32049
Description:
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
I've been following git HEAD of xournalpp, updating every once in a while, and using it every day to teach, I can say it works and it has several nice improvements over the previous version.
In particular it is now possible to write lua plugins to enhance the program. I'm using plugins and I included a trivial very tiny patch so that plugins can be loaded from user configuration (`$HOME/.config/xournalpp/plugins/`) and not only from system directory (`/usr/share/xournalpp/plugins/`). I hope this is ok, since it is otherwise impossible to load plugins without changing system files. Note that a more general approach for plugin paths is planned (https://github.com/xournalpp/xournalpp/issues/1155#issuecomment-623234420); it should be compatible with my workaround (in the sense that once they implement what they are planning we can remove this temporary patch).
prev parent reply other threads:[~2021-07-20 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 23:28 [PR PATCH] " tornaria
2021-07-20 2:39 ` [PR PATCH] [Updated] " tornaria
2021-07-20 13:18 ` tornaria
2021-07-20 14:45 ` ericonr
2021-07-20 18:00 ` tornaria
2021-07-20 18:00 ` tornaria [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210720180033.skKbbKAu0Nbl_2VrjFrW0N6k1XHW3aMlzw6RZlFBCl4@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).