Am Samstag, den 30.12.2017, 21:25 +0900 schrieb Joel Kulesza: > I've pulled (1ff34a97) and tested along with your 9261 patch. It > doesn't appear to work for me as I'd expect; please > see: https://youtu.be/sEIFW9Vo0UY.
OK, I see now that it does not make sense to have this separate function. I reverted it and disabled the function at this position. Appending here is the same as prepending (with this particular cursor position). > > > Append from within the frame. I can't recall if I demonstrated > > this > > > in my video, but it splits the current frame rather than > > inserting a > > > new frame after the current one. > > > > This is intentional. The splitting always is relative to the cursor > > position. > > I understand this is intentional, but what is the rationale behind > the decision to do this rather than to keep the frame a standalone > component that exists before/after the current frame? If we would always move the cursor to the start/end of the environment first, there would not be a way to split in between. As it is now, you have full control over where the new environment is to start. > As an aside: given the splitting, is append (and failing to mention > the splitting) misleading in the menu entry? I'll rename it anyway when moving to insert. Jürgen
signature.asc
Description: This is a digitally signed message part
