Thanks Mark S. I didn't understand. I do now. YES. It could be quite easy for me as I now understand what you saying. Decent text editors support "vertical paste" so it would be easy to get a number on each line and then in TW regex it into position.
BUT I'm still playing with "how to do this without leaving TW". Yesterday I was playing with transcluding a list of the 1000 numbers vertically next to a transclusion of content that needs enumerating to see if one could generate a (surface level) copyable text to go back into processing. So far no good as the selection is columnised. Best wishes Josiah Mark S. wrote: > > What I'm suggesting is that you don't need the counters -- you create a > 1000 rules to apply a 1000 counts, one after the other. Building up those > rules shouldn't take long in a good text editor (especially one's like > Emacs that have column modes). > > On Wednesday, February 21, 2018 at 7:28:15 AM UTC-8, @TiddlyTweeter wrote: >> >> Thank you Mark S & coda coder >> >> For your further ideas -- molto grazie. >> >> coda coder wrote: >> >>> I'm not sure if I've understood correctly, but, that draft seems to >>> suggest that in Firefox you *may* be able to set user-select, either in >>> the parent element or in the before/after pseudo element itself: >> >> >> Right. There is a lot of ambiguity and no clear outcome. Its clear its an >> issue. >> >> I tried a few different tests on user-select. Got it to work but not >> (yet) on any generated pseudo bits. I try a bit more before giving up. >> >> Mark S. wrote: >>> >>> I'm not familiar with how your regex tools work. Do they re-iterate >>> until there are no more changes to be made? >>> >> >> I'm using BJ's Flexity plugin that allows sequences of RegEx to be run >> before the main parser kicks in. Iteration continues freely if you want, >> until done. Basically its raw access to JS regex in its full form. >> >> >>> If so, then I'm thinking that rules like this at the very end: >>> >>> /(.*?)#startmarker#/$1 0001#endmarker#/ >>> /(.*?)#startmarker#/$1 0002#endmarker#/ >>> .... etc. >>> >>> Might brute force what you want. >>> >> >> The problem is getting the counters. Whilst some JS (edit: I meant Regex) >> implementations when you get a capturing group you can return both the >> string and the match index (i.e. return the match count value as well as >> the string content) in JS, as far as I know, you can return the string >> matched with the captured group, but you can't access the COUNT of the >> match, even though you can use it. IF you could then I could use that to >> build the indices I need. >> >> Best wishes >> Josiah >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2958c3f4-fa68-4f52-8984-f978943eab5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
