unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Rainer M Krug <Rainer@krugs.de>, help-gnu-emacs@gnu.org
Subject: RE: How to increase the depth of the scan in imenu and speecbar?
Date: Fri, 27 Mar 2015 07:12:45 -0700 (PDT)	[thread overview]
Message-ID: <9ba6ae73-23af-41d3-bd5a-238ca311a94b@default> (raw)
In-Reply-To: <m2d23ulinn.fsf@krugs.de>

> I started using imenu and speedbar, anr=d I like them, but I would like
> to have not only a second level, but up to e.g. 6th level. Where can I
> set these options? I did not find anything.
> 
> I am particularly talking about orgmode files and their headers, which
> are only shown up to level 2.

See `C-h v imenu-generic-expression'.  I don't think you can have more
than two levels.  Each element of the list must be a list of the form
(MENU-TITLE REGEXP INDEX [FUNCTION] [ARGUMENTS...]). 

You can at least have more submenus (i.e. level 2), to break things
down more.  IOW, instead of trying to have, say, this:

MyMenu
  Variables
    Options

You can just use this:

MyMenu
  Options
  Non-Option Variables

Remember that the regexps are tried in order. So putting Options
(every option is a variable) before Non-Option Variables lets
you use a more general regexp for the latter.

That's at least better than just MyMenu > Variables, i.e., it at
least lets you separate the two kinds of variables.

Taking a look at library `imenu+.el' might help in this regard.
http://www.emacswiki.org/emacs/download/imenu%2b.el



  parent reply	other threads:[~2015-03-27 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 12:38 How to increase the depth of the scan in imenu and speecbar? Rainer M Krug
2015-03-27 13:12 ` [Solved]: " Rainer M Krug
2015-03-27 14:12 ` Drew Adams [this message]
2015-03-27 14:21   ` Drew Adams
2015-03-27 14:55     ` Rainer M Krug

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ba6ae73-23af-41d3-bd5a-238ca311a94b@default \
    --to=drew.adams@oracle.com \
    --cc=Rainer@krugs.de \
    --cc=help-gnu-emacs@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.
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).