all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Imenu and structured documents
Date: Sat, 28 Sep 2019 16:50:33 -0600	[thread overview]
Message-ID: <24ae143c-245a-679d-686d-01fe83250db9@grinta.net> (raw)
In-Reply-To: <jwv4l0w3wcc.fsf-monnier+emacs@gnu.org>

On 28/09/2019 16:16, Stefan Monnier wrote:
>> . 2017
>> . . 2017 January
>> . . 2017 February
> 
> In Imenu, the submenu structure usually doesn't reflect the document
> structure, but instead it is just a fixed structure for different
> *categories* of entries (e.g. functions-vs-classes-vs-variables), so I'd
> expect all the sections and subsections to just be placed within the
> same "level".
> 
> I use Imenu via the minibuffer (with completion) rather than via mouse
> selection in a GUI menu (or via Speedbar).  I'm not sure if it's the
> more common way to use Imenu, but it's one where this flat structure
> works fairly well.

Thanks Stefan, this is useful information.

Do you use imenu with latex-mode? From the description of your use case
I think you do not use it with org-mode. Is prefixing sublevels with an
indicator that represent the hierarchy as done in latex-mode something
desirable? I may imagine that it can be annoying is the goal is
completion in the minibuffer.

Thank you.

Cheers,
Dan



  reply	other threads:[~2019-09-28 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 20:41 Imenu and structured documents Daniele Nicolodi
2019-09-28 22:16 ` Stefan Monnier
2019-09-28 22:50   ` Daniele Nicolodi [this message]
2019-09-29 18:25     ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=24ae143c-245a-679d-686d-01fe83250db9@grinta.net \
    --to=daniele@grinta.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.