From: Matt Price <moptop99@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: eldoc recursion error
Date: Tue, 8 Sep 2020 11:27:50 -0400 [thread overview]
Message-ID: <CAN_Dec-d=kxiEpNA3WxJM5BrRFNP7FJcTupGa-eq7exwWRXu9Q@mail.gmail.com> (raw)
In-Reply-To: <878sdkxqtd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On Tue, Sep 8, 2020 at 10:53 AM Bastien <bzg@gnu.org> wrote:
> Hi Matt,
>
> Matt Price <moptop99@gmail.com> writes:
>
> > In a new org file, add these lines:
> >
> > #+begin_src python
> > print
> > #+end_src
> >
> > position cursor inside block and the error message occurs.
>
> I can't reproduce the bug. What version of Emacs are you using?
>
> Can you give a recipe starting with emacs -q?
>
I htink I have it now.
$ emacs -q
(require 'org-eldoc) ;;(or navigate to lisp/org-eldoc.el and eval-buffer)
create new org file, add this content:
#+begin_src python
print
#+end_src
ensure eldoc-mode is turned on. place cursor inside block.
If for some reason that doesn' twork try manually running `org-eldoc-load`
and repositioning cursor.
> Thanks!
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1566 bytes --]
next prev parent reply other threads:[~2020-09-08 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 13:49 eldoc recursion error Matt Price
2020-09-08 14:24 ` Bastien
2020-09-08 14:49 ` Matt Price
2020-09-08 14:53 ` Bastien
2020-09-08 15:27 ` Matt Price [this message]
2020-09-08 16:19 ` Matt Price
2020-09-11 4:12 ` Kyle Meyer
2020-09-21 1:51 ` Kyle Meyer
-- strict thread matches above, loose matches on Subject: below --
2020-09-15 19:22 James N V Cash
2020-09-17 4:55 ` Kyle Meyer
2020-09-17 15:03 ` James N. V. Cash
2020-09-20 4:54 ` Kyle Meyer
2020-09-20 15:35 ` James N. V. Cash
2020-09-20 15:49 ` James N. V. Cash
2020-09-20 23:38 ` Kyle Meyer
2020-09-21 1:07 ` James N. V. Cash
2020-09-21 1:36 ` Kyle Meyer
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='CAN_Dec-d=kxiEpNA3WxJM5BrRFNP7FJcTupGa-eq7exwWRXu9Q@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=bzg@gnu.org \
--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).