From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: eliz@gnu.org, tv.raman.tv@gmail.com, rgm@gnu.org, 13731@debbugs.gnu.org
Subject: bug#13731: 24.3.50; C-h N -- Outline navigation Fails
Date: Sat, 16 Feb 2013 18:48:14 -0800 [thread overview]
Message-ID: <CADkJX2hzxtoPaNFhn1GYmAC5vT1ouGxg8Lb24DohhBWOXqdhyw@mail.gmail.com> (raw)
In-Reply-To: <20768.17500.927206.155870@gargle.gargle.HOWL>
This is definitely something in the packages I'm loading; emacs
-q with emacspeak loaded does not exhibit the breakage.
--
Best Regards,
--raman
On 2/16/13, T. V. Raman <tv.raman.tv@gmail.com> wrote:
> Sadly, C-c C-n -- which also runs the same command
> outline-next-visible-heading goes straight e to the end of the buffer.
>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> >> Date: Sat, 16 Feb 2013 12:04:46 -0800 From: "T. V. Raman"
> >> <tv.raman.tv@gmail.com> Cc: tv.raman.tv@gmail.com,
> >> 13731@debbugs.gnu.org
> >>
> >>
> >> Glenn -- M-n runs outline-visible-next-heading.
> Eli>
> Eli> Not here, it doesn't. I get "undefined", like Glenn.
> Eli>
> Eli> You have a lot of optimal features active, so I guess
> Eli> you see this not in "emacs -Q".
> Eli>
> Eli> outline-next-visible-heading (sic!) is on "C-c C-n", not
> Eli> M-n. If I type "C-c C-n", it does go to the next
> Eli> heading, as expected.
>
> --
> Best Regards,
> --raman
>
next prev parent reply other threads:[~2013-02-17 2:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 19:08 bug#13731: 24.3.50; C-h N -- Outline navigation Fails raman
2013-02-16 19:31 ` Glenn Morris
2013-02-16 20:04 ` T. V. Raman
2013-02-16 20:18 ` Eli Zaretskii
2013-02-17 2:45 ` T. V. Raman
2013-02-17 2:48 ` T.V. Raman [this message]
2013-02-17 3:49 ` Eli Zaretskii
2013-02-19 1:42 ` T.V. Raman
2013-02-19 15:56 ` Bastien
2013-02-19 19:23 ` Drew Adams
2013-02-19 19:34 ` Bastien
2013-02-19 20:49 ` Drew Adams
2013-02-19 21:57 ` Stefan Monnier
2013-02-19 22:03 ` Drew Adams
2013-02-20 2:20 ` T. V. Raman
2013-02-20 13:08 ` Bastien
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=CADkJX2hzxtoPaNFhn1GYmAC5vT1ouGxg8Lb24DohhBWOXqdhyw@mail.gmail.com \
--to=tv.raman.tv@gmail.com \
--cc=13731@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rgm@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 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.