From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: bug? Date: Thu, 29 Jun 2017 20:53:20 -0400 Message-ID: References: <874luysvwc.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47269) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQkBd-000837-SY for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 20:53:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQkBZ-0007yM-0D for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 20:53:29 -0400 Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]:33615) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dQkBY-0007vn-SC for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 20:53:24 -0400 Received: by mail-qk0-x233.google.com with SMTP id v143so5938019qkb.0 for ; Thu, 29 Jun 2017 17:53:23 -0700 (PDT) In-reply-to: <874luysvwc.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: Org-mode All I thought should happen is that the invisible text adjacent to the point would be edited (except for the {}). Other than the edge case where there is no first headline, it seems to work ok as far as I can tell. Nicolas Goaziou writes: > Hello, > > John Kitchin 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, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu