set looplimit [expr {[tcl::string::length $overblock] + 10}]
}
set scheme 3
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
set inputchunks [lindex [list $lflines [unset lflines]] 0]
}
4 {
set inputchunks [list]
foreach ln [split $overblock \n] {
lappend inputchunks [string cat $ln \n]
}
if {[llength $inputchunks]} {
lset inputchunks end [tcl::string::range [lindex $inputchunks end] 0 end-1]
}
}
}
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
#review insert_mode. As an 'overtype' function whose main function is not interactive keystrokes - insert is secondary -
#but even if we didn't want it as an option to the function call - to process ansi adequately we need to support IRM (insertion-replacement mode) ESC [ 4 h|l
set renderargs [list -experimental $opt_experimental\
set renderopts [list -experimental $opt_experimental\
#REVIEW - merging extended (e.g 4:4) underline attributes suppresses all other SGR attributes on at least some terminals which don't support extended underlines
"Return a boolean indicating whether Ansi codes were detected in text.
Important caveat:
When text is a tcl list made from splitting (or lappending) some ansi string
- individual elements may be braced or have certain chars escaped.
(one example is if a list element contains an unbalanced brace)
This can cause square brackets that form part of the ansi to be backslash escaped
- and the function can fail to match it as an Ansi code.
"
@values -min 1
text -type string
} ]
#*** !doctools
#[call [fun detect] [arg text]]
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
#detect any ansi escapes
#review - only detect 'complete' codes - or just use the opening escapes for performance?
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
regexp <re> $text
}]
@ -7405,7 +7432,7 @@ if {![info exists ::punk::args::register::NAMESPACES]} {
#[para]Currently only utf-8, utf-16* and utf-32* are properly supported even though the other BOMs are detected, reported via get_bomid, and stripped from the data.
#[para]GB18030 falls back to cp936/gbk (unless a gb18030 encoding has been installed). Use -encoding iso8859-1 if this isn't suitable and you need to do your own processing of the bytes.
#eat or own dogfood version - shows the implementation is simpler - but unfortunately not suitable for a simple function like this which should be as fast as possible?
#we don't have to decide what is an opt vs a value
#even if the caller provides the argument -block without a value the next function's validation will report a reasonable error because there is now nothing in $values (consumed by -block)
#dirfiles assumes we don't have glob chars in the filenames or paths - dirfiles_dict can be called directly with explicit -tailglob in the rare case that assumption doesn't hold
# dirfiles will test last segment (tail) of supplied searchspecs for fileness vs folderness (when no globchars present in tail) so that it can pass the appropriate flags downstream
#wasn't resolved by id - so take this as a request to generate it (probably there is an existing custom def - and this has been manually requested to get the default)
set origin [string range $origin [string length (autodef)] end]
set subcommands [lsort [dict keys $subcommand_dict]]
if {[llength $commandargs]} {
set match [tcl::prefix::match $subcommands [lindex $commandargs 0]]
if {[llength $queryargs]} {
set match [tcl::prefix::match $subcommands [lindex $queryargs 0]]
if {$match in $subcommands} {
set subcmd [dict get $subcommand_dict $match]
return [arginfo {*}$subcmd {*}[lrange $commandargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
return [arginfo {*}$subcmd {*}[lrange $queryargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
Frame width doesn't adapt and content may be truncated
so -width may need to be manually set to display more."
*values -min 0 -max 1
@values -min 0 -max 1
contents -default "" -type string\
-help "Frame contents - may be a block of text containing newlines and ANSI.
Text may be 'ragged' - ie unequal line-lengths.
No trailing ANSI reset required.
${$EG}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${$RST}"
}]
${[textblock::EG]}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${[textblock::RST]}"
}
#options before content argument - which is allowed to be absent
#frame performance (noticeable with complex tables even of modest size) is improved somewhat by frame_cache - but is still (2024) a fairly expensive operation.
#REVIEW - merging extended (e.g 4:4) underline attributes suppresses all other SGR attributes on at least some terminals which don't support extended underlines
"Return a boolean indicating whether Ansi codes were detected in text.
Important caveat:
When text is a tcl list made from splitting (or lappending) some ansi string
- individual elements may be braced or have certain chars escaped.
(one example is if a list element contains an unbalanced brace)
This can cause square brackets that form part of the ansi to be backslash escaped
- and the function can fail to match it as an Ansi code.
"
@values -min 1
text -type string
} ]
#*** !doctools
#[call [fun detect] [arg text]]
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
#detect any ansi escapes
#review - only detect 'complete' codes - or just use the opening escapes for performance?
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
regexp <re> $text
}]
@ -7405,7 +7432,7 @@ if {![info exists ::punk::args::register::NAMESPACES]} {
#[para]Currently only utf-8, utf-16* and utf-32* are properly supported even though the other BOMs are detected, reported via get_bomid, and stripped from the data.
#[para]GB18030 falls back to cp936/gbk (unless a gb18030 encoding has been installed). Use -encoding iso8859-1 if this isn't suitable and you need to do your own processing of the bytes.
#eat or own dogfood version - shows the implementation is simpler - but unfortunately not suitable for a simple function like this which should be as fast as possible?
#we don't have to decide what is an opt vs a value
#even if the caller provides the argument -block without a value the next function's validation will report a reasonable error because there is now nothing in $values (consumed by -block)
#dirfiles assumes we don't have glob chars in the filenames or paths - dirfiles_dict can be called directly with explicit -tailglob in the rare case that assumption doesn't hold
# dirfiles will test last segment (tail) of supplied searchspecs for fileness vs folderness (when no globchars present in tail) so that it can pass the appropriate flags downstream
#wasn't resolved by id - so take this as a request to generate it (probably there is an existing custom def - and this has been manually requested to get the default)
set origin [string range $origin [string length (autodef)] end]
set subcommands [lsort [dict keys $subcommand_dict]]
if {[llength $commandargs]} {
set match [tcl::prefix::match $subcommands [lindex $commandargs 0]]
if {[llength $queryargs]} {
set match [tcl::prefix::match $subcommands [lindex $queryargs 0]]
if {$match in $subcommands} {
set subcmd [dict get $subcommand_dict $match]
return [arginfo {*}$subcmd {*}[lrange $commandargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
return [arginfo {*}$subcmd {*}[lrange $queryargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
Frame width doesn't adapt and content may be truncated
so -width may need to be manually set to display more."
*values -min 0 -max 1
@values -min 0 -max 1
contents -default "" -type string\
-help "Frame contents - may be a block of text containing newlines and ANSI.
Text may be 'ragged' - ie unequal line-lengths.
No trailing ANSI reset required.
${$EG}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${$RST}"
}]
${[textblock::EG]}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${[textblock::RST]}"
}
#options before content argument - which is allowed to be absent
#frame performance (noticeable with complex tables even of modest size) is improved somewhat by frame_cache - but is still (2024) a fairly expensive operation.
set looplimit [expr {[tcl::string::length $overblock] + 10}]
}
set scheme 3
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
set inputchunks [lindex [list $lflines [unset lflines]] 0]
}
4 {
set inputchunks [list]
foreach ln [split $overblock \n] {
lappend inputchunks [string cat $ln \n]
}
if {[llength $inputchunks]} {
lset inputchunks end [tcl::string::range [lindex $inputchunks end] 0 end-1]
}
}
}
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
#review insert_mode. As an 'overtype' function whose main function is not interactive keystrokes - insert is secondary -
#but even if we didn't want it as an option to the function call - to process ansi adequately we need to support IRM (insertion-replacement mode) ESC [ 4 h|l
set renderargs [list -experimental $opt_experimental\
set renderopts [list -experimental $opt_experimental\
#REVIEW - merging extended (e.g 4:4) underline attributes suppresses all other SGR attributes on at least some terminals which don't support extended underlines
"Return a boolean indicating whether Ansi codes were detected in text.
Important caveat:
When text is a tcl list made from splitting (or lappending) some ansi string
- individual elements may be braced or have certain chars escaped.
(one example is if a list element contains an unbalanced brace)
This can cause square brackets that form part of the ansi to be backslash escaped
- and the function can fail to match it as an Ansi code.
"
@values -min 1
text -type string
} ]
#*** !doctools
#[call [fun detect] [arg text]]
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
#detect any ansi escapes
#review - only detect 'complete' codes - or just use the opening escapes for performance?
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
regexp <re> $text
}]
@ -7405,7 +7432,7 @@ if {![info exists ::punk::args::register::NAMESPACES]} {
#[para]Currently only utf-8, utf-16* and utf-32* are properly supported even though the other BOMs are detected, reported via get_bomid, and stripped from the data.
#[para]GB18030 falls back to cp936/gbk (unless a gb18030 encoding has been installed). Use -encoding iso8859-1 if this isn't suitable and you need to do your own processing of the bytes.
#eat or own dogfood version - shows the implementation is simpler - but unfortunately not suitable for a simple function like this which should be as fast as possible?
#we don't have to decide what is an opt vs a value
#even if the caller provides the argument -block without a value the next function's validation will report a reasonable error because there is now nothing in $values (consumed by -block)
#dirfiles assumes we don't have glob chars in the filenames or paths - dirfiles_dict can be called directly with explicit -tailglob in the rare case that assumption doesn't hold
# dirfiles will test last segment (tail) of supplied searchspecs for fileness vs folderness (when no globchars present in tail) so that it can pass the appropriate flags downstream
#wasn't resolved by id - so take this as a request to generate it (probably there is an existing custom def - and this has been manually requested to get the default)
set origin [string range $origin [string length (autodef)] end]
set subcommands [lsort [dict keys $subcommand_dict]]
if {[llength $commandargs]} {
set match [tcl::prefix::match $subcommands [lindex $commandargs 0]]
if {[llength $queryargs]} {
set match [tcl::prefix::match $subcommands [lindex $queryargs 0]]
if {$match in $subcommands} {
set subcmd [dict get $subcommand_dict $match]
return [arginfo {*}$subcmd {*}[lrange $commandargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
return [arginfo {*}$subcmd {*}[lrange $queryargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
Frame width doesn't adapt and content may be truncated
so -width may need to be manually set to display more."
*values -min 0 -max 1
@values -min 0 -max 1
contents -default "" -type string\
-help "Frame contents - may be a block of text containing newlines and ANSI.
Text may be 'ragged' - ie unequal line-lengths.
No trailing ANSI reset required.
${$EG}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${$RST}"
}]
${[textblock::EG]}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${[textblock::RST]}"
}
#options before content argument - which is allowed to be absent
#frame performance (noticeable with complex tables even of modest size) is improved somewhat by frame_cache - but is still (2024) a fairly expensive operation.
set looplimit [expr {[tcl::string::length $overblock] + 10}]
}
set scheme 3
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
set inputchunks [lindex [list $lflines [unset lflines]] 0]
}
4 {
set inputchunks [list]
foreach ln [split $overblock \n] {
lappend inputchunks [string cat $ln \n]
}
if {[llength $inputchunks]} {
lset inputchunks end [tcl::string::range [lindex $inputchunks end] 0 end-1]
}
}
}
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
#review insert_mode. As an 'overtype' function whose main function is not interactive keystrokes - insert is secondary -
#but even if we didn't want it as an option to the function call - to process ansi adequately we need to support IRM (insertion-replacement mode) ESC [ 4 h|l
set renderargs [list -experimental $opt_experimental\
set renderopts [list -experimental $opt_experimental\
#REVIEW - merging extended (e.g 4:4) underline attributes suppresses all other SGR attributes on at least some terminals which don't support extended underlines
"Return a boolean indicating whether Ansi codes were detected in text.
Important caveat:
When text is a tcl list made from splitting (or lappending) some ansi string
- individual elements may be braced or have certain chars escaped.
(one example is if a list element contains an unbalanced brace)
This can cause square brackets that form part of the ansi to be backslash escaped
- and the function can fail to match it as an Ansi code.
"
@values -min 1
text -type string
} ]
#*** !doctools
#[call [fun detect] [arg text]]
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
#detect any ansi escapes
#review - only detect 'complete' codes - or just use the opening escapes for performance?
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
regexp <re> $text
}]
@ -7405,7 +7432,7 @@ if {![info exists ::punk::args::register::NAMESPACES]} {
#[para]Currently only utf-8, utf-16* and utf-32* are properly supported even though the other BOMs are detected, reported via get_bomid, and stripped from the data.
#[para]GB18030 falls back to cp936/gbk (unless a gb18030 encoding has been installed). Use -encoding iso8859-1 if this isn't suitable and you need to do your own processing of the bytes.
#eat or own dogfood version - shows the implementation is simpler - but unfortunately not suitable for a simple function like this which should be as fast as possible?
#we don't have to decide what is an opt vs a value
#even if the caller provides the argument -block without a value the next function's validation will report a reasonable error because there is now nothing in $values (consumed by -block)
#dirfiles assumes we don't have glob chars in the filenames or paths - dirfiles_dict can be called directly with explicit -tailglob in the rare case that assumption doesn't hold
# dirfiles will test last segment (tail) of supplied searchspecs for fileness vs folderness (when no globchars present in tail) so that it can pass the appropriate flags downstream
#wasn't resolved by id - so take this as a request to generate it (probably there is an existing custom def - and this has been manually requested to get the default)
set origin [string range $origin [string length (autodef)] end]
set subcommands [lsort [dict keys $subcommand_dict]]
if {[llength $commandargs]} {
set match [tcl::prefix::match $subcommands [lindex $commandargs 0]]
if {[llength $queryargs]} {
set match [tcl::prefix::match $subcommands [lindex $queryargs 0]]
if {$match in $subcommands} {
set subcmd [dict get $subcommand_dict $match]
return [arginfo {*}$subcmd {*}[lrange $commandargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
return [arginfo {*}$subcmd {*}[lrange $queryargs 1 end]] ;#subcmd is sometimes multiple words (implemented as a further ensemble subcommand) (e.g huddle string -> "Type_string string")
Frame width doesn't adapt and content may be truncated
so -width may need to be manually set to display more."
*values -min 0 -max 1
@values -min 0 -max 1
contents -default "" -type string\
-help "Frame contents - may be a block of text containing newlines and ANSI.
Text may be 'ragged' - ie unequal line-lengths.
No trailing ANSI reset required.
${$EG}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${$RST}"
}]
${[textblock::EG]}e.g: frame \"[a+ blue White] \\nMy blue foreground text on\\nwhite background\\n\"${[textblock::RST]}"
}
#options before content argument - which is allowed to be absent
#frame performance (noticeable with complex tables even of modest size) is improved somewhat by frame_cache - but is still (2024) a fairly expensive operation.
set looplimit [expr {[tcl::string::length $overblock] + 10}]
}
set scheme 3
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
set inputchunks [lindex [list $lflines [unset lflines]] 0]
}
4 {
set inputchunks [list]
foreach ln [split $overblock \n] {
lappend inputchunks [string cat $ln \n]
}
if {[llength $inputchunks]} {
lset inputchunks end [tcl::string::range [lindex $inputchunks end] 0 end-1]
}
}
}
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
#review insert_mode. As an 'overtype' function whose main function is not interactive keystrokes - insert is secondary -
#but even if we didn't want it as an option to the function call - to process ansi adequately we need to support IRM (insertion-replacement mode) ESC [ 4 h|l
set renderargs [list -experimental $opt_experimental\
set renderopts [list -experimental $opt_experimental\
set looplimit [expr {[tcl::string::length $overblock] + 10}]
}
set scheme 3
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
set inputchunks [lindex [list $lflines [unset lflines]] 0]
}
4 {
set inputchunks [list]
foreach ln [split $overblock \n] {
lappend inputchunks [string cat $ln \n]
}
if {[llength $inputchunks]} {
lset inputchunks end [tcl::string::range [lindex $inputchunks end] 0 end-1]
}
}
}
#overblock height/width isn't useful in the presence of an ansi input overlay with movements. The number of lines may bear little relationship to the output height
#review insert_mode. As an 'overtype' function whose main function is not interactive keystrokes - insert is secondary -
#but even if we didn't want it as an option to the function call - to process ansi adequately we need to support IRM (insertion-replacement mode) ESC [ 4 h|l
set renderargs [list -experimental $opt_experimental\
set renderopts [list -experimental $opt_experimental\
#REVIEW - merging extended (e.g 4:4) underline attributes suppresses all other SGR attributes on at least some terminals which don't support extended underlines
"Return a boolean indicating whether Ansi codes were detected in text.
Important caveat:
When text is a tcl list made from splitting (or lappending) some ansi string
- individual elements may be braced or have certain chars escaped.
(one example is if a list element contains an unbalanced brace)
This can cause square brackets that form part of the ansi to be backslash escaped
- and the function can fail to match it as an Ansi code.
"
@values -min 1
text -type string
} ]
#*** !doctools
#[call [fun detect] [arg text]]
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
#detect any ansi escapes
#review - only detect 'complete' codes - or just use the opening escapes for performance?
#[para]Return a boolean indicating whether Ansi codes were detected in text
#[para]Important caveat:
#[para] When text is a tcl list made from splitting (or lappending) some ansi string - individual elements may be braced or have certain chars escaped. (one example is if a list element contains an unbalanced brace)
#[para] This can cause square brackets that form part of the ansi being backslash escaped - and the regexp can fail to match
regexp <re> $text
}]
@ -7405,7 +7432,7 @@ if {![info exists ::punk::args::register::NAMESPACES]} {
