You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First let me thank you for this wonderful tool. I'm using it everywhere... almost...
Now, I've a question/request: Is it possible to get the position of the start column used by cog to output it's text, i.e.: the position of the "/*[[[cog" delimiter. I don't know how to call it, so why not "anchor position" .
I've found no reference to it in the doc's, and I'm a bit too lost in your code to implement it myself :-)
Actually I'm trying to write a simple wrapping-class to customize the outputs in such a way that the global source width is fixed (e.g.: 80 or 120) but also that it will be wrapped onto the next lines with the proper indentation. To achieve this I need to know this anchor point in order to set the proper width of the current line of code. So far it's working bu I have to set the "anchor" manually, which is boring.
Any help would be really appreciated...
The text was updated successfully, but these errors were encountered:
Hello,
First let me thank you for this wonderful tool. I'm using it everywhere... almost...
Now, I've a question/request: Is it possible to get the position of the start column used by cog to output it's text, i.e.: the position of the "
/*[[[cog
" delimiter. I don't know how to call it, so why not "anchor position" .I've found no reference to it in the doc's, and I'm a bit too lost in your code to implement it myself :-)
Actually I'm trying to write a simple wrapping-class to customize the outputs in such a way that the global source width is fixed (e.g.: 80 or 120) but also that it will be wrapped onto the next lines with the proper indentation. To achieve this I need to know this anchor point in order to set the proper width of the current line of code. So far it's working bu I have to set the "anchor" manually, which is boring.
Any help would be really appreciated...
The text was updated successfully, but these errors were encountered: