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
are both valid control sequences in xterm but the former won't work because the start sequence "\033]0;" is used to lookup an alist (the first match is always used). In this case, we can modify the algorithm to keep all matches of the start sequence in the alist but I'm not sure if such a modified algorithm can catch all the other control sequences. In general, some kind of grammer parsing algorithm is needed.
There are also some other restrictions in control commands (described in the documentation of term-emulate-terminal).
xterm-256color.el cannot be our savior
xterm-256color.el aims at as much xterm compatibility as possible by patching the original implementation of term.el. This kind of patching is cumbersome and have a large risk of making a new bug. Introducing a systematic grammer parser without breaking the original implementation is a castle in the air.
What we need
My opinion is to rewrite term.el from scratch with a grammer parser in a modern way but this would be another project.
The text was updated successfully, but these errors were encountered:
Currently, there are many missing control sequences but it tends to be difficult to support some minor ones.
Control commands are not enough
Some OSC sequences are added as control commands but this is fundamentally a wrong way because of restrictions of control commands.
It is not possible to define some missing xterm control sequences by
term+new-control-command
. For example,are both valid control sequences in xterm but the former won't work because the start sequence
"\033]0;"
is used to lookup an alist (the first match is always used). In this case, we can modify the algorithm to keep all matches of the start sequence in the alist but I'm not sure if such a modified algorithm can catch all the other control sequences. In general, some kind of grammer parsing algorithm is needed.There are also some other restrictions in control commands (described in the documentation of
term-emulate-terminal
).xterm-256color.el cannot be our savior
xterm-256color.el aims at as much xterm compatibility as possible by patching the original implementation of term.el. This kind of patching is cumbersome and have a large risk of making a new bug. Introducing a systematic grammer parser without breaking the original implementation is a castle in the air.
What we need
My opinion is to rewrite term.el from scratch with a grammer parser in a modern way but this would be another project.
The text was updated successfully, but these errors were encountered: