From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Conflict between Org hyperlink and auto-complete (I think) [9.6 ( @ /home/dsmasterson/.emacs.d/elpa/org-9.6/)]
Date: Fri, 06 Jan 2023 16:14:16 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455233B5E9BA736A10DE127A2F89@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87y1qfhcb4.fsf@localhost> (Ihor Radchenko's message of "Fri, 06 Jan 2023 16:12:31 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> Not yet sure how to minimize my setup to build a reproducible case or
>> further debug this, but I thought I'd get the bug out to others who
>> might know better.
>
> I may consider using https://github.com/Malabarba/elisp-bug-hunter
I think I'll add this package to my setup, but I don't think it can help
in this case as it's an infinite loop bug. Once it's locked in the
loop, I have to kill emacs, so elisp-bug-hunter would never have a
chance to report anything.
Question: does Org scan (some part of the) text *AS* you are typing?
I'm beginning to think that the answer is 'no' and, so, it was
auto-complete that tripped on a sequence of characters. I'll have to
look at which part of auto-complete did it.
--
David Masterson
next prev parent reply other threads:[~2023-01-07 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 6:56 [BUG] Conflict between Org hyperlink and auto-complete (I think) [9.6 ( @ /home/dsmasterson/.emacs.d/elpa/org-9.6/)] David Masterson
2023-01-06 16:12 ` Ihor Radchenko
2023-01-07 0:14 ` David Masterson [this message]
2023-01-07 12:26 ` Ihor Radchenko
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=SJ0PR03MB5455233B5E9BA736A10DE127A2F89@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).