| Age | Commit message (Collapse) | Author |
|
- don't make assumptions on where programs live (i.e., /bin/sh, /bin/rm,
/bin/mv) are not universal
- dont invoke shell when unnecessary
- improve error-handling
|
|
|
|
Build the tests lazily, i.e., not before `meson test`. This helps with
build-times.
|
|
No need for identical files in mu4e / guile dirs, move to build-aux.
|
|
In message, don't re-fill when unneeded. Add tests.
Fixes #2802.
|
|
Somewhere along the way, the body-txt and body-html fields were merged
into a single body field. Later, commit 8eac3922215c ("guile: re-enable
the guile support") finally removed support for Field::Id::BodyHtml from
mu:c:get-field.
Unfortunately mu.scm and the documentation are still stuck in the past, so
update them. mu:body-txt is now a synonym for mu:body, and mu:body-html
always returns #f.
I wanted to add a mu:body test also for the rfc822.1 message, but there's
currently a bug where its body text is is duplicated (issue #2802), so the
test would fail.
|
|
It's stated to be US-ASCII with 7-bit encoding, but it contains the
UTF-8 character '—'.
Fixing the encoding very slightly changes the average size of messages
reported by mu:average, so adjust the new expected value.
|
|
|
|
|
|
|
|
When meson is run in a build path that is different from source root, the
generated shared library cannot be found under "<source_root>/guile". This
patch adds the corresponding path under build root to guile_root_path so that
they continue to work.
This should fix https://github.com/djcb/mu/issues/2631.
|
|
While not recommended, sometimes it can be useful to disable building
the unit tests. This can be done now with
meson -Dtests=disabled build
|
|
|
|
We were using dates (in documentation, (c) notices etc) based on the
build-date; that makes it hard to do reproducible builds, so specify a
specific date in the top-level meson file, and use that throughout.
|
|
and add a new one for the indexer
|
|
Fixes #2548
|
|
upgrade to the new formatting code.
Fixes: #2540
|
|
We use
guile_dep.get_variable(pkgconfig: 'extensiondir')
but that's not good for everyone.
|
|
|
|
|
|
Not complete, but a first big stab converting users of Mu::Error and
various g_warning & friends, format to the new libfmt-based APIs.
|
|
Use the new & improved APIs.
|
|
It was getting old...
Remove the unused parts, refactor the few parts still in use.
|
|
They're incompatible.
|
|
|
|
We need some of the new functionality in the near-future.
Fix build warnings.
|
|
Some minor improvements to the existing scripts
|
|
|
|
|
|
Scripts seem to depend on both.
|
|
Fixes #2323
|
|
|
|
Since 2008, autotools has served us well - thank you!
However, mu is now using meson build, and it's time to remove the
autotools support -- one build system is enough.
|
|
Move test-mu-common to mu-test-utils. Use mu_test_init as a wrapper for
g_test_init. Update users.
|
|
So the docs can be found.
|
|
|
|
snarfing is tricky to get to work portably with c++ code. So, for now let's just
include the pre-generated .x files and safe us a bit of time. They're not very
prone to change anyway.
|
|
Already has it... seems to break compilation on some machines?
|
|
Update for the internal (Mu::Message) APIs.
Update build.
|
|
It's not ready for the new Message
|
|
|
|
|
|
We need the extensions, and/or let's use _one_ optional implementation everywhere.
|
|
|
|
Adapt to the new names / directory. Big commit, but mostly just very boring renaming.
|
|
Basically, move/rename lib/mu-message* to lib/mu-*.
Add the beginnings of a Message class.
|
|
Make it work with meson.
|
|
|
|
|
|
|