unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Nathan Trapuzzano <nbtrap@nbtrap.com>
Cc: 15848@debbugs.gnu.org
Subject: bug#15848: 24.3.50; cperl-mode + which-function: Improve reporting (corner case)
Date: Wed, 13 Nov 2013 10:44:23 +0530	[thread overview]
Message-ID: <87siv0hoi8.fsf@gmail.com> (raw)
In-Reply-To: <87txfhif11.fsf@nbtrap.com> (Nathan Trapuzzano's message of "Tue,  12 Nov 2013 14:41:30 -0500")

Nathan Trapuzzano <nbtrap@nbtrap.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>
>>     Perl->Tools->Imenu-POD headers menu entry.  
>>     cperl-imenu-index-pod is a variable defined in `cperl-mode.el'.

> Perhaps I misunderstand, but when I have that variable set to nil, the
> POD imenu entries go away, which is what the docstring says. 

The behaviour is as documented.  I should have done something wrong
yesterday.

> However, I think indexing the POD entries by default is the better way
> for several reasons:
>
> 1. cperl-mode already does it that way.
> 2. perl-mode does it.
> 3. There is no "pod-mode".  For editing pod files, perl-/cperl-mode is
>    the best Emacs has.  Moreover, many people _do_ write plain pod
>    files, in which case the entries should get indexed.

Hmm.... Losing something to gain some thing else doesn't seem good to
me.

I cursorily looked at cperl-mode.  My gut feeling is that which-function
decides the box it is in by looking at the markers that is returned.  So
we may have to examine what value goes in to the marker.  

My recommendation would be to put the patch on hold.





  reply	other threads:[~2013-11-13  5:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  6:58 bug#15848: 24.3.50; cperl-mode + which-function: Improve reporting (corner case) Jambunathan K
2013-11-10 11:51 ` Nathan Trapuzzano
2013-11-10 13:06   ` Jambunathan K
2013-11-10 13:13     ` Jambunathan K
2013-11-10 15:51       ` Nathan Trapuzzano
2013-11-10 16:20         ` Jambunathan K
2013-11-10 16:48           ` Nathan Trapuzzano
2013-11-10 18:14             ` Nathan Trapuzzano
2013-11-11  7:20             ` Jambunathan K
2013-11-11 10:50               ` Nathan Trapuzzano
2013-11-11 11:09                 ` Jambunathan K
2013-11-11 11:18                   ` Nathan Trapuzzano
2013-11-11 11:31                     ` Jambunathan K
2013-11-11 11:43                       ` Jambunathan K
2013-11-11 15:03                       ` Nathan Trapuzzano
2013-11-12  5:23                         ` Jambunathan K
2013-11-12 14:11                           ` Nathan Trapuzzano
2013-11-12 17:49                             ` Jambunathan K
2013-11-12 19:41                               ` Nathan Trapuzzano
2013-11-13  5:14                                 ` Jambunathan K [this message]
2013-11-13 11:41                                   ` Nathan Trapuzzano
2013-11-14  5:39                                     ` Jambunathan K
2013-11-14 11:11                                       ` Nathan Trapuzzano
2013-11-10 18:04         ` Stefan Monnier
2013-11-10 22:12           ` Nathan Trapuzzano
2013-11-11  2:57           ` Leo Liu
2013-11-11  4:18             ` Stefan Monnier
2013-11-11 10:58               ` Nathan Trapuzzano
2013-11-11 10:54             ` Nathan Trapuzzano
2013-11-15  5:16 ` Jambunathan K

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=87siv0hoi8.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=15848@debbugs.gnu.org \
    --cc=nbtrap@nbtrap.com \
    /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.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).