emacs
/
mu
mirror of https://github.com/djcb/mu.git
1
0
Fork 0
Code Issues Releases Wiki Activity

NEWS.org: attempt to appease github's org parser

This commit is contained in:
Dirk-Jan C. Binnema 2021-08-30 11:43:45 +03:00
parent 1865e98221
commit aa6c03bfab
1 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
NEWS.org
View File

@ -5,21 +5,21 @@
*** mu
- ~mu~ switched to use the [[https://mesonbuild.com][meson]] build system by default. The existing
~autotools~ is still avaiable, but is to be removed after the 1.8 release.
- =mu= switched to use the [[https://mesonbuild.com][meson]] build system by default. The existing
=autotools= is still avaiable, but is to be removed after the 1.8 release.
Using ~meson~ (which you need to install), you can use something like in the
Using =meson= (which you need to install), you can use something like in the
mu top directory:
#+begin src sh
#+BEGIN_SRC sh
$ meson build && ninja -C build
#+end src
#+END_SRC
After that, ~ninja -C build~ should be enough. ~autogen.sh~ has been updated
to use ~meson~ instead, and and even delivers a ~Makefile~ with some useful
targets that invoke the corresponding ~meson~ / ~ninja~ targets.
After that, =ninja -C build= should be enough. =autogen.sh= has been updated
to use =meson= instead, and and even delivers a =Makefile= with some useful
targets that invoke the corresponding =meson= / =ninja= targets.
- ~mu~ now require C++17 support for building (this is in preparation for code
- =mu= now require C++17 support for building (this is in preparation for code
that actually _uses_ C++17)
*** mu4e
@ -29,21 +29,21 @@
- a lot of the internals have been changed:
- ~mu4e~ is slowly moving from using the ~~~ to the more common ~--~ separator for
private functions; i.e., ~mu4e~foo~ becomes ~mu4e--foo~.
- ~mu4e-utils.el~ had become a bit of a dumping ground for bits of code;
- =mu4e= is slowly moving from using the =~= to the more common =--= separator for
private functions; i.e., =mu4e-foo= becomes =mu4e--foo=.
- =mu4e-utils.el= had become a bit of a dumping ground for bits of code;
it's gone now, with the functionality move to topic-specific files --
~mu4e-folders.el~, ~mu4e-bookmarks.el~, ~mu4e-update.el~, and included in
=mu4e-folders.el=, =mu4e-bookmarks.el=, =mu4e-update.el=, and included in
existing files.
- the remaining common functionality has ended up in ~mu4e-helpers.el~
- ~mu4e-search.el~ takes the search-specific code from ~mu4e-headers.el~, and
- the remaining common functionality has ended up in =mu4e-helpers.el=
- =mu4e-search.el= takes the search-specific code from =mu4e-headers.el=, and
adds a minor-mode for the keybindings.
- ~mu4e-context.el~ and ~mu4e-update.el~ also define minor modes with
- =mu4e-context.el= and =mu4e-update.el= also define minor modes with
keybindings, which saves a lot of code in the various views, since they
don't need explicitly bind all those function.
- also ~mu4e-vars.el~ had become very big, we're refactoring the ~defvar~ /
~defcustom~ declarations to the topic-specific files.
- ~mu4e-proc.el~ has been renamed ~mu4e-server.el~.
- also =mu4e-vars.el= had become very big, we're refactoring the =defvar= /
=defcustom= declarations to the topic-specific files.
- =mu4e-proc.el= has been renamed =mu4e-server.el=.
*** guile