View Single Post
Old 05-31-2015, 06:23 PM   #17
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,729
Karma: 205159604
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Hitch View Post
Probably. I do it the same way that Turtle does--I regex them in, immediately preceding whatever element/class I've used for the section heads. Then split. I actually think using BV for this is dicier than using CV, because the results MAY (not necessarily will) be unexpected as to the location of the split. Not that it's unfixable, of course, but...{shrug}.

Hitch
I do the same for the same reasons. The "cursor" position in Book View is a bit ambiguous (with respect to the underlying markup). I'll still occasionally do the one-off manual "Split at Cursor" in Code View (as opposed to wholesale split markers inserted via regex S&R), so I do those splits/marks in Code View where the cursor position is never ambiguous.

Splitting into nested div situations, coupled with the wrong Tidy Settings, cured me of doing such things in Book View long ago.

Last edited by DiapDealer; 05-31-2015 at 06:31 PM.
DiapDealer is offline   Reply With Quote