From: Bastien <bzg@gnu.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: is it possible to customise what headline level which-function displays?
Date: Fri, 18 Apr 2014 10:01:41 +0200 [thread overview]
Message-ID: <87oazzqd5m.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87tx9rnk6n.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 18 Apr 2014 08:58:08 +0100")
Hi Eric,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> then which-function thinks we are in A.1 when point is where
> indicated. This is the case with the default value of
> org-imenu-depth.
Surely an issue with Emacs, as I can't reproduce the problem here
with latest Emacs.
--
Bastien
prev parent reply other threads:[~2014-04-18 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 21:18 is it possible to customise what headline level which-function displays? Eric S Fraga
2014-04-17 15:44 ` Bastien
2014-04-18 7:58 ` Eric S Fraga
2014-04-18 8:01 ` Bastien [this message]
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=87oazzqd5m.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=e.fraga@ucl.ac.uk \
--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).