emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: bug?
Date: Thu, 29 Jun 2017 20:53:20 -0400	[thread overview]
Message-ID: <m260fethxb.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <874luysvwc.fsf@nicolasgoaziou.fr>

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


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

  reply	other threads:[~2017-06-30  0:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 13:38 bug? John Kitchin
2017-06-29 14:36 ` bug? Nicolas Goaziou
2017-06-30  0:53   ` John Kitchin [this message]
2017-07-01 12:30     ` bug? Nicolas Goaziou
  -- 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

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