aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/interface.h
diff options
context:
space:
mode:
authorRobin Haberkorn <robin.haberkorn@googlemail.com>2024-09-04 12:49:29 +0200
committerRobin Haberkorn <robin.haberkorn@googlemail.com>2024-09-09 18:22:21 +0200
commitb31b88717172e22b49c0493185f603b8f84989ec (patch)
tree43850d7d04e721987b89c37c68f24e657b5cb9c6 /src/interface.h
parentb85edaa0021c06d63fee6d8904fc822815e8b933 (diff)
downloadsciteco-b31b88717172e22b49c0493185f603b8f84989ec.tar.gz
the ^EUq string building escape now respects the encoding (can insert bytes or codepoints) (refs #5)
* This is trickier than it sounds because there isn't one single place to consult. It depends on the context. If the string argument relates to buffer contents - as in <I>, <S>, <FR> etc. - the buffer's encoding is consulted. If it goes into a register (EU), the register's encoding is consulted. Everything else (O, EN, EC, ES...) expects only Unicode codepoints. * This is communicated through a new field teco_machine_stringbuilding_t::codepage which must be set in the states' initial callback. * Seems overkill just for ^EUq, but it can be used for context-sensitive processing of all the other string building constructs as well. * ^V and ^W cannot be supported for Unicode characters for the time being without an Unicode-aware parser
Diffstat (limited to 'src/interface.h')
-rw-r--r--src/interface.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/interface.h b/src/interface.h
index cbe10bd..bbefe88 100644
--- a/src/interface.h
+++ b/src/interface.h
@@ -154,6 +154,12 @@ void teco_interface_process_notify(SCNotification *notify);
/** @pure */
void teco_interface_cleanup(void);
+static inline guint
+teco_interface_get_codepage(void)
+{
+ return teco_view_get_codepage(teco_interface_current_view);
+}
+
static inline gssize
teco_glyphs2bytes(teco_int_t pos)
{