The Emacs Muse is similar to EmacsWikiMode, especially its markup. A comparison of the two is available on this page.
Emacs Muse is an authoring and publishing environment for Emacs. It simplifies the process of writing documents and publishing them to various output formats.
Muse consists of two main parts: an enhanced text-mode for authoring documents and navigating within Muse projects, and a set of publishing styles for generating different kinds of output.
What makes Muse distinct from other text-publishing systems is a modular environment, with a rather simple core, in which “styles” are derived from to create new styles. Much of Muse’s overall functionality is optional. For example, you can use the publisher without the major-mode, or the mode without doing any publishing; or if you don’t load the Texinfo or LaTeX modules, those styles won’t be available.
The Muse codebase is a departure from emacs-wiki.el version 2.44. The code has been restructured and rewritten, especially its publishing functions. The focus in this revision is on the authoring and publishing aspects, and the “wikiness” has been removed as a default behavior (available in the optional muse-wiki module). CamelCase words are no longer special by default.
One of the principal aims in the development of Muse is to make it very easy to produce good-looking, standards-compliant documents.
The Muse manual is available on-line in several forms.
There is also a Quick Start guide, which is available at
Muse is hacked on and maintained using git.
If you would like to track the latest development changes, or contribute code to Muse, check out the MuseDevelopment page for instructions.
AUTHORS file included with Muse for a complete listing of contributors to Muse.
There are several mailing lists for Muse.
The Gmane website allows you to access the mailing lists in a variety of useful forms, such as: RSS feed, a blog-style interface, and a news feed for a newsreader.
Please consult http://mwolson.org/projects/ReportingEmacsLispBugs.html before filing a bug report.
There is an IRC channel devoted to discussion of Muse (as well as EmacsWikiMode and perhaps PlannerMode) at
irc.freenode.net. The current maintainer (MichaelOlson) occasionally hangs out there.
The initial stable version of Muse has been released. Nested list support and context-aware escaping of specials have been added to it, as of the 3.03 release. The 3.10 release also includes an EmacsWikiMode migration guide in the etc/ directory.
The big question is: Why shouldn’t I just use EmacsWikiMode for publishing my stuff?
Jim Ottaway has written a latex style that allows you to specify latex options using the muse directives. So you can do things like
Location: http://www.users.zetnet.co.uk/jeho/archives/2005 Archive name: email@example.com Branch: muse-stuff--jeho--1.0
I do not like using “.muse” as file extension; after all, muse files are text files. But opening all “.txt” files in muse-mode is also undesirable. The following lines in my .emacs automatically open muse-mode if:
(add-to-list 'auto-mode-alist '("#title " . muse-mode)) (add-hook 'text-mode-hook (lambda () (unless (eq major-mode 'muse-mode) (when (equal (file-name-extension buffer-file-truename) "txt") (save-excursion (goto-line 5) (if (re-search-backward "\* [A-Z][a-z]+.*" 1 t) (muse-mode)))))))
I had multiple problems with the code above: 1st: According to the manual, auto-mode-alist controls “the correspondence between file names and major modes”, so the first expression doesn’t work as intended. I modified the 2nd expression to do all the work. 2nd: it prevented me of running text-mode on an unsaved buffer - (progn (interactive) (switch-to-buffer “my-new-buffer”) (text-mode)) - would fail. This was preventing me of running remember mode. Below are my modifications on FelipeCsaszar’s code.
;; muse-mode on *.txt files, if a #title or sect. header is on top 4 lines (add-hook 'text-mode-hook (lambda () (unless (or (eq major-mode 'muse-mode) (not (stringp buffer-file-truename))) (when (equal (file-name-extension buffer-file-truename) "txt") (save-excursion (goto-line 5) (if (re-search-backward "\* [A-Z][a-z]+.*\\|#title " 1 t) (muse-mode)))))))
Do NOT modify existing upstream source files
I prefer markup rules like LDP WikiText, which is designed for authoring before converted to DocBook
<johnw> now, you could make muse-moin.el, however <johnw> and have it change muse-publish-markup-regexps, rule 1600 <johnw> and then you'd have what you want, and all styles would honor it <mwolson> that would be cool <johnw> the muse core allows for complete customization
What about having a more sophisticated way to customize the markup ? I mean, we could have different markup used inside a muse-project or even for each file in a muse-project. I opened a bug in the bugtracker. I am still waiting for answers and support to start hacking something.
Can get enough of Muse? Find yourself spending more and more time with it? Well now you can make your life even more Muse-centric by evaluating code (M-C-x). Thus referencing files within Muse becomes easy:
…also works great with Tramp:
Or use Muse to launch your favorite file-browser! Add this function in your dot-emacs:
(defun browse-dir (dir-as-string) (start-process-shell-command "browse" "*scratch*" ;(concat "/usr/bin/rox-filer --new " dir-as-string) (concat "/usr/bin/nautilus --no-desktop " dir-as-string)))
…then evaluate within Muse:
See the bug-tracking interface. Wishlist items are those with a severity of 1.
Q: Could you provide a step by step guide about how to generate a project of pages?
A: Check out the “Creating and Managing Muse Projects” part of the Muse manual; hopefully that will be of use to you. The
examples directory in the Muse tarball might also be worth looking at.
Q: Could you show how to set up muse to render mathematical formulae?
A: Muse now comes with muse-latex2png.el. Check out its header for directions.