From: Nick Dokos <firstname.lastname@example.org>
Subject: Re: Search for an entry expands parent
Date: Mon, 20 Jul 2020 10:33:30 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
Gt Uit <firstname.lastname@example.org> writes:
> 18.07.2020, 18:48, "Kyle Meyer" <email@example.com>:
> Gt Uit writes:
> Updates since my last email:
> - Sometimes the first C-s yields intended result (minimal), with
> subsequent C-s searches expanding all entries.
> - I tried on Emacs 28.0.50 and am getting the same results.
> - I tried with emacs -Q and isearch minimal behaves properly!
> - I tried a live distribution (Linux Mint 20 Ulyana, same
> distribution I am currently using) and isearch minimal behaves
> - I tried the following without any success:
> + Remove all emacs related packages and reinstall emacs (via apt)
> + Install emacs from snap.
> Now that I have narrowed down the bug to be something local to my
> current installation please advise on how to debug/resolve.
> Something that might give you a clue about what's going on is stepping
> through org-show-set-visibility, comparing what happens when it works as
> expected and what happens when it doesn't. If you haven't used Edebug
> before, take a look at its node in the Elisp manual:
> (info "(elisp)Edebug")
> Thanks for pointing me to Edebug, a tremendously useful tool.
> I got the following:
> - Executed:
> + M-x find-function org-show-set-visibility
> + C-u C-M-x (edebug-defun)
> - The first time I launch emacs, the function org-show-set-visibility is
> called and I can step through the code via Edebug
Typing "d" at this point should give you a stack trace, so you can figure out
who called it.
> - Subsequent calls do not invoke org-show-set-visibility
> I didn't mention earlier that I got this bug after upgrading from Linux
> Mint 19.3 to Linux Mint 20.
> Can you please point me to what to further debug, in particular function
> that is called before org-show-set-visibility.
> Gt Uit
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2020-07-20 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 7:32 Search for an entry expands parent Gt Uit
2020-07-16 22:42 ` Kyle Meyer
2020-07-17 4:55 ` Gt Uit
2020-07-18 8:58 ` Gt Uit
2020-07-18 15:48 ` Kyle Meyer
2020-07-20 7:18 ` Gt Uit
2020-07-20 14:33 ` Nick Dokos [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).