all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: bug?
Date: Thu, 29 Jun 2017 16:36:51 +0200	[thread overview]
Message-ID: <874luysvwc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m21sqerd8b.fsf@andrew.cmu.edu> (John Kitchin's message of "Tue, 20 Jun 2017 09:38:12 -0400")

Hello,

John Kitchin <jkitchin@andrew.cmu.edu> writes:

> I think there is a bug with invisible edits.
>
> In org 8.2.10 if I set this:
>
> (setq org-catch-invisible-edits 'smart) ; or show
>
> and have org-toggle-pretty-entities active, then if there is no headline
> before point, with the point here:
>
> NH^{3}
>       ^
>
> I get outline-back-to-heading: Before first heading if I try to type anything.
>
> I also get this same error in org 9.0.7. It only happens with the 3
> wrapped in {}.
>
> That seems like a bug to me.

Fixed, somewhat.

I think `org-check-before-invisible-edit' deserves some discussion about
its specifications. As-is, it contains logic errors. For example, if you
try to edit text near invisible text and you happen to have invisible
custom properties somewhere else in the buffer, the properties are going
to be made visible but not the invisible text at point.

I would be happy to fix this, but need to think about what is expected,
e.g. when we are editing something near an invisible link or, as in your
example, sub/superscript.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-06-29 14:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 13:38 bug? John Kitchin
2017-06-29 14:36 ` Nicolas Goaziou [this message]
2017-06-30  0:53   ` bug? John Kitchin
2017-07-01 12:30     ` bug? Nicolas Goaziou
     [not found] <875y9aciir.fsf.ref@yahoo.com>
2023-05-03  1:26 ` Bug? Po Lu
2023-05-03  9:40   ` Bug? Mattias Engdegård
2023-05-03 10:12     ` Bug? Mattias Engdegård
2023-05-03 11:24       ` Bug? Shynur Xie
2023-05-03 12:27         ` Bug? Mattias Engdegård
2023-05-03 17:22           ` Bug? Juri Linkov
2023-05-03 11:24       ` Bug? Eli Zaretskii
2023-05-03 11:26         ` Bug? Shynur Xie
2023-05-04  8:35         ` Bug? Shynur Xie
2023-05-04 20:57         ` Bug? Shynur Xie
2023-05-05  4:41           ` Bug? Eli Zaretskii
2023-05-05 16:18             ` Bug? Shynur Xie
2023-05-06 10:44           ` Bug? Mattias Engdegård
2023-05-06 14:58             ` Bug? Shynur Xie
2023-05-06 15:24               ` Bug? Eli Zaretskii
2023-05-07 11:08               ` Bug? Mattias Engdegård
2023-05-07 12:05                 ` Bug? Po Lu
2023-05-07 12:17                   ` Bug? Eli Zaretskii
2023-05-07 12:54                     ` Bug? Po Lu
2023-05-07 13:36                     ` Bug? Shynur Xie
2023-05-07 13:51                       ` Bug? Mattias Engdegård
2023-05-07 14:42                         ` Bug? Shynur Xie
2023-05-07 15:06                           ` Bug? Eli Zaretskii
2023-05-03 11:23     ` Bug? Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2014-05-06 14:47 Bug?? Susan Cragin
2014-05-06 15:28 ` Bug?? Maurice
2014-05-06 21:30   ` Bug?? Suvayu Ali
2014-05-07 16:15 ` Bug?? Achim Gratz
2014-02-06 10:15 Bug: "#+STARTUP: content" shows text as well as headlines [8.2.5h (8.2.5h-elpa @ ~/.emacs.d/elpa/org/) Paul Stansell
2014-02-06 10:42 ` Bastien
2014-02-06 11:38   ` Bastien
2014-03-06 17:32     ` Bug: Paul Stansell
2012-12-04 16:53 Bug? Charles
2012-12-04 19:12 ` Bug? Achim Gratz
2012-12-05  1:20   ` Bug? Charles
2010-05-12 12:50 bug? J. David Boyd
2010-05-12 13:35 ` bug? Bernt Hansen
2010-05-12 14:32   ` bug? J. David Boyd
2005-03-07 16:35 bug ? fg
2003-09-23 11:07 Bug? Mark Espinoza
2002-08-28 17:41 Bug? Sharon A Watkins
2002-08-29  1:38 ` Bug? Juanma Barranquero
2002-08-29  4:44 ` Bug? Eli Zaretskii

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=874luysvwc.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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.