all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-fold problems
Date: Sat, 07 May 2022 09:47:10 +0100	[thread overview]
Message-ID: <87pmkp91bl.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87sfplyko3.fsf@localhost> (Ihor Radchenko's message of "Sat, 07 May 2022 13:30:04 +0800")

Hi Ihor,

On Saturday,  7 May 2022 at 13:30, Ihor Radchenko wrote:
> While you are at the deadline, feel free to switch org-fold-core-style
> back to overlays.

Thank you.  I should have done that (had I thought if it ;-)) but
deadline met in any case.  Next time.

> If you get some time and encounter the described issue, can you try to
> run M-: (setq org-fold-core-first-unfold-functions nil) and try
> org-reveal again?

Okay.  I cannot replicate the problem with the file I had problems with
yesterday (the file has obviously changed in the meantime) but will do
so when/if it arises again.

On a related matter, I typically use vc-ediff for comparing the current
working copy of a file and the last committed version.  This used to
expand the file completely (assuming I'm remembering correctly) but now
(some?) drawers are not opened so if there are differences inside a
drawer, I cannot see them via ediff.  Does this make sense?  If so, is
there something I should customise to have *everything* opened when
using ediff?

Thanks again,
eric

-- 
: Eric S Fraga, with org release_9.5.3-472-gd2a459 in Emacs 29.0.50


  reply	other threads:[~2022-05-07  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 13:39 org-fold problems Eric S Fraga
2022-05-07  5:30 ` Ihor Radchenko
2022-05-07  8:47   ` Eric S Fraga [this message]
2022-05-08  7:25     ` Ihor Radchenko
2022-05-09 12:40       ` Eric S Fraga
2022-05-11 11:03         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmkp91bl.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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.