Hi Daniel, > Killing and yanking in Bongo buffers seems to be seriously > messed up somehow. I wrote functions for moving sections > and tracks, [...].
Good idea. I wrote such functions too, but ended up changing lots of other stuff in the process, and haven't gotten around to sorting out the overexuberant changes. > This is what moving a section means: > > bongo-kill-line > bongo-forward-section > bongo-yank > bongo-backward-section That's fine, except it will mess with the kill ring. Here's what my implementation looks like:
binDjTwbbhuO2.bin
Description: application/emacs-lisp
(I renamed `bongo-{backward,forward}-section' to
`bongo-{previous,next}-object' and made them signal errors
instead of returning nil, an idea that snowballed into a
whole bunch of other changes.)
> It's supposed to work fine, I think. I don't see anything wrong with
> this approach. But often it leaves stray or duplicated lines in the
> buffer. Sometimes lines disappear. And I get "end of buffer" errors.
>
> Daniel, do you have any idea of what is wrong?
I can duplicate such bugs if I try to move collapsed sections,
but not otherwise, I think. Can you confirm that? If so, then
it's almost certainly a cluster of invisibility bugs.
I believe I fixed a bunch of those in that experimental
branch in which I've changed too much. I almost never
collapse things myself, so invisibility bugs have had a
tendency to build up over time in Bongo.
Thank you for reporting this. I will take a look at it.
--
Daniel Brockman <[EMAIL PROTECTED]>
_______________________________________________ bongo-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bongo-devel
