mu/mu4e/mu4e-config.el.in

;; auto-generated

(defconst mu4e-mu-version "@VERSION@"
  "Required mu binary version; mu4e's version must agree with this.")

(defconst mu4e-doc-dir "@MU_DOC_DIR@"
  "Mu4e's data-dir.")

(provide 'mu4e-config)
* mu4e: restructure code a bit and enable byte-compilation 2012-04-09 15:34:52 +02:00			`;; auto-generated`
mu4e: use mu4e-config instead of mu4e-meta All these changes to avoid: ,---- \| mu4e/meson.build:92: WARNING: Source item '/home/djcb/Sources/mu/build/mu4e/mu4e-meta.el' cannot be converted to File object, because it is a generated file. This will become a hard error in the future `---- This is because we want to byte-compile a file we just before generated using configure_file. This does not seem like a crazy thing, but meson threatens with breaking the build at some point in the future. So instead, we decide _not_ to compile this (very boring) file. But, users may still have an older mu4e-meta.elc lying around, leading to confusion. So, let's rename that file and we're golden. 2022-05-29 00:09:53 +02:00
* mu4e-version.el.in: use @VERSION@, not @PACKAGE_STRING@ to compare the version 2012-04-10 08:08:29 +02:00			`(defconst mu4e-mu-version "@VERSION@"`
mu4e: fix typo and doc-string formatting 2012-11-14 13:36:18 +01:00			`"Required mu binary version; mu4e's version must agree with this.")`
* mu4e: restructure code a bit and enable byte-compilation 2012-04-09 15:34:52 +02:00
mu4e: add NEWS(.org) as a main menu item 2015-06-07 20:07:59 +02:00			`(defconst mu4e-doc-dir "@MU_DOC_DIR@"`
			`"Mu4e's data-dir.")`

mu4e: use mu4e-config instead of mu4e-meta All these changes to avoid: ,---- \| mu4e/meson.build:92: WARNING: Source item '/home/djcb/Sources/mu/build/mu4e/mu4e-meta.el' cannot be converted to File object, because it is a generated file. This will become a hard error in the future `---- This is because we want to byte-compile a file we just before generated using configure_file. This does not seem like a crazy thing, but meson threatens with breaking the build at some point in the future. So instead, we decide _not_ to compile this (very boring) file. But, users may still have an older mu4e-meta.elc lying around, leading to confusion. So, let's rename that file and we're golden. 2022-05-29 00:09:53 +02:00			`(provide 'mu4e-config)`