From: Christian Moe <mail@christianmoe.com>
To: Alan L Tyree <alantyree@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org menu change
Date: Mon, 25 Nov 2013 09:22:31 +0100 [thread overview]
Message-ID: <m2mwksevqw.fsf@uio.no> (raw)
In-Reply-To: <87zjot3ubq.fsf@breezy.my.home>
Alan L Tyree writes:
>>> In the Emacs menu Org -> Customize -> Expand this menu used to give a
>>> complete menu of org-mode customisations which was quite helpful for an
>>> amateur. Now it gives a short menu that does little more than send the
>>> user to the usual Emacs customisation system.
I haven't used this feature before, and get different behaviors on OSX
(where I have mu4e) and Linux (where I don't at the moment), so I'm not
sure what you expect to see.
On Mint 15, clicking "Expand this
menu" places a Customize item in the Customize sub-menu, and hovering
over this item opens a sub-sub-menu of Org customizations.
On Mac OSX, it also places a Customize item in the sub-menu; no
sub-sub-menu appears, however, but clicking the item takes me to a
*Customize Group: Org* buffer.
> The error is being caused by my mu4e setup. It begins:
>
> (require 'mu4e)
> (require 'org-mu4e) ;; sets up links to email
> (require 'org-contacts)
> Eliminating the second two requires cures the problem and the 'Expand
> this menu works as it should.
I don't require org-contacts.
Requiring or not requiring org-mu4e doesn't seem to make a difference on
my Mac setup, I get the above behavior regardless.
> My mu4e and emacs 24 setup is a little unusual, so I don't know if
> this
> is a general problem. I would like to hear from anyone using mu4e.
Sorry I couldn't be less ambiguous...
Yours,
Christian
next prev parent reply other threads:[~2013-11-25 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 4:15 Org menu change Alan L Tyree
2013-11-24 4:40 ` Nick Dokos
2013-11-24 5:42 ` Alan L Tyree
2013-11-25 5:48 ` Alan L Tyree
2013-11-25 8:22 ` Christian Moe [this message]
2013-11-25 20:09 ` Alan L Tyree
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mwksevqw.fsf@uio.no \
--to=mail@christianmoe.com \
--cc=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).