emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
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: Sat, 07 Jan 2023 12:26:17 +0000	[thread overview]
Message-ID: <871qo6msye.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455233B5E9BA736A10DE127A2F89@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

>> You 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.

You can use interactive bisection.
See https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and 
https://cubeatic.com/index.php/s/iQakFWXgxsJzyXP

> 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.

Yes, Org does scan things as you type. However, you should always be
able to exit upon typing C-g (maybe
`org-element--cache-interrupt-C-g-max-count' times).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2023-01-07 12:26 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
2023-01-07 12:26     ` Ihor Radchenko [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=871qo6msye.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dsmasterson@gmail.com \
    --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).