Just a small feature request – it would be convenient if the Move Up and Move Down commands would include nested list items when moving a parent item. I can’t imagine a situation where you would want to move just the parent item and not the children items of the parent.
Generally agree, but in the meantime, you can move items with nested children if you collapse them first.
You can select multiple list items, and the move command will move all of them.
We had a long discussion in the past about the best way to implement this. At the time, the line-based approach was the one our users preferred. That said, I’ll make a note to revisit the behavior when we get to that part.
Thanks, I appreciate that. I’m surprised to hear the users preferred the single-line-based approach even for nested lists!
For me it’s not that important what the standard behaviour is, as long as both are possible: moving a single item as well as the selected list with all its children. But: If the standard behaviour were now the other way round (with move up/down also moving the children without prior selection), how would you then move only a single item if you want?
You could always use the traditional method of cut and paste.
But I’d be curious, if a bullet has sub-bullets, when would you even want to move only the single parent line? I can’t think of an example of that. If there is one, I’d imagine it would be so rare that my request is still a really useful behavior, and cut and paste could be used in the rare exceptions.
Actually never. So that’s a valid point. But as I said, I do not really care, as long as I can do both things easily. Bear is not an outliner app, so I don’t see the necessity that it act like one. But it also could be changed for all I care. I really don’t mind. ![]()